| Summary: | Graphics hang, nouveau PFIFO_DMA_PUSHER error MEM_FAULT | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dan Krejsa <dan.krejsa> | ||||||
| Component: | xorg-x11-drv-nouveau | Assignee: | Ben Skeggs <bskeggs> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 16 | CC: | airlied, ajax, bskeggs | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-02-13 12:48:09 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
I was able to reproduce the problem and obtain an ssh session to the host after it occurred. [In this case, I simply had the firefox browser open to this bugzilla page and was away from the computer when the hang occurred.] From the ssh session I tried to kill (SIGTERM) the gnome-session process with no visible effect; then with 'kill -9 ...' and successfully killed the gnome-session process. The screen stays frozen except for the mouse cursor. Killing /usr/bin/Xorg as root with SIGTERM also had no visible effect; killing it with SIGKILL allowed me to log in again on the laptop that had the problem. I've noticed an 'EQ overflowing' message and a backtrace in Xorg.0.log.old after this process, however I'm not sure it may have been the result of my messing about killing things. So, I'll try to reproduce the issue again and see what's in /Xorg.0.log without the killing. Created attachment 559095 [details]
Xorg.0.log.old after power cycling after the problem occurred. EQ overflowing.
From attached Xorg.0.log.old. Occurred using kernel 3.2.2-1.fc16.i686. Obtained after power cycling and rebooting; I didn't have ssh enabled this time and so wasn't able to obtain the backtrace before rebooting. [ 6798.274] [mi] EQ overflowing. The server is probably stuck in an infinite loop. [ 6798.275] Backtrace: [ 6798.275] 0: /usr/bin/Xorg (xorg_backtrace+0x3c) [0x80a863c] [ 6798.276] 1: /usr/bin/Xorg (mieqEnqueue+0x175) [0x81ac145] [ 6798.276] 2: /usr/bin/Xorg (0x8047000+0x43822) [0x808a822] [ 6798.276] 3: /usr/bin/Xorg (xf86PostMotionEventM+0xf2) [0x80dbb52] [ 6798.276] 4: /usr/bin/Xorg (xf86PostMotionEvent+0x99) [0x80dbd19] [ 6798.276] 5: /usr/lib/xorg/modules/input/synaptics_drv.so (0x130000+0x2a21) [0x132a21] [ 6798.276] 6: /usr/lib/xorg/modules/input/synaptics_drv.so (0x130000+0x4c4c) [0x134c4c] [ 6798.276] 7: /usr/bin/Xorg (0x8047000+0x7f5b0) [0x80c65b0] [ 6798.276] 8: /usr/bin/Xorg (0x8047000+0xa603b) [0x80ed03b] [ 6798.276] 9: (vdso) (__kernel_sigreturn+0x0) [0xe9c400] [ 6798.276] 10: (vdso) (__kernel_vsyscall+0x2) [0xe9c416] [ 6798.276] 11: /lib/libc.so.6 (ioctl+0x19) [0x45ef3639] [ 6798.276] 12: /usr/lib/libdrm.so.2 (drmIoctl+0x34) [0x47ca69a4] [ 6798.276] 13: /usr/lib/libdrm.so.2 (drmCommandWrite+0x3d) [0x47ca932d] [ 6798.276] 14: /usr/lib/libdrm_nouveau.so.1 (0xfb8000+0x2b8f) [0xfbab8f] [ 6798.276] 15: /usr/lib/libdrm_nouveau.so.1 (nouveau_bo_map_range+0x10a) [0xfbb28a] [ 6798.276] 16: /usr/lib/libdrm_nouveau.so.1 (nouveau_bo_map+0x33) [0xfbb383] [ 6798.277] 17: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0xba2000+0x547c) [0xba747c] [ 6798.277] 18: /usr/lib/xorg/modules/libexa.so (0x1f1000+0x3f69) [0x1f4f69] [ 6798.277] 19: /usr/lib/xorg/modules/libexa.so (0x1f1000+0x7450) [0x1f8450] [ 6798.277] 20: /usr/lib/xorg/modules/libexa.so (0x1f1000+0x11242) [0x202242] [ 6798.277] 21: /usr/lib/xorg/modules/libexa.so (0x1f1000+0xdf4e) [0x1fef4e] [ 6798.277] 22: /usr/bin/Xorg (0x8047000+0x10fb4f) [0x8156b4f] [ 6798.277] 23: /usr/bin/Xorg (CompositePicture+0x1db) [0x81496fb] [ 6798.277] 24: /usr/bin/Xorg (0x8047000+0x107cbb) [0x814ecbb] [ 6798.277] 25: /usr/bin/Xorg (0x8047000+0x102f74) [0x8149f74] [ 6798.277] 26: /usr/bin/Xorg (0x8047000+0x2f155) [0x8076155] [ 6798.277] 27: /usr/bin/Xorg (0x8047000+0x1d39a) [0x806439a] [ 6798.277] 28: /lib/libc.so.6 (__libc_start_main+0xf3) [0x45e226b3] [ 6798.277] 29: /usr/bin/Xorg (0x8047000+0x1d6c9) [0x80646c9] After the latest occurrence, screen artifacts started showing up at boot during BIOS and grub execution. So, it's quite possible that the issue is flaky hardware. Sigh. If you want to close this bug, it's OK with me. This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 558093 [details] Output from lspci -v Description of problem: A couple of times today, but not 100% reproducibly, gnome shell has hanged for me in a particular way: - Some subtle squiggles appear in a repetitive pattern all over the screen. - also, an odd pattern of squiggles were attached to the mouse and moved with the mouse. - The gui stops responding, except that the cursor still moves with the mouse. - No response to the keyboard, except that the squiggles may disappear after some action (e.g. ctrl-alt-del) - The system still responds to pings. I've not yet been able to reproduce it with an ssh session going to the target, however. - After giving up and powering down and rebooting, I see a message like the following just before the reboot: Jan 28 11:50:02 localhost kernel: [ 174.448221] [drm] nouveau 0000:01:00.0: PFIFO_DMA_PUSHER - Ch 3 Get 0x011d3798 Put 0x011d37a8 State 0xc0002054 (e rr: MEM_FAULT) Push 0x00000000 Jan 28 11:50:02 localhost kernel: [ 174.448232] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00010000 - Ch 3 This is on an up-to-date Fedora 16 system. Version-Release number of selected component (if applicable): xorg-x11-drv-nouveau-0.0.16-27.20110720gitb806e3f.fc16.i686 xorg-x11-server-Xorg-1.11.3-1.fc16.i686 Seen with kernels 3.2.1-3 and 3.1.9-1 Graphics controller is nVidia GeForce Go 7900 GS (see attached 'lspci -v' output). How reproducible: Not sure, happened on two successive reboots, but this reboot it hasn't happened yet. The steps to reproduce below are what I was doing when the result occurred, but are not guaranteed to reproduce the issue. Steps to Reproduce: 1. Open firefox, browse 2. Right click 3. ? Actual results: Hang and graphical glitch as described above Expected results: No hang Additional info: