Ticket #2294 (closed defect: fixed)
xf86-video-glamo: stopping X can crash the whole system (not even JTAG works)
| Reported by: | lindi | Owned by: | openmoko-kernel |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | kernel | Version: | unspecified |
| Severity: | normal | Keywords: | xf86-video-glamo WSOD Xorg |
| Cc: | Blocked By: | ||
| Blocking: | Estimated Completion (week): | ||
| HasPatchForReview: | no | PatchReviewResult: | |
| Reproducible: | always |
Description
Steps to reproduce:
1) sudo gdb
2) attach <pid-of-X>
3) break GlamoRestoreHW
4) continue
5) sudo kill pidof X
6) continue
7) continue
8) continue
9) continue
Expected results:
6-8) gdb stops due to three signals
9) gdb stops at GlamoRestoreHW and shows its prompt
Actual results:
6-9) gdb stops due to three signals and at GlamoRestoreHW. However, gdb is unable to show its prompt and the whole system stops responding. Even JTAG stops working:
(gdb) break GlamoRestoreHW
Breakpoint 1 at 0x405658b0: file glamo-driver.c, line 744.
(gdb) c
Continuing.
Program received signal SIGTERM, Terminated.
[Switching to Thread 0x40021c50 (LWP 1476)]
0x4039ffe4 in select () from /lib/libc.so.6
(gdb) c
Continuing.
Program received signal SIGTERM, Terminated.
0x000efac4 in ?? ()
(gdb) c
Continuing.
Program received signal SIGCONT, Continued.
0x000efd7c in GiveUp? ()
(gdb)
Continuing.
Breakpoint 1, GlamoRestoreHW (pScrn=0x1c02f8) at glamo-driver.c:744
More info:
1) xf86-video-glamo 451398a21
2) linux 9ecc089861ab238e
3) GDB is not strictly needed here. It is used here just to slow down Xorg so that it hits the bug always:
--- Log opened Sun May 10 08:23:26 2009
08:23 <lars_> i just updated to the newest kernel and i get a wsod every time i quit X

The problem was caused by turning of the glamo memory clock and has been fixed with commit 69ccc9307c6b6a1aeb1f51ea732af20d52a66685
Closing as fixed