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. Openmoko Bug #1996: display stays blank at incoming call
(Openmoko Public Trac)
4. Re: Openmoko Bug #1792: SMS not received properly during
suspend (Openmoko Public Trac)
5. Re: Openmoko Bug #1939: wifi crashes the device
(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 | Resolution:
Keywords: wsod,resume | Blockedby:
Reproducible: always | Blocking:
----------------------------+-----------------------------------------------
Comment(by GiggleLoop):
I have this problem too, I'm adding my info in case it helps track down
the culprit.
The WSOD seems only to occur after more than 1-2 hours standby. Standby
overnight (appx. 8 hours) triggers it all the time.
My versions:
{{{
# cat /etc/om-version
Tag Name:
VERSION: c4a208ae4114f14224a5fa37e55a8b2a51fbd5ba
Branch: org.openmoko.asu.stable
Build Host: barbie
Time Stamp: Wed, 10 Sep 2008 08:22:26 +0800
}}}
{{{
# uname -a
Linux om-gta02 2.6.24 #1 PREEMPT Wed Sep 3 19:01:18 CST 2008 armv4tl
unknown
}}}
{{{
baa7e75288d30d67e263d4486d977cfa Om2008.8-gta02-20080903.uImage.bin
92e0360acd0af200b519b4a33bd99ed5 Om2008.8-gta02-20080910.rootfs.jffs2
3c1ee3fb8a03dfa5b3b44491d33517a6 gta02v5_and_up-u-boot.bin
}}}
I'm attaching the dmesg output.
Is there anything else I can run/try to help debug?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:16>
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 GiggleLoop):
I have this problem too, I'm adding my info in case it helps track down
the culprit.
The WSOD seems only to occur after more than 1-2 hours standby. Standby
overnight (appx. 8 hours) triggers it all the time.
My versions:
{{{
# cat /etc/om-version
Tag Name:
VERSION: c4a208ae4114f14224a5fa37e55a8b2a51fbd5ba
Branch: org.openmoko.asu.stable
Build Host: barbie
Time Stamp: Wed, 10 Sep 2008 08:22:26 +0800
}}}
{{{
# uname -a
Linux om-gta02 2.6.24 #1 PREEMPT Wed Sep 3 19:01:18 CST 2008 armv4tl
unknown
}}}
{{{
baa7e75288d30d67e263d4486d977cfa Om2008.8-gta02-20080903.uImage.bin
92e0360acd0af200b519b4a33bd99ed5 Om2008.8-gta02-20080910.rootfs.jffs2
3c1ee3fb8a03dfa5b3b44491d33517a6 gta02v5_and_up-u-boot.bin
}}}
I'm attaching the dmesg output.
Is there anything else I can run/try to help debug?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:16>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1996: display stays blank at incoming call
----------------------+-----------------------------------------------------
Reporter: h.koenig | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Keywords:
Blockedby: | Reproducible:
Blocking: |
----------------------+-----------------------------------------------------
running Om 2008.8 + updates:
today I tried calling my FR (for me usually it's not a phone;). vibration
alarm and bell worked fine,but the display stays blank. so it's not
possible to see who's calling, without touching the display (or maybe even
without releasing the lock or similar).
other phones usually switch the on display on incoming calls...
btw, the FR was not suspended (see #1985) but only screen saver was
active.
is this a known (IMHO bad) feature or a bug ?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1996>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1792: SMS not received properly during suspend
------------------------+---------------------------------------------------
Reporter: thomasb | Owner: zecke
Type: defect | Status: in_testing
Priority: normal | Milestone: Om2008.9
Component: Qtopia | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
------------------------+---------------------------------------------------
Comment(by thomasb):
Replying to [comment:17 regina_kim]:
> hey thomasb
> can you test this ticket again weather is happen still ?
Sure. I tested it again today with the most recent packages from the
2008.8-update feed.
> what about get sms when not suspend status ??
It works perfectly, both when on suspend and when not suspended: The
device wakes up (if suspended), it shows a notification on screen, it
vibrates and it beeps.
In the three weeks since the fix for #1776 was applied I have observed
this issue exactly once, but I wasn't able to reproduce it. Might as well
have been due to normal network delay when delivering the SMS. I will
report back if I ever see it again.
Until then, I regard this as fixed for me.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1792#comment:18>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1939: wifi crashes the device
-------------------------+--------------------------------------------------
Reporter: gawlitza | Owner: marek
Type: defect | Status: assigned
Priority: normal | Milestone: Om2008.9
Component: unknown | Version: Om2008.9-dev
Severity: major | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
-------------------------+--------------------------------------------------
Comment(by gawlitza):
Hi Marek,
answering your question via mail does not work (mail returned with not
known address).
The hang occurs if you want to establish a wep-key-secured wlan-
connection. It occurs NOT with unsecured wlan. If you disable wep-key
security in the router and let the wep key in iwconfig empty, then wifi
works and you can install packages and so on ! If you set wep-key with
iwconfig and then - which is necessary - set the proper essid, then system
freezes, you must remove all plugs and battery to reboot. Therefore I
think this is a kernel / kernel-module / driver problem, and not a problem
of applications in rootfs. This is reproducable every time I tried.
I have frerunner full-flashed with Om2008.8-gta02-20080903.uImage.bin and
Om2008.8-gta02-20080904.rootfs.jffs2.
Greatings M. Gawlitza
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1939#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
