Bug 1003314 - xorg-x11-drv-nouveau crashes system
xorg-x11-drv-nouveau crashes system
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau (Show other bugs)
19
x86_64 Linux
unspecified Severity urgent
: ---
: ---
Assigned To: Ben Skeggs
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-01 17:51 EDT by Daniel
Modified: 2013-09-02 02:38 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-09-02 02:38:56 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Daniel 2013-09-01 17:51:31 EDT
Description of problem:
After running a system update (yum update) of xorg-x11-drv-nouveau-1.0.7-1 to current xorg-x11-drv-nouveau-1.0.9-1 my system crashes a few minutes after reaching graphic welcome screen or logging in as user. The system is then forced to reboot.

No whatsoever traces in logs. Only found in /var/log/messages some binary symbols which are all zeros when viewing it with xxd.

My graphic card is

[root@bl4ckh0l3 ~]# lspci |grep -i VGA
02:00.0 VGA compatible controller: NVIDIA Corporation G92 [GeForce 9800 GT] (rev a2)

The system worked fine with all previous versions of Fedora and nouveau driver (F17 and F19, skipped F18).

Steps to Reproduce:
1. Install xorg-x11-drv-nouveau-1.0.9-1 or later
2. boot system
3. a few moments (sometimes a bit longer) system will be forced to reboot
   without warning.
4. After reboot the same misery.


Additional info:

Last functioning version: xorg-x11-drv-nouveau-1.0.7-1

Definitely broken versions: xorg-x11-drv-nouveau-1.0.9-1 and 1.0.9-2

No results for versions between 1.0.7-1 and 1.0.9-1
Comment 1 Daniel 2013-09-02 02:38:56 EDT
Random system crashes persist, even with older versions of xorg-x11-drv-nouveau. No logs.

Note You need to log in before you can comment on or make changes to this bug.