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 #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
2. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
3. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
4. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
5. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
6. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
7. Re: Openmoko Bug #2155: opkg-native do_compile failed
(Openmoko Public Trac)
8. Openmoko Bug #2160: bluetooth is powered up on resume and
bootup (Openmoko Public Trac)
--- 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 | Keywords: wsod,resume
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------+----------------------------------------------------
Comment(by andy):
I have added your second patch on stable, and put both on stable-tracking
now. Thanks again for the work on it.
It's pretty interesting actually, this new sticky LCM behaviour of "jazzy
lines" is provoked solely by taking down LDO6, the LCM power during
suspend. If I have LDO6 kept up during suspend, no jazzy lines.
However while we don't take down LDO6 and we didn't enter deep sleep in
LCM ASIC, I guess we are burning a little power in suspend we don't need
to... it's less of an issue than WSOD :-) but it still needs looking at.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:100>
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 | Keywords: wsod,resume
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------+----------------------------------------------------
Comment(by nicolas.dufresne):
Those "jazzy lines" are probably a separate issue. I've seen those by
switching to QVGA or sometimes when I rotate the screen.
For Joerg comment you are right, he haven't posted on dev list or track,
he posted on the owners list. I don't know why ... Here's the comment I
was referring
From Joerg on owners list:
|The "no deep_suspend" patch didn't work for us -> it's a problem often
|triggered by but not directly caused by deep_suspend.
But I don't think this was their final conclusion. Anyway, if that patch
only fixes half of the affected devices, we still have half of devices
owners that can now use and test the device for longer period of time.
For power consumption, I've tested what percentage would go away over
night (~9h) and I end up night at 87% (-13%). I guess this is pretty much
the right number since an other owner have sent me this exact same stats
(owner is Sebastien Hammerl, thanks to you).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:101>
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 | Keywords: wsod,resume
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------+----------------------------------------------------
Comment(by andy):
Replying to [comment:101 nicolas.dufresne]:
> Those "jazzy lines" are probably a separate issue. I've seen those by
switching to QVGA or sometimes when I rotate the screen.
Yes they are a separate issue for sure. The stickiness of it same as WSOD
was interesting though, but now Balaji is checking it can be caused by
something different on his side.
> But I don't think this was their final conclusion. Anyway, if that patch
only fixes half of the affected devices, we still have half of devices
owners that can now use and test the device for longer period of time.
Well the patch works for me on unaffected LCM, that's good enough for me
when added to only positive feedback from customer test of your patch on
affected device.
> For power consumption, I've tested what percentage would go away over
night (~9h) and I end up night at 87% (-13%). I guess this is pretty much
the right number since an other owner have sent me this exact same stats
(owner is Sebastien Hammerl, thanks to you).
Awesome, that's not very noticeable change either. If Balaji find the
issue is on his side about LDO6 there is chance we can even take the LCM
completely down too, but this situation as it stands is a lot better than
the WSOD we can't impact.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:102>
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 | Keywords: wsod,resume
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------+----------------------------------------------------
Comment(by TimoJyrinki):
With the cleaner patch that appeared in stable-tracking, I can now play
Pingus (which rotates the screen) without problems - earlier I got the
whitish screen. Still though Doom does not work (which both changes to
QVGA and rotates screen) - I got a corrupted screen still, though it's
different than what was there before the patch. Now it's a darker screen
with stripes etc, earlier it was close to pure white with various lines
etc.
Please tell if there is a separate bug for these screen mode change
problems I can follow.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:103>
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 | Keywords: wsod,resume
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------+----------------------------------------------------
Comment(by andy):
Replying to [comment:103 TimoJyrinki]:
> With the cleaner patch that appeared in stable-tracking, I can now play
Pingus (which rotates the screen) without problems - earlier I got the
whitish screen.
Great.
> Still though Doom does not work (which both changes to QVGA and rotates
screen) - I got a corrupted screen still, though it's different than what
was there before the patch. Now it's a darker screen with stripes etc,
earlier it was close to pure white with various lines etc.
>
> Please tell if there is a separate bug for these screen mode change
problems I can follow.
Try #1812 if it is the same, otherwise create a new one.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:104>
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 | Keywords: wsod,resume
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------+----------------------------------------------------
Comment(by Seppi):
Here is the Kernel which i compiled for me with the patch from 11/26/08
Works very well for me, no WSOD since then. Nicolas is my hero :)
http://music-starvation.de/openmoko/uImage_no_deep_sleep_11262008.bin
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:105>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2155: opkg-native do_compile failed
---------------------+------------------------------------------------------
Reporter: manitu | Owner: tick
Type: defect | Status: in_testing
Priority: high | Milestone:
Component: opkg | Version:
Severity: blocker | Keywords: opkg opkg-native do_compile SUSE11.0
compile error free_error_list opkh_cmd.c opkg_cmd opkg_print_error_list
Haspatch: 1 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
---------------------+------------------------------------------------------
Comment(by tick):
ah...
4844 already contains the free_error_list(&error_list); patch
so you do not need to patch that again. :-)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2155#comment:14>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2160: bluetooth is powered up on resume and bootup
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: highest | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------------+----------------------------------------------
With stable-tracking 80f4b57fef5dcffb it seems that bluetooth chip is
powered up (neo1973-pm-bt.0/power_on=1) after resume and bootup. If I
power it down it is up again after the phone returns from suspend.
I use debian on freerunner and stopped fso-frameworkd while doing this
testing just to make sure it does not touch the power status of bluetooth.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2160>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
