Send buglog mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:
1. Re: Openmoko Bug #1597: after a long suspend time, kernel
thread events/0 sits eating 30% cpu (Openmoko Public Trac)
2. Re: Openmoko Bug #1597: after a long suspend time, kernel
thread events/0 sits eating 30% cpu (Openmoko Public Trac)
3. Re: Openmoko Bug #2067: qtopia-phone-x11 overwrites
(important) configuration files on package update
(Openmoko Public Trac)
4. Re: Openmoko Bug #1597: after a long suspend time, kernel
thread events/0 sits eating 30% cpu (Openmoko Public Trac)
5. Re: Openmoko Bug #1597: after a long suspend time, kernel
thread events/0 sits eating 30% cpu (Openmoko Public Trac)
6. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
7. Re: Openmoko Bug #1597: after a long suspend time, kernel
thread events/0 sits eating 30% cpu (Openmoko Public Trac)
8. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
--- Begin Message ---
#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 zecke):
Debugging hint:
- Compile a6k as module make it autoload
- If CPU is eaten unload the module
Hypothesis:
- events/0 is executing the work queue of the hcd s3c implementation of
"Openmoko" (glue)
- interrupts will continue but the cpu will not be busy anymore
What would be interesting:
- loading the module again (assuming the hcd s3c implementation is doing
a reset)
- What happens with the interrupts and the load
- Maybe even restart connman
Possible outcomes:
- With reload/reset interrupts come in and events/0 is busy => firmware
- With reload/reset interrupts are normal => our hcd glue
who is willing to do what is necessary?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1597#comment:38>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#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):
Unload/reset would most likely stop the trouble, but that may just be
because the driver would of course reset the WLAN module. My current
plan is to just observe but otherwise ignore that bug for now and put
everything on the Linux SDIO stack instead. Then we'll see if the
problem persists.
Regarding the USB crash: seems that this is caused by the accelerometer
driver trying to get a mutex while interrupts are off and isn't related
to the WLAN problem. I think Andy has a patch that gets rid of all those
mutex uses in the driver, so it should solve that specific issue.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1597#comment:39>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2067: qtopia-phone-x11 overwrites (important) configuration files on package
update
------------------------+---------------------------------------------------
Reporter: kavol | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
------------------------+---------------------------------------------------
Comment(by zecke):
Would you be willing to do a fix? qtopia-phone-x11.git in the OE metadata
needs to mark some CONFFILES in the right packages. It is an easy but time
consuming task and I don't see myself doing it in the next half a year.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2067#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#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 andy):
ar6k doesn't work as it is when compiled as a module. The stack doesn't
pick up that it exists on module insertion.
Having WLAN stuff as a module gives some nice opportunity to recover from
this and firmware / stack problems without reboot, it also enables power
saving stuff too.
If Werner can put ar6k on normal stack, maybe it can detect "insertion"
properly and we can use the whole thing as a module, that will be another
advantage of the change.
Attempts to use Linux SPI stack with interrupt lockout are doomed, these
are the source of the dmesg traffic.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1597#comment:40>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#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 zecke):
"Insertion" should be farily easy to add to the a6k stack... our hcd glue
is sending such an event... it is just a nightmare to track it.
Disclaimer: This does not mean I volunteer. :)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1597#comment:41>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1841: white screen of death (WSOD) after resume
----------------------------+-----------------------------------------------
Reporter: Rorschach | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: GTA02v5
Severity: critical | Resolution:
Keywords: wsod,resume | Blockedby:
Reproducible: always | Blocking:
----------------------------+-----------------------------------------------
Comment(by leachim):
Since i changed the display of my freerunner the white screen of death has
gone.
Before every resume longer than 10 minutes resulted in a white screen
issue.
I hope that this information helps to fix the problem.
Greetings, Michael
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:30>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#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 lala):
And another thing, maybe will be helpful: the power consumption is ~100mA
with brightness set to low and gsm activated. When events/0 starts to eat
~27% CPU, the consumption goes to 200-240mA, and after 2-3 hours the front
of the neo is unusual hot.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1597#comment:42>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1841: white screen of death (WSOD) after resume
----------------------------+-----------------------------------------------
Reporter: Rorschach | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: GTA02v5
Severity: critical | Resolution:
Keywords: wsod,resume | Blockedby:
Reproducible: always | Blocking:
----------------------------+-----------------------------------------------
Comment(by nelg):
Replying to [comment:30 leachim]:
> Since i changed the display of my freerunner the white screen of death
has gone.
> Before every resume longer than 10 minutes resulted in a white screen
issue.
>
Did you replace they physical display? or are you talking something in
software?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:31>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
