Bug 679979

Summary: [NVa8] Nouveau test day image causes graphics card to become unstable across reboots and OS's
Product: [Fedora] Fedora Reporter: Dan Weber <danweber>
Component: xorg-x11-drv-nouveauAssignee: Ben Skeggs <bskeggs>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: airlied, ajax, bskeggs
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 15:32:57 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:
Description Flags
output of /var/log/messages
none
output of dmesg
none
xorg log
none
output of rendercheck test
none
Fedora 15 Alpha Boot Log none

Description Dan Weber 2011-02-24 01:25:49 UTC
Description of problem:
Using nouveau from the nouveau test day live cd causes a kernel panic. No graphics after rebooting into Fedora 13 from the hard disk with nvidia binary driver. Unstable graphics (no boot screen/corrupt boot screen/no graphics period on three different reboots in a row) with the nouveau driver in Fedora 13. 

Version-Release number of selected component (if applicable):
From live cd found here: http://fedoraproject.org/wiki/Test_Day%3A2011-02-22_Nouveau

How reproducible:
Run livecd, boots into gnome-fallback. Let it sit for a while and the kernel panics. 


Additional info:
Grabbed from /var/log/messages when the nvidia driver died:
Feb 23 19:54:42 dan-thinkpad kernel: vmap allocation for size 16781312 failed: use vmalloc=<size> to increase size.
Feb 23 19:54:42 dan-thinkpad kernel: NVRM: failed to map registers!!
Feb 23 19:54:42 dan-thinkpad kernel: NVRM: RmInitAdapter failed! (0x10:0x32:1312)
Feb 23 19:54:42 dan-thinkpad kernel: NVRM: rm_init_adapter(0) failed

Comment 1 Dan Weber 2011-02-24 01:27:20 UTC
Oops, forgot the ever-important hardware description. Lenovo thinkpad t410 with nvidia nvs quadro 3100.

Comment 2 Ben Skeggs 2011-02-24 03:37:06 UTC
I don't see how the vmalloc failure of the NVIDIA binary driver can possibly be related.  You're running a 32-bit kernel, and NVIDIA GPUs have *massive* amounts of register space.  With a lot of devices, the kernel will quickly run out of places to map them.

The corrupt graphics with nouveau on reboot are more than likely the older version of nouveau not being able to deal with some residual state the new version sets up, that a warm reset does not fix.

Anyhow, are you able to capture some information on the kernel panic you're seeing, as well as dmesg output and /var/log/Xorg.0.log before it panics.

Comment 3 Dan Weber 2011-03-01 04:43:26 UTC
For the OS on my hard drive (Fedora 13):
I've got the nvidia binary working again, but only for one kernel on my system. It fails for one, and isn't available for the other. Nouveau doesn't work on any right now. When I boot nouveau, it never boots it graphical. Although it changes the resolution and does display the pretty shutdown screen (not the pretty boot one though).

For Fedora 15 test day live cd:
Seems to work for a while but intermittently locks up. I haven't seen the kernel panic since the first time, but every time it boots I get 'BIT loadval' errors, like Bug 630765. I've attached the output of /var/log/messages, dmesg, and Xorg.0.log. I also managed to get both rendercheck to run and test xv one time (it worked), so I have that as well.

Comment 4 Dan Weber 2011-03-01 04:47:20 UTC
Created attachment 481505 [details]
output of /var/log/messages

Comment 5 Dan Weber 2011-03-01 04:47:51 UTC
Created attachment 481506 [details]
output of dmesg

Comment 6 Dan Weber 2011-03-01 04:52:03 UTC
Created attachment 481508 [details]
xorg log

Comment 7 Dan Weber 2011-03-01 04:52:35 UTC
Created attachment 481509 [details]
output of rendercheck test

Comment 8 Dan Weber 2011-03-20 01:11:44 UTC
Just tried out the Fedora 15 Alpha 64-bit live cd. No crashes yet, but same error. I attached the new boot log. Also, I've been getting some graphical glitches occasionally. A few examples: parts of text missing, like someone dragged the eraser through the middle of a line of text and also the gnome login window having different blocks of dark gradient over its normally light background.

Comment 9 Dan Weber 2011-03-20 01:13:47 UTC
Created attachment 486428 [details]
Fedora 15 Alpha Boot Log

Comment 10 Fedora End Of Life 2012-08-07 15:32:59 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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" (top right of this page) 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