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 #2123: SMS doesn't work in framworkd
(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 #2003: [Setting] Please take out suspend
time "10 sec." (Openmoko Public Trac)
8. Re: Openmoko Bug #2003: [Setting] Please take out suspend
time "10 sec." (Openmoko Public Trac)
--- Begin Message ---
#2123: SMS doesn't work in framworkd
---------------------------+------------------------------------------------
Reporter: think-free | Owner: openmoko-kernel
Type: defect | Status: closed
Priority: normal | Milestone:
Component: unknown | Version:
Severity: blocker | Resolution: invalid
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
---------------------------+------------------------------------------------
Comment(by alphaone):
Please file your bug at http://trac.freesmartphone.org, assign to daniel
and use frameworkd/ogsmd as component. Please also list the git hash of
frameworkd you are using.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2123#comment:2>
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 | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: always |
----------------------------+-----------------------------------------------
Comment(by nicolas.dufresne):
I've seen the hard reset that has been added in the jbt driver in stable-
tracking so I've tested it. I've got the same problem too, but I've tested
only once and did not try to sleep it again to see if reset help
recovering (I will try to find time later to do this test).
I've been reading the jbt driver source code today. I have a feeling that
locking is too weak. I think it only protects the registry cache.This
makes me think there is a larger problem. As the resume process implies
multiple reg_write (and the locking is done inside this function) it means
that registry could be written during a suspend or resume sequence or
registry write, which I don't think it is a good idea. But I might also be
totally wrong.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:65>
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 | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: always |
----------------------------+-----------------------------------------------
Comment(by theseer105):
I tried it today. I always get WSOD with a cold freerunner. If the
Freerunner is about body temperature it resumes fine.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:66>
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 | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: always |
----------------------------+-----------------------------------------------
Comment(by andy):
Is it ever the case that once you had a WSOD, by making it right
temperature or anything else, that we ever recover from it during the same
session?
On current andy-tracking there is a /sys node
/sys/class/i2c-adapter/i2c-0/0-0073/pcf50633-regltr.9/glamo3362.0/glamo-
spi-gpio.0/spi2.0/reset
if you echo 1 in there (take care about spaces, echo 1 > /sys...) it
should reset the jbt6k74 asic in the LCM.
Nicolas: About the locking, yes it can make trouble because the
framebuffer blanking action that calls through to jbt6k74 code now is
async to resume action in jbt6k74. But if this was the problem, a
subsequent use of that reset /sys node should clear it, since that reset
code does a physical hard reset of the LCM similar to boot init, and we
NEVER see WSOD on boot. But I get the feel this WSOD thing is super
sticky and the only thing that impresses it is reboot which is knows about
somehow.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:67>
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 | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: always |
----------------------------+-----------------------------------------------
Comment(by nicolas.dufresne):
I've added trace to the jbt driver and can confirmed that the locking was
not affecting the resume process. Every calls are exclusive and are
produced in same order both cases (wsod or not).
I wanted to test using andy-tracking and doing the reset, unfortunately
the branch won't compile. I've also tried the kernel on
http://people.openmoko.org/andy, but I always get a Bad CRC error from
uboot. I'll try later ... I think it's important to confirm if the wsod
can be recovered or if it sticks until reboot.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:68>
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 | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: always |
----------------------------+-----------------------------------------------
Comment(by theseer105):
I think it's the temperature. Freerunner was over night on the heating and
wakes up without WSOD. Same test on the table there is a WSOD.
The Freerunner is 5 minutes in the fridge and it resumes with WSOD even if
I tried "echo 1 > /sys ..." bevor I toutch the Freerunner
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:69>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2003: [Setting] Please take out suspend time "10 sec."
---------------------------+------------------------------------------------
Reporter: wendy_hung | Owner: john_lee
Type: defect | Status: assigned
Priority: normal | Milestone:
Component: Settings | Version:
Severity: normal | Resolution:
Keywords: Om2008.11 | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
---------------------------+------------------------------------------------
Changes (by sushama):
* owner: marek => john_lee
* status: in_testing => assigned
Comment:
Test Date:24-nov-2008
'10 sec ' is still displayed under setting.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2003#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2003: [Setting] Please take out suspend time "10 sec."
---------------------------+------------------------------------------------
Reporter: wendy_hung | Owner: john_lee
Type: defect | Status: in_testing
Priority: normal | Milestone:
Component: Settings | Version:
Severity: normal | Resolution:
Keywords: Om2008.11 | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
---------------------------+------------------------------------------------
Changes (by john_lee):
* cc: [EMAIL PROTECTED] (removed)
* cc: [EMAIL PROTECTED] (added)
* status: assigned => in_testing
Comment:
marek:
please remember to modify conf/distro/include/sane-srcrevs.inc as well
after you updated om-settings. thanks.
committed as b688012b25b6aae3665ad5e3758974a96a6a34e0
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2003#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
