270.41.03 does not work with MSI interrupts

[djgera]

Loading module with NVreg_EnableMSI=1. No issues with previous version (260.19.29). I can remember some time ago was happens something similar issue with one driver version a was fixed.

Only x86_64 tested at this time.

nvidia 0000:01:00.0: setting latency timer to 64
NVRM: loading NVIDIA UNIX x86_64 Kernel Module  270.41.03  Sat Apr  9 00:06:19 PDT 2011
nvidia 0000:01:00.0: irq 42 for MSI/MSI-X
do_IRQ: 0.121 No irq handler for vector (irq -1)
do_IRQ: 0.121 No irq handler for vector (irq -1)
NVRM: RmInitAdapter failed! (0x12:0x2b:1716)
NVRM: rm_init_adapter(0) failed

[mooninite]

It must be specific to your hardware. I'm on 270.41.03 and MSI is still working for me on several systems.

 54:       6278     423188          0          0   PCI-MSI-edge      nvidia

[artem]

It also works here:

 61:       1532          0          0          0   PCI-MSI-edge      nvidia
OpenGL version string: 3.3.0 NVIDIA 270.41.03

[kwizart]

Works here too,

You often need a full reboot because the previous module might not be able to release the msi.
A patch was reported on this forum to fix the msi release on module unload with recent kernel.

Hopefully this was added to this new driver

[artem]

BTW, does (using) MSI make any difference?

[zbiggy]

Originally Posted by artem

BTW, does (using) MSI make any difference?

MSI is more stable and safe than traditional PIC or APIC. And it offloads PIC's/APIC's interrupt less than 16/24 so other devices which are not MSI capable can use it.

Of course hardware/driver implementation of MSI must be bug free. For example my Geforce 8200 mainboard supports well MSI for onboard SATA, Ethernet and audio. The only device which hangs after minutes of use in MSI mode is Geforce 8200 integrated GPU. I do not know if this is GPU hw failure or Nvidia binary driver is buggy.

[djgera]

Originally Posted by kwizart

Works here too,

You often need a full reboot because the previous module might not be able to release the msi.
A patch was reported on this forum to fix the msi release on module unload with recent kernel.

Hopefully this was added to this new driver

Thanks. Doing a full reboot/reset the system, works fine again.