User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; fr; rv:1.9.2) Gecko/20100121 Remi/fc12 Firefox/3.6 X freezes the clock stopped, keyboard seemed not to be responding, every so often the mouse would track but no response to clicks. And the reboot hardware is an obligation, TTY couldn't functionnal Reproducible: Always Actual Results: The computer is not functionnal, hardware reboot to solve it I use nouVeau driver with 8800 GTS but it's totally functionnal with this card in my old computer
Created attachment 395297 [details] Xorg log in freeze
Comment on attachment 395297 [details] Xorg log in freeze Edit with the good error
Comment on attachment 395297 [details] Xorg log in freeze (II) NOUVEAU(0): Printing probed modes for output DVI-I-0 (II) NOUVEAU(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz) (II) NOUVEAU(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz) (II) NOUVEAU(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz) (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz) (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz) (II) NOUVEAU(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz) (II) NOUVEAU(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz) (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz) (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz) (II) NOUVEAU(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz) (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz) (II) NOUVEAU(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz) (II) NOUVEAU(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz) (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz) (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz) (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz) (II) NOUVEAU(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz) (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz) (II) NOUVEAU(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz) (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz) (II) NOUVEAU(0): EDID for output DVI-I-1 [mi] EQ overflowing. The server is probably stuck in an infinite loop. Backtrace: 0: /usr/bin/Xorg (xorg_backtrace+0x28) [0x49ec58] 1: /usr/bin/Xorg (mieqEnqueue+0x1f4) [0x49e624] 2: /usr/bin/Xorg (xf86PostMotionEventP+0xce) [0x4791ee] 3: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7ffddedd9000+0x516f) [0x7ffddedde16f] 4: /usr/bin/Xorg (0x400000+0x6c0d7) [0x46c0d7] 5: /usr/bin/Xorg (0x400000+0x1173c3) [0x5173c3] 6: /lib64/libpthread.so.0 (0x35e2c00000+0xf0f0) [0x35e2c0f0f0] 7: /lib64/libc.so.6 (ioctl+0x7) [0x35e24d6937] 8: /usr/lib64/libdrm.so.2 (drmIoctl+0x23) [0x35fd403383] 9: /usr/lib64/libdrm.so.2 (drmCommandWrite+0x1b) [0x35fd40360b] 10: /usr/lib64/libdrm_nouveau.so.1 (0x7ffde2235000+0x2f1d) [0x7ffde2237f1d] 11: /usr/lib64/libdrm_nouveau.so.1 (nouveau_bo_map_range+0xfc) [0x7ffde223811c] 12: /usr/lib64/xorg/modules/drivers/nouveau_drv.so (0x7ffde2471000+0xc0c9) [0x7ffde247d0c9] 13: /usr/lib64/xorg/modules/drivers/nouveau_drv.so (0x7ffde2471000+0xd390) [0x7ffde247e390] 14: /usr/lib64/xorg/modules/libexa.so (0x7ffde0016000+0x8308) [0x7ffde001e308] 15: /usr/bin/Xorg (0x400000+0x1534f4) [0x5534f4] 16: /usr/lib64/xorg/modules/libexa.so (exaGetPixmapFirstPixel+0xa9) [0x7ffde00250e9] 17: /usr/lib64/xorg/modules/libexa.so (0x7ffde0016000+0xe365) [0x7ffde0024365] 18: /usr/bin/Xorg (0x400000+0xd2460) [0x4d2460] 19: /usr/bin/Xorg (0x400000+0xcbbae) [0x4cbbae] 20: /usr/bin/Xorg (0x400000+0x2c7bc) [0x42c7bc] 21: /usr/bin/Xorg (0x400000+0x21d8a) [0x421d8a] 22: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x35e241eb1d] 23: /usr/bin/Xorg (0x400000+0x21949) [0x421949]
Does the keyboard "stop working" also running on runlevel 3 for a while? It seems that you have the same problem I've reported here: https://bugzilla.redhat.com/show_bug.cgi?id=560147
In Fedora 13, I have tested nouVeau and this bug is present. I have this error in /var/log/message, just before the bug : "Mar 28 15:48:52 localhost kernel: [drm] nouveau 0000:01:00.0: PFIFO_DMA_PUSHER - Ch 2" And, for information, I didn't have this bug with this video card (8800 GTS), nouVeau was perfect. But I have changed my motherboard, one ASUS P5Q SE2 and I have this bug since day. I have seen in Google, one option of BIOS can cause this bug with nouVeau… It's maybe the solution ?
Well, I have an ASUS too. It would be interesting knowing which one is the option according to what you've found.
Just a wild guess from another bug report, if there's options in your BIOS setup relating to PCI-E ASPM, try turning it off.
There is no such an option in my BIOS (AMI)
Can I see your dmesg output please :)
Created attachment 404047 [details] barbara's dmesg If you asked me, I've attached a fresh one.
Ben Skeggs, I don't have this option in BIOS. The modules for power in this BIOS are turned off since the start.
(In reply to comment #10) > Created an attachment (id=404047) [details] > barbara's dmesg > > If you asked me, I've attached a fresh one. This is a little worrying, not sure of the cause yet: "nouveau 0000:02:00.0: PCI: Disallowing DAC for device" For ASPM, give booting with "pcie_aspm=off" a try.
I tried this and it finally seems to have fixed the problem for me. I can start Xorg using nouveau now. Anyway I have to do some other tests to do, for example if it still locks on runlevel 3, as I did a lot of things including downgrading BIOS, change various options, etc. I've reported the same also in one of my previous bugs (560147).
Looks like my Clevo laptop is affected by this bug: Jun 13 17:49:59 localhost kernel: [drm] nouveau 0000:01:00.0: PFIFO_DMA_PUSHER - Ch 2 X is frozen, but you can still log in remotely and shutdown the machine cleanly. I'll try that pcie_aspm kernel option. Additionally my desktop machine at work had a X lockup which looks the same: X using 100% CPU, remote login still possible. But I get different DRM messages in the log: Jun 15 10:37:47 salit23 kernel: [drm] nouveau 0000:02:00.0: PGRAPH_TRAP - Ch 2/5 Class 0x8297 Mthd 0x0f04 Data 0x00000000:0x00000000 Jun 15 10:37:47 salit23 kernel: [drm] nouveau 0000:02:00.0: PGRAPH_TRAP_CCACHE_F AULT - VM: Trapped read at 00412a2000 status 00000560 00000000 channel 2 Jun 15 10:37:47 salit23 kernel: [drm] nouveau 0000:02:00.0: PGRAPH_TRAP_CCACHE_F AULT - 00000000 00000000 00000000 00000000 00000000 00000000 00000000 and dmesg says: Jun 15 10:49:24 salit23 kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it Is this related to the same issue? But if I interpret "dmesg" correctly pcie_aspm=off won't work on this system.
Just saw this again with kernel-2.6.33.5-124.fc13.x86_64, on a PCI-E box with pcie_aspm=off. Fortunately its fairly rare ATM.
(In reply to comment #14) > Looks like my Clevo laptop is affected by this bug: > > Jun 13 17:49:59 localhost kernel: [drm] nouveau 0000:01:00.0: PFIFO_DMA_PUSHER > - Ch 2 > > X is frozen, but you can still log in remotely and shutdown the machine > cleanly. I'll try that pcie_aspm kernel option. No lockups since I've added pcie_aspm=off. FYI: the laptop HW supports PCIe ASPM, but not Intel VT-d, i.e. intel_iommu=off would be ineffective (see Bug #561267).
Another sighting this morning with kernel-2.6.33.6-147.fc13.x86_64. X wedged but mouse tracks, ssh works but restarting X only revisits the error, full reboot needed to get X back. /var/log/messages says: Jul 14 10:42:02 riesling kernel: [drm] nouveau 0000:01:00.0: PFIFO_DMA_PUSHER - Ch 2 Jul 14 10:42:02 riesling kernel: [drm] nouveau 0000:01:00.0: PGRAPH_DATA_ERROR - Ch 2/5 Class 0x8297 Mthd 0x155c Data 0x00000000:0x00000000 Jul 14 10:42:02 riesling kernel: [drm] nouveau 0000:01:00.0: PGRAPH_DATA_ERROR - unknown value 0x0000000d Jul 14 10:42:02 riesling kernel: [drm] nouveau 0000:01:00.0: PGRAPH_DATA_ERROR - Ch 2/5 Class 0x8297 Mthd 0x1560 Data 0x00000000:0x412a3000 Jul 14 10:42:02 riesling kernel: [drm] nouveau 0000:01:00.0: PGRAPH_DATA_ERROR - unknown value 0x0000000d Jul 14 10:42:02 riesling kernel: [drm] nouveau 0000:01:00.0: PGRAPH_DATA_ERROR - Ch 2/5 Class 0x8297 Mthd 0x1564 Data 0x00000000:0x00000000 Jul 14 10:42:02 riesling kernel: [drm] nouveau 0000:01:00.0: PGRAPH_DATA_ERROR - unknown value 0x0000000d
Another sighting with some change: Jul 16 08:26:27 riesling kernel: [drm] nouveau 0000:01:00.0: PFIFO_DMA_PUSHER - Ch 2 Jul 16 08:26:42 riesling kernel: [drm] nouveau 0000:01:00.0: nouveau_channel_free: freeing fifo 2 Jul 16 08:26:45 riesling kernel: [drm] nouveau 0000:01:00.0: Failed to idle channel 2. Jul 16 08:26:45 riesling kernel: [drm] nouveau 0000:01:00.0: PFIFO_DMA_PUSHER - Ch 127 (The following is new behaviour, there was a KDE update the other day, looks like kdm is now more able to try to restart X. Certainly the screen did go blank which it did not before) Jul 16 08:26:45 riesling kdm[1943]: X server for display :0 terminated unexpectedly (However we get to here, and the new X is sitting at 95% CPU but the screen is as dead as ever. The GPU is wedged?) Jul 16 08:26:51 riesling kernel: [drm] nouveau 0000:01:00.0: Allocating FIFO number 2 Jul 16 08:26:51 riesling kernel: [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 2
Please try 2.6.34.2-34.fc13
I'm getting hit by this roughly every other week. kernel: 2.6.34.6-54.fc13.x86_64 Using gnome with metacity in compositing mode. Hang tends to appear when I'm using firefox, but that might just be coincidence. Haven't found any way to reproduce the issue. dmesg from two incidents: 1. [drm] nouveau 0000:01:00.0: PGRAPH_TRAP - Ch 2/5 Class 0x8297 Mthd 0x15e0 Data 0x00000000:0x00000000 [drm] nouveau 0000:01:00.0: PGRAPH_TRAP_TPDMA - no VM fault? [drm] nouveau 0000:01:00.0: PGRAPH_TRAP_TPDMA - TP0: Unhandled ustatus 0x00000008 [drm] nouveau 0000:01:00.0: PFIFO_DMA_PUSHER - Ch 2 [drm] nouveau 0000:01:00.0: PGRAPH_DATA_ERROR - Ch 2/5 Class 0x8297 Mthd 0x0fa4 Data 0x00000000:0x0008ae04 [drm] nouveau 0000:01:00.0: PGRAPH_DATA_ERROR - INVALID_BITFIELD [drm] nouveau 0000:01:00.0: PGRAPH_DATA_ERROR - Ch 2/5 Class 0x8297 Mthd 0x0fa8 Data 0x00000000:0x0151014d [drm] nouveau 0000:01:00.0: PGRAPH_DATA_ERROR - INVALID_VALUE 2. [drm] nouveau 0000:01:00.0: PFIFO_DMA_PUSHER - Ch 2 [drm] nouveau 0000:01:00.0: PGRAPH_DATA_ERROR - Ch 2/2 Class 0x502d Mthd 0x0220 Data 0x000000cf:0x00144230 [drm] nouveau 0000:01:00.0: PGRAPH_DATA_ERROR - INVALID_BITFIELD
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.