Red Hat Bugzilla – Bug 830402
X.org freezes randomly when using the nouveau driver
Last modified: 2013-07-31 17:50:25 EDT
Created attachment 590566 [details]
Errors in dmesg from when X froze
Description of problem:
X.org freezes at random times when using the nouveau graphics driver. It may be more likely to occur when using XVideo overlays. The "freeze" in this context means that X becomes completely unresponsive: mouse cursor doesn't move, keyboard doesn't work (can't even kill the X server), non-interactive things like video stopped playing, etc. The system is still alive, so I can log in remotely to kill -9 the X server. Even that didn't bring back the console. Could however recover it by doing the following from the remote ssh shell:
I also checked out dmesg, where I found a bunch of nouveau related error messages (see the attachment "nouveau_kernel_errors.txt").
Version-Release number of selected component (if applicable):
Typically takes a few hours between each crash.
Steps to Reproduce:
1. Use X normally.
Do not know if this is new in Fedora 17, because I used rpmfusion's kmod-nvidia in my past installation (which never caused any problems). I have now disabled nouveau and gone back to using kmod-nvidia, so I will probably not make any followups to this bug report, I posted it just to record the problem in case others experience the same thing.
Relevant hardware info:
Graphics card: NVIDIA GeForce GTX 280
Motherboard: Gigabyte GA-EX58-UD5
CPU: Intel i7-920
Even though the X server could be restarted (remotely) after SIGKILL'ing the frozen X server, nouveau kept spamming the kernel log with warnings. Always the same warning though:
Jun 9 09:19:18 snowbird kernel: [22891.677555] [drm] nouveau 0000:02:00.0: PFIFO_CACHE_ERROR - Ch 127/3 Mthd 0x1460 Data 0x00fc7460
Jun 9 09:19:18 snowbird kernel: [22891.677572] [drm] nouveau 0000:02:00.0: PFIFO_CACHE_ERROR - Ch 127/3 Mthd 0x1464 Data 0x00fc7460
Jun 9 09:19:18 snowbird kernel: [22891.677596] [drm] nouveau 0000:02:00.0: PFIFO_CACHE_ERROR - Ch 127/3 Mthd 0x1468 Data 0x00fc7460
Jun 9 09:19:18 snowbird kernel: [22891.677612] [drm] nouveau 0000:02:00.0: PFIFO_CACHE_ERROR - Ch 127/3 Mthd 0x146c Data 0x00fc7460
Jun 9 09:19:18 snowbird kernel: [22891.677636] [drm] nouveau 0000:02:00.0: PFIFO_CACHE_ERROR - Ch 127/3 Mthd 0x1470 Data 0x00fc7460
Jun 9 09:19:18 snowbird kernel: [22891.677652] [drm] nouveau 0000:02:00.0: PFIFO_CACHE_ERROR - Ch 127/3 Mthd 0x1474 Data 0x00fc7460
Same thing here, but I don't get the PFIFO_CACHE_ERROR messages. I don't
know if the machine is still alive or not, but it seems pretty dead to me.
Audio repeats in a ~1 second loop. Everything else seems dead. Cursor
doesn't move, clock doesn't update, num lock keyboard lights don't work
when the num lock key is pressed etc.
After a reboot, there's nothing in /var/log/messages from immediately
before the crash.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.
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 17'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 17 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 change the
'version' to a later Fedora version prior to Fedora 17's end of life.
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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.