Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 10-19-10, 03:02 AM   #1
artem
Registered User
 
Join Date: Jun 2006
Posts: 705
Question To NVIDIA developers, a strange bug, kernel guys blame you

Here's a bug which I'm unable to resolve and kernel developers claim it's a problem with the NVIDIA driver.

Please, look into it, I'm ready to provide any necessary information.

The error I get is:
Code:
(EE) NVIDIA(0): The NVIDIA kernel module does not appear to be receiving
(EE) NVIDIA(0):     interrupts generated by the NVIDIA graphics device
(EE) NVIDIA(0):     PCI:5:0:0.  Please see Chapter 8: Common Problems in the
(EE) NVIDIA(0):     README for additional information.
(EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
artem is offline   Reply With Quote
Old 10-19-10, 05:36 AM   #2
kwizart
Registered User
 
Join Date: Feb 2005
Location: Paris, France
Posts: 129
Default Re: To NVIDIA developers, a strange bug, kernel guys blame you

You can start to read the sticky If you have a problem, PLEASE read this first

Then start with the very lastest driver as 260.19.12.

Also, one option I usually tend to use more and more is :
options nvidia NVreg_EnableMSI=1 in /etc/modprobe.d/nvidia.conf
You might give it a try. (couldn't MSI be activated automatically in some cases ?)
kwizart is offline   Reply With Quote
Old 10-19-10, 06:42 AM   #3
artem
Registered User
 
Join Date: Jun 2006
Posts: 705
Default Re: To NVIDIA developers, a strange bug, kernel guys blame you

I already have NVreg_EnableMSI=1 in my modprobe configuration:

Code:
# grep -i nvidia /proc/interrupts
 42:       4021       3914       3563       2909   PCI-MSI-edge      nvidia
The newest driver also exhibit this problem.
Attached Files
File Type: gz nvidia-bug-report.log.gz (33.1 KB, 48 views)
artem is offline   Reply With Quote
Old 10-19-10, 07:36 AM   #4
AaronP
NVIDIA Corporation
 
AaronP's Avatar
 
Join Date: Mar 2005
Posts: 2,487
Default Re: To NVIDIA developers, a strange bug, kernel guys blame you

Interrupt routing is set up by the system BIOS and the kernel, and the driver has little to do with it so it's surprising that the kernel developers blame the driver. Have you tried disabling MSI?
AaronP is offline   Reply With Quote
Old 10-19-10, 07:40 AM   #5
artem
Registered User
 
Join Date: Jun 2006
Posts: 705
Default Re: To NVIDIA developers, a strange bug, kernel guys blame you

I will try and report back ASAP.

Thanks, AaronP, disabling MSI helped and now I'm able to load nvidia.ko module at anytime.

However my GPU now shares an interrupt with a USB controller:
Code:
grep -i nvidia /proc/interrupts
 16:         25         80         16        116   IO-APIC-fasteoi   ehci_hcd:usb1, nvidia
which I don't much like but I can live with.

Alan Cox said exactly this: "It's a non free driver only they have the source to all the parts so only they can debug it." And as expected the bug was closed as INVALID.

Last edited by artem; 10-19-10 at 07:57 AM. Reason: new info
artem is offline   Reply With Quote
Old 10-19-10, 08:57 AM   #6
dae
Registered User
 
Join Date: Jul 2004
Location: Sweden
Posts: 40
Default Re: To NVIDIA developers, a strange bug, kernel guys blame you

FYI, MSI stopped working for me when I switched from 260.19.06 to 260.19.12 (same kernel version). Something must've changed in the driver that broke it.
dae is offline   Reply With Quote
Old 10-19-10, 11:18 AM   #7
AaronP
NVIDIA Corporation
 
AaronP's Avatar
 
Join Date: Mar 2005
Posts: 2,487
Default Re: To NVIDIA developers, a strange bug, kernel guys blame you

I talked to our kernel guy and he said that MSI is notoriously problematic throughout the hardware and software stack, and he recommended that you just stick with traditional interrupts.
AaronP is offline   Reply With Quote
Old 10-19-10, 12:00 PM   #8
dae
Registered User
 
Join Date: Jul 2004
Location: Sweden
Posts: 40
Default Re: To NVIDIA developers, a strange bug, kernel guys blame you

AaronP, that's an interresting statement. I'm absolutely not question him, but I'd love to hear more.

I wasn't aware of any problems in the kernel (which I assume is what he means with "software stack"), and I have a number of devices using PCI MSI without any issues what so ever. Is it related to nvidia hardware only, or is it a more general problem?

I don't mind using legacy INTx interrupts, as I don't think the overhead from interrupt sharing (nvidia shares interrupt with USB controller) is anything I need to be concerned about; I'm only asking out of curiosity.
dae is offline   Reply With Quote

Old 10-19-10, 12:13 PM   #9
artem
Registered User
 
Join Date: Jun 2006
Posts: 705
Default Re: To NVIDIA developers, a strange bug, kernel guys blame you

Aaron, thanks for the information.

However it's kinda weird that I've been running MSI'ed nvidia.ko module for three years straight with no problems and this issue has surfaced only recently (I must mention that I swapped my PC half a year ago, but even with a new one I didn't have this problem at the beginning - but then it was a different kernel and nvidia driver version).
artem is offline   Reply With Quote
Old 10-24-10, 10:04 AM   #10
dura91
Registered User
 
Join Date: Aug 2009
Location: Near Paris France
Posts: 40
Default Re: To NVIDIA developers, a strange bug, kernel guys blame you

MSI stop working for me with driver 195.36.24 (195.36.31+ are too buggy for me) when I switch from kernel 2.6.35.4 to 2.6.35.7 or 2.6.36.

So there was a change in the kernel that make MSI not working anymore with nvidia driver.

MSI still working fine with other hardware.

AaronP : On my computer it's the contrary, it really works better with MSI enabled. With traditional interrupts I got after a few days :
Code:
kernel: [144397.974550] Disabling IRQ #16
and graphics start to be very slow until I unload and reload nvidia kernel module.
dura91 is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 12:28 AM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.