Openmoko Bug #1597: after a long suspend time, kernel thread events/0 sits eating 30% cpu
Openmoko Public Trac
bugs at docs.openmoko.org
Fri Oct 3 07:58:02 CEST 2008
#1597: after a long suspend time, kernel thread events/0 sits eating 30% cpu
--------------------------------+-------------------------------------------
Reporter: raster | Owner: zecke
Type: defect | Status: in_testing
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
--------------------------------+-------------------------------------------
Comment(by werner):
From reading the code, I'd say that the ar6000_ioctl_giwscan message means
that no access points were found and SIOCGIWSCAN returned EAGAIN, which is
arguably the wrong return code.
I don't know if not finding any access points is cause or effect, though.
Does my ar6k-giwscan-no-eagain.patch ease the pain ?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1597#comment:29>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
More information about the buglog
mailing list