Bug 868

Summary: [nvidia] X crashes randomly
Product: Fedora Reporter: Thomas R. <nethad>
Component: nvidia-kmodAssignee: Nicolas Chauvet <kwizart>
Status: RESOLVED FIXED    
Severity: normal CC: s.adam
Priority: P5    
Version: 11   
Hardware: i386   
OS: GNU/Linux   
namespace:
Attachments: nvidia-bug-report.log.gz

Description Thomas R. 2009-10-14 23:25:16 CEST
Hi,

for over a week or two now my X server crashes every now and then, I can't say which application is triggering it, but sometimes when I click the taskbar to show a specific window X crashes, the screen does show random colors for a second and then X aborts. The only thing I could find in the logs is:

[...]
(II) NVIDIA(0): Setting mode "nvidia-auto-select"                                                                          
(II) NVIDIA(0): Setting mode                                                                                               
(II) NVIDIA(0):     "CRT-0:nvidia-auto-select@1680x1050+0+0,DFP-0:nvidia-auto-select@1280x800+0+0"                         

Backtrace:
0: /usr/bin/X(xorg_backtrace+0x3b) [0x812d8eb]
1: /usr/bin/X(xf86SigHandler+0x9e) [0x80c0e0e]
2: [0x1fe400]                                 
3: /usr/lib/xorg/modules/drivers//nvidia_drv.so(_nv001647X+0x2b) [0xf7f5fb]

Fatal server error:
Caught signal 11.  Server aborting


Please consult the The X.Org Foundation support 
         at http://wiki.x.org                   
 for help.   
[...]

Is this any valuable information? Which other log file should I check?

My system:
Fedora 11, up to date with rpmfusion binary nvidia drivers.

$ lspci|grep VGA
01:00.0 VGA compatible controller: nVidia Corporation G72M [Quadro NVS 110M/GeForce Go 7300] (rev a1)

$ rpm -qa|grep  nvidia
xorg-x11-drv-nvidia-libs-185.18.36-3.fc11.i586
akmod-nvidia-185.18.36-1.fc11.i686
kmod-nvidia-2.6.30.8-64.fc11.i686.PAE-185.18.36-1.fc11.2.i686
xorg-x11-drv-nvidia-185.18.36-3.fc11.i586
kmod-nvidia-PAE-185.18.36-1.fc11.2.i686
kmod-nvidia-2.6.29.6-217.2.16.fc11.i686.PAE-185.18.36-1.fc11.i686

$ uname -r
2.6.29.6-217.2.16.fc11.i686.PAE

I can't use the 2.6.30.x kernels, because I'm suffering a 3D desktop effects bug there (effects are disabled, there are 2 bug reports in this DB already)
Comment 1 Thomas R. 2009-10-14 23:28:04 CEST
sorry for reposting, but: I am using KDE.
Comment 2 Nicolas Chauvet 2009-10-15 09:39:06 CEST
Can you attach the result of nvidia-bug-report.sh
Comment 3 Thomas R. 2009-10-15 13:09:54 CEST
Created attachment 304 [details]
nvidia-bug-report.log.gz
Comment 4 Nicolas Chauvet 2009-10-15 13:48:01 CEST
There is few things that cannot be supported in your system:

* ro root=/dev/mapper/vg_herbert-lv_root rhgb quiet vga=0x318
That line has loaded vesafb. But framebuffer support isn't really supported by nvidia, (so cannot be by us either). I'm asking you to remove that line and reboot before going any further.

* /var/log/message showed that you tried kmod 190.32 without rebooting.
Changing driver version without a reboot isn't really supported either.
According to the nvidia-installer.log, you seems to have removed the 190.32 driver appropriately.

On you have rebooted, and removed the grub line you can forward the new report to nvidia.

Geforce 7 can also be supported by the kmod-nvidia-173xx, you can it a try.

Comment 5 Thomas R. 2009-10-16 14:29:33 CEST
thanks for you help.

For a day now it does not crash, don't know if that grub option helped...
I do have another problem now, but I don't think it's related. I can't activate my KDE desktop effects, although direct rendering is OK:

$ glxinfo|grep direct
direct rendering: Yes
    GL_EXT_direct_state_access, GL_EXT_draw_range_elements, GL_EXT_fog_coord

And all the other 3D stuff I tested runs OK.
The problem could be that I have kde 4.2.2 packages from testing installed, but I as far as I remember they worked when I installed them. (meaning the effects worked).
Comment 6 Nicolas Chauvet 2009-11-01 23:39:49 CET
You seems to have the problem solved.
If not, please test the new driver in testing (190.42) and re-open the bug.