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 #1192: unknown reason cause TI GSM modem
always return "+CME ERROR: 512" (Openmoko Public Trac)
4. Re: Openmoko Bug #1192: unknown reason cause TI GSM modem
always return "+CME ERROR: 512" (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 #1841: white screen of death (WSOD) after
resume (Sten Kvamme)
8. Openmoko Bug #2126: xserver-xglamo eats 100% cpu time after
resume (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 | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: always |
----------------------------+-----------------------------------------------
Comment(by mmezo):
/proc/cpuinfo shows:
Hardware : GTA02
Revision : 0350
back:
Model: GTA02
S/N: 8A8602752
Date Code: 20080618
P/N: 56-21147-00
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:51>
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 mrmoku):
/proc/cpuinfo:
Hardware : GTA02
Revision : 0360
gsmdevice.GetInfo (from within cli-framework)
'model': '"Neo1973 GTA02 Embedded GSM Modem"',
'revision': '"HW: GTA02BV5, GSM:
gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko8"'}
inside:
Model: GTA02
S/N: 8A8710361
Date Code: 20080725
P/N: 56-21147-00
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:52>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1192: unknown reason cause TI GSM modem always return "+CME ERROR: 512"
-----------------------------------------+----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: openmoko-devel
Type: defect | Status: assigned
Priority: high | Milestone:
Component: hardware | Version:
Severity: critical | Resolution:
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
-----------------------------------------+----------------------------------
Changes (by mickey):
* component: Qtopia => hardware
Comment:
I just got the first report from someone whose 512 was fixed by updating
to moko10-beta2 firmware. Although this may be unrelated (since we still
don't know which exact conditions lead to 512), it may be worthwhile to
try. 512 may be connected to Om ticket #666.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1192#comment:22>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1192: unknown reason cause TI GSM modem always return "+CME ERROR: 512"
-----------------------------------------+----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: openmoko-devel
Type: defect | Status: assigned
Priority: high | Milestone:
Component: hardware | Version:
Severity: critical | Resolution:
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
-----------------------------------------+----------------------------------
Comment(by mickey):
Someone also needs to double check whether
[http://docs.openmoko.org/trac/changeset/3964] has any effect on 512 or
not.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1192#comment:23>
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 vanous):
Qtopia reports:
GTA02BV5
Backside:
S/N 8A8710381
DATE 20080728
GSM MOKO8
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:53>
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 RuiSeabra):
In my case (WSoD after resume / and more recently after dimming as well:
#2115)
/proc/cpuinfo shows:
Hardware : GTA02
Revision : 0350
back:
Model: GTA02
S/N: 8A8603495
Date Code: 20080621
P/N: 56-21147-00
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:54>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
On ons, 2008-11-19 at 08:18 +0000, Openmoko Public Trac wrote:
> #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 joerg):
>
> Please can we collect exact hw-revision (A5, A6...), serial# (!), and
> datecode for every device showing WSOD.
> Please attach to this ticket!
> thanks,
> jOERG
>
P/N 70-7GTA01B-00001
S/N 8A7507389
'manufacturer': '"FIC/OpenMoko"',
'model': '"Neo1973 GTA01 Embedded GSM Modem"',
'revision': '"HW: GTA01Bv4, GSM:
gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko1"'}
/Sten Kvamme
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
#2126: xserver-xglamo eats 100% cpu time after resume
---------------------+------------------------------------------------------
Reporter: lindi | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
---------------------+------------------------------------------------------
xserver-xglamo seems to spend 100% cpu time after resume from suspend
sometimes.
I am using debian with
ii linux-image-2.6.24-openmoko-gta02 20081103.git7172ec57-1
Linux 2.6.24 kernel image for the Openmoko Neo Freerunner
ii xserver-xglamo 1.3.0.0+git20080807-3
tiny X server for the SMedia Glamo graphics chipset
[[Image()]]
Strace shows that xglamo calls gettimeofday again and again. The attached
file xglamo-instructions.txt shows what instructions xglamo is executing
according to gdb but backtrace prints just
#0 0x00014e3c in ?? ()
Cannot access memory at address 0x0
so it is not very usable. I can not kill X with kill -9 and dmesg shows
{{{
BUG: scheduling while atomic: X/1885/0x00000002
[<c0344a08>] (dump_stack+0x0/0x14) from [<c0041cdc>]
(__schedule_bug+0x50/0x5c)
[<c0041c8c>] (__schedule_bug+0x0/0x5c) from [<c02b7c78>]
(schedule+0x6c/0x2d4)
r4:0001c33b
[<c02b7c0c>] (schedule+0x0/0x2d4) from [<c0041fec>]
(sys_sched_yield+0x48/0x54)
[<c0041fa4>] (sys_sched_yield+0x0/0x54) from [<c02b8024>]
(yield+0x24/0x28)
[<c02b8000>] (yield+0x0/0x28) from [<c01ad0d0>]
(glamofb_cmd_mode+0x24/0xf0)
[<c01ad0ac>] (glamofb_cmd_mode+0x0/0xf0) from [<c01ad200>]
(glamofb_set_par+0x64/0x444)
r5:c7c6ce74 r4:c7c6cc00
[<c01ad19c>] (glamofb_set_par+0x0/0x444) from [<c01740ac>]
(fb_set_var+0x1ac/0x258)
r8:00000020 r7:c71abe48 r6:c7c6cc00 r5:c71abe48 r4:c01ace70
[<c0173f00>] (fb_set_var+0x0/0x258) from [<c01742ac>]
(fb_ioctl+0x154/0x4dc)
[<c0174158>] (fb_ioctl+0x0/0x4dc) from [<c00a3b48>] (do_ioctl+0x80/0x9c)
r8:c0029128 r7:00134628 r6:00004601 r5:00134628 r4:c7e652c0
[<c00a3ac8>] (do_ioctl+0x0/0x9c) from [<c00a3e1c>] (vfs_ioctl+0x2b8/0x2e8)
r6:00004601 r5:c7e652c0 r4:c7ea80a4
[<c00a3b64>] (vfs_ioctl+0x0/0x2e8) from [<c00a3e8c>] (sys_ioctl+0x40/0x60)
r7:c7e652c0 r6:00004601 r5:00134628 r4:00000004
[<c00a3e4c>] (sys_ioctl+0x0/0x60) from [<c0028f80>]
(ret_fast_syscall+0x0/0x2c)
r7:00000036 r6:00134fe0 r5:001351a8 r4:00134628
}}}
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2126>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
