Open GoogleCodeExporter opened 8 years ago
strace on netd consuming 100% CPU
Original comment by christia...@gmail.com
on 3 Dec 2012 at 9:49
Attachments:
hi,
I have exactly the same issue on my Galaxy Axe. I also tried Wayland cm9.1, and
Maclaw aosp, and issue remains. I also saw in xda some other people who have
the same issue, on CM10.1, on Mini or Gio.
Original comment by gregory....@gmail.com
on 14 Jan 2013 at 11:29
I have exactly the same issue on my Gio. CyanogenMod10.1 (OS 4.2.2).
Original comment by incoming...@gmail.com
on 18 Feb 2013 at 1:10
[deleted comment]
Exactly the same issue (Ace, CM 10.1-20130615-NIGHTLY-cooper)
Original comment by ri...@boogiepalace.hopto.org
on 30 Jul 2013 at 9:11
I got exactly the same issues in
CyanogenMod10.1,aokp,aosp,paranoid,pacrom........
Anyone know how to fix this issue ????
Original comment by a...@camerocks.com
on 23 Aug 2013 at 4:05
I think I found the cause of this issue. The problem is in the code parsing
netlink messages, which is used by netd. It seems that netd gets stuck in
infinite loop as soon as it receives buggy netlink message. I've created a
patch to avoid that, however it needs more testing and possibly some refining.
Original comment by Kazimier...@gmail.com
on 21 Dec 2013 at 9:54
Attachments:
but how to apply the patch ?
Original comment by junnick....@gmail.com
on 5 Jan 2014 at 1:26
Same problem on Galaxy Mini/Next with cm-10.1-20130402-NIGHTLY-tass from
http://forum.xda-developers.com/showthread.php?t=2085347
Original comment by davide.cavestro
on 7 Jan 2014 at 4:26
The patch should be applied on a CM9 source code before build a rom. Here is a
compiled libsysutils.so for Galaxy Gio using the MMB CM9 source tree and above
patch. Anyone brave enough may replace the original library with this one. Of
course I'm not responsible for any bricked phone :)
Original comment by Kazimier...@gmail.com
on 7 Jan 2014 at 7:08
Attachments:
Anyone can build a libsysutils.so for Galaxy ACE CM 10.1 ?
Original comment by wilson.c...@oppa.com.br
on 8 Jan 2014 at 1:44
Original issue reported on code.google.com by
christia...@gmail.com
on 3 Dec 2012 at 9:46Attachments: