Random video hangs after upgrading from 290.10 to 295.9 and 295.17

PhoenixUT · 02-09-12, 10:40 AM

I use VDPAU on an 8600GT to accelerate video decoding within MythTV. With the 290.xx series of drivers I was been having intermittent application crashes so when I saw that the 295.9 beta drivers had a fix for the multithread OpenGL issue I upgraded.

The driver no longer crashes, but occasionally when seeking/starting video playback in MythTV the video will lock up entirely. The system is still up and running, the cursor moves, and I can ssh into the machine and kill the X server. After removing the nvidia module, and reinserting it I am able to start X and have video working again. This never happened in the 290.xx series. I have tried both the 295.9 and 295.17 beta releases, and both exhibit the same issue.

All of the failures coincide with a similar output to the kernel log:

nvidia 0000:07:00.0: irq 50 for MSI/MSI-X
irq 50: nobody cared (try booting with the "irqpoll" option)
Pid: 0, comm: swapper Tainted: P 3.1.1 #5
Call Trace:
[<c1065fe1>] ? __report_bad_irq+0x21/0xc0
[<c106619e>] ? note_interrupt+0x11e/0x1d0
[<fac712ff>] ? nv_kern_isr+0x2f/0x70 [nvidia]
[<c1064626>] ? handle_irq_event_percpu+0x66/0x140
[<c1067d52>] ? irq_move_masked_irq+0x82/0xb0
[<c1066840>] ? irq_check_poll+0x20/0x20
[<c106472c>] ? handle_irq_event+0x2c/0x50
[<c1066840>] ? irq_check_poll+0x20/0x20
[<c1066894>] ? handle_edge_irq+0x54/0xd0
<IRQ> [<c1003ead>] ? do_IRQ+0x3d/0xc0
[<c1037091>] ? irq_exit+0x31/0xa0
[<c1019e11>] ? smp_apic_timer_interrupt+0x51/0x90
[<c1277e69>] ? common_interrupt+0x29/0x30
[<fa6500d8>] ? _nv014109rm+0xa3/0x1d0 [nvidia]
[<fac53fde>] ? rm_check_pci_config_space+0x1b6/0xe19 [nvidia]
[<c1004675>] ? handle_irq+0x15/0x90
[<c1003eb6>] ? do_IRQ+0x46/0xc0
[<c1037091>] ? irq_exit+0x31/0xa0
[<c1019e11>] ? smp_apic_timer_interrupt+0x51/0x90
[<c1037270>] ? irq_enter+0x60/0x60
[<c1277e69>] ? common_interrupt+0x29/0x30
[<fac7291a>] ? nv_kern_isr_bh+0x7a/0x80 [nvidia]
[<c1036b23>] ? tasklet_action+0x83/0x90
[<c10372e0>] ? __do_softirq+0x70/0xf0
[<c1037270>] ? irq_enter+0x60/0x60
<IRQ> [<c10370ce>] ? irq_exit+0x6e/0xa0
[<c1003eb6>] ? do_IRQ+0x46/0xc0
[<c1019e11>] ? smp_apic_timer_interrupt+0x51/0x90
[<c1277e69>] ? common_interrupt+0x29/0x30
[<c1009902>] ? mwait_idle+0x42/0x60
[<c1001bf4>] ? cpu_idle+0x54/0x90
[<c136c6c7>] ? start_kernel+0x26c/0x271
[<c136c299>] ? kernel_init+0x117/0x117
handlers:
[<fac712d0>] nv_kern_isr
Disabling IRQ #50
NVRM: Xid (0000:07:00): 16, Head 00000000 Count 001dd59e
nvidia 0000:07:00.0: PCI INT A disabled

I have attached the nvidia-bug-report file, but this file was generated after I had downgraded the driver back to the 290.10 version.

PhoenixUT · 02-13-12, 11:27 AM

Just wanted to provide a quick update.

After reverting back to the 290.10 driver, the crashes from libnvidia-tls.so are back, but I haven't had any issues with the ISR, and unhandled interrupts after downgrading.

If there's any more information I can provide that would be useful just let me know.

PhoenixUT · 02-25-12, 12:28 PM

I updated to 295.20 once it was released and things were looking good for a while, but I just had the same unhandled IRQ issue again last night. It happened while watching/seeking in a H.264 encoded video through MythTV. After killing the X server, removing the kernel module and reinserting it, I was able to restart X and watch the same video just fine. If you have any suggestions or need more info, please feel free to ask.

Here is a snippet from the kernel log:

Code:

irq 50: nobody cared (try booting with the "irqpoll" option)
Pid: 0, comm: swapper Tainted: P            3.1.1 #5
Call Trace:
 [<c1065fe1>] ? __report_bad_irq+0x21/0xc0
 [<c106619e>] ? note_interrupt+0x11e/0x1d0
 [<fac72bff>] ? nv_kern_isr+0x2f/0x70 [nvidia]
 [<c1064626>] ? handle_irq_event_percpu+0x66/0x140
 [<c1067d52>] ? irq_move_masked_irq+0x82/0xb0
 [<c1066840>] ? irq_check_poll+0x20/0x20
 [<c106472c>] ? handle_irq_event+0x2c/0x50
 [<c1066840>] ? irq_check_poll+0x20/0x20
 [<c1066894>] ? handle_edge_irq+0x54/0xd0
 <IRQ>  [<c1003ead>] ? do_IRQ+0x3d/0xc0
 [<c1037091>] ? irq_exit+0x31/0xa0
 [<c1019e11>] ? smp_apic_timer_interrupt+0x51/0x90
 [<c1037270>] ? irq_enter+0x60/0x60
 [<c1277e69>] ? common_interrupt+0x29/0x30
 [<c1037270>] ? irq_enter+0x60/0x60
 [<c10372ae>] ? __do_softirq+0x3e/0xf0
 [<c1037270>] ? irq_enter+0x60/0x60
 <IRQ>  [<c10370ce>] ? irq_exit+0x6e/0xa0
 [<c1003eb6>] ? do_IRQ+0x46/0xc0
 [<c104f1e0>] ? hrtimer_start+0x20/0x30
 [<c1277e69>] ? common_interrupt+0x29/0x30
 [<c1009902>] ? mwait_idle+0x42/0x60
 [<c1001bf4>] ? cpu_idle+0x54/0x90
 [<c136c6c7>] ? start_kernel+0x26c/0x271
 [<c136c299>] ? kernel_init+0x117/0x117
handlers:
[<fac72bd0>] nv_kern_isr
Disabling IRQ #50
sky2 0000:03:00.0: eth1: rx error, status 0x7ffc0001 length 168
NVRM: Xid (0000:07:00): 8, Channel 00000004
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: Xid (0000:07:00): 16, Head 00000000 Count 01378862

PhoenixUT · 02-26-12, 03:52 PM

Here's another failure, same symptoms, similar kernel log.

This ISR problem never occurred with the 290.xx series of driver. It appears a regression of some sort has been introduced in the 295.xx series. This is rather unfortunate since I have been suffering from the multi-threaded OpenGL segmentation faults with 290.xx and previous versions of the drivers.

Code:

irq 50: nobody cared (try booting with the "irqpoll" option)
Pid: 0, comm: swapper Tainted: P            3.1.1 #5
Call Trace:
 [<c1065fe1>] ? __report_bad_irq+0x21/0xc0
 [<c106619e>] ? note_interrupt+0x11e/0x1d0
 [<f8a72bff>] ? nv_kern_isr+0x2f/0x70 [nvidia]
 [<c1064626>] ? handle_irq_event_percpu+0x66/0x140
 [<c1067d52>] ? irq_move_masked_irq+0x82/0xb0
 [<c1066840>] ? irq_check_poll+0x20/0x20
 [<c106472c>] ? handle_irq_event+0x2c/0x50
 [<c1066840>] ? irq_check_poll+0x20/0x20
 [<c1066894>] ? handle_edge_irq+0x54/0xd0
 <IRQ>  [<c1003ead>] ? do_IRQ+0x3d/0xc0
 [<c1037091>] ? irq_exit+0x31/0xa0
 [<c1019e11>] ? smp_apic_timer_interrupt+0x51/0x90
 [<c1037270>] ? irq_enter+0x60/0x60
 [<c1277e69>] ? common_interrupt+0x29/0x30
 [<c1037270>] ? irq_enter+0x60/0x60
 [<c10200d8>] ? vmalloc_fault+0x128/0x180
 [<c10372ae>] ? __do_softirq+0x3e/0xf0
 [<c1037270>] ? irq_enter+0x60/0x60
 <IRQ>  [<c10370ce>] ? irq_exit+0x6e/0xa0
 [<c1003eb6>] ? do_IRQ+0x46/0xc0
 [<c1277e69>] ? common_interrupt+0x29/0x30
 [<c1009902>] ? mwait_idle+0x42/0x60
 [<c1001bf4>] ? cpu_idle+0x54/0x90
 [<c136c6c7>] ? start_kernel+0x26c/0x271
 [<c136c299>] ? kernel_init+0x117/0x117
handlers:
[<f8a72bd0>] nv_kern_isr
Disabling IRQ #50
NVRM: Xid (0000:07:00): 8, Channel 00000003
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: Xid (0000:07:00): 8, Channel 0000007e
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: Xid (0000:07:00): 8, Channel 00000003
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
nvidia 0000:07:00.0: PCI INT A disabled

PhoenixUT · 03-06-12, 01:42 PM

Any suggestions or feedback on this sighting?

I really am at a loss as to what I can do to further debug these hangs. I have verified that the problem exists in all 295.xx releases and does not occur at all in the 290.xx releases. Please let me know if there is any further info that would be of help.

PhoenixUT · 03-19-12, 11:08 AM

Still suffering random VDPAU hangs in the kernel ISR when using the 295.xx series drivers. Any insight woudl be greatly appreciated. Please request any additional information that may be helpful. The only thing that the hangs seem to be related to is seeking while watching video in MythTV. When a hang occurs the video freezes before jumping to the new location (after the seek).

Code:

irq 50: nobody cared (try booting with the "irqpoll" option)
Pid: 11019, comm: mythcommflag Tainted: P            3.1.1 #5
Call Trace:
 [<c1065fe1>] ? __report_bad_irq+0x21/0xc0
 [<c106619e>] ? note_interrupt+0x11e/0x1d0
 [<f604ebff>] ? nv_kern_isr+0x2f/0x70 [nvidia]
 [<c1064626>] ? handle_irq_event_percpu+0x66/0x140
 [<c1067d52>] ? irq_move_masked_irq+0x82/0xb0
 [<c1066840>] ? irq_check_poll+0x20/0x20
 [<c106472c>] ? handle_irq_event+0x2c/0x50
 [<c1066840>] ? irq_check_poll+0x20/0x20
 [<c1066894>] ? handle_edge_irq+0x54/0xd0
 <IRQ>  [<c1003ead>] ? do_IRQ+0x3d/0xc0
 [<c1037091>] ? irq_exit+0x31/0xa0
 [<c1019e11>] ? smp_apic_timer_interrupt+0x51/0x90
 [<c1037270>] ? irq_enter+0x60/0x60
 [<c1277e69>] ? common_interrupt+0x29/0x30
 [<c1037270>] ? irq_enter+0x60/0x60
 [<c10372b3>] ? __do_softirq+0x43/0xf0
 [<c1037270>] ? irq_enter+0x60/0x60
 <IRQ>  [<c10370ce>] ? irq_exit+0x6e/0xa0
 [<c1003eb6>] ? do_IRQ+0x46/0xc0
 [<c1037091>] ? irq_exit+0x31/0xa0
 [<c1019e11>] ? smp_apic_timer_interrupt+0x51/0x90
 [<c1277e69>] ? common_interrupt+0x29/0x30
handlers:
[<f604ebd0>] nv_kern_isr
Disabling IRQ #50
NVRM: Xid (0000:07:00): 16, Head 00000000 Count 011fcce6
nvidia 0000:07:00.0: PCI INT A disabled

alan242 · 03-25-12, 04:38 PM

Well, in your original post, your bug report shows there's problems with your X setup. Specifically,

[3235440.663] (WW) Warning, couldn't open module dri
[3235440.663] (II) UnloadModule: "dri"
[3235440.663] (II) Unloading dri
[3235440.663] (EE) Failed to load module "dri" (module does not exist, 0)
[3235440.663] (II) LoadModule: "dri2"
[3235440.663] (WW) Warning, couldn't open module dri2
[3235440.663] (II) UnloadModule: "dri2"
[3235440.663] (II) Unloading dri2
[3235440.663] (EE) Failed to load module "dri2" (module does not exist, 0)

[3235442.928] (WW) NVIDIA(0): The EDID for Mitsubishi MEUSPTV10 (DFP-0) contradicts itself:
[3235442.928] (WW) NVIDIA(0): mode "1920x1080" is specified in the EDID; however, the
[3235442.928] (WW) NVIDIA(0): EDID's valid VertRefresh range (59.000-61.000 Hz) would
[3235442.928] (WW) NVIDIA(0): exclude this mode's VertRefresh (30.0 Hz); ignoring
[3235442.928] (WW) NVIDIA(0): VertRefresh check for mode "1920x1080".

[3235443.093] (WW) NVIDIA(0): Option "TwinViewXineramaInfoOrder" requested "CRT", but no
[3235443.093] (WW) NVIDIA(0): such display device could be found, or all display devices
[3235443.093] (WW) NVIDIA(0): by that name are currently unavailable.
[3235443.093] (WW) NVIDIA(0): Option "TwinViewXineramaInfoOrder" requested "TV", but no such
[3235443.093] (WW) NVIDIA(0): display device could be found, or all display devices by
[3235443.093] (WW) NVIDIA(0): that name are currently unavailable.

and lastly

[3235443.094] (EE) NVIDIA: Failed to load module "dri2" (module does not exist, 0)
[3235443.094] (II) NVIDIA(0): The X server will not be able to send the VDPAU driver name to
[3235443.094] (II) NVIDIA(0): libvdpau.

So you need to figure out what's causing those issues.

Once your X setup is cleaned up and there are no more warnings or errors in the log, if you still have the problem, you may need to disable MSI interrupts. Either the motherboard or the video card might be having problems with using that interrupt mechanism. To disable MSI, you'll need to pass the parm NVreg_EnableMSI=0 to the nvidia kernel driver.

PhoenixUT · 03-25-12, 05:57 PM

Quote:

Originally Posted by alan242

Well, in your original post, your bug report shows there's problems with your X setup. Specifically,

[3235440.663] (WW) Warning, couldn't open module dri
[3235440.663] (II) UnloadModule: "dri"
[3235440.663] (II) Unloading dri
[3235440.663] (EE) Failed to load module "dri" (module does not exist, 0)
[3235440.663] (II) LoadModule: "dri2"
[3235440.663] (WW) Warning, couldn't open module dri2
[3235440.663] (II) UnloadModule: "dri2"
[3235440.663] (II) Unloading dri2
[3235440.663] (EE) Failed to load module "dri2" (module does not exist, 0)

The DRI modules are not used by the nvidia blob driver (except recently to present some VDPAU API naming interface), and are not necessary. I have never loaded the DRI modules and did not have the ISR problems until upgrading to the 295.xx driver series.

The README for the driver installation also indicates that the DRI module should be removed from the X configuration.

Code:

Remove the following lines:

    Load "dri"
    Load "GLCore"

Quote:

[3235442.928] (WW) NVIDIA(0): The EDID for Mitsubishi MEUSPTV10 (DFP-0) contradicts itself:
[3235442.928] (WW) NVIDIA(0): mode "1920x1080" is specified in the EDID; however, the
[3235442.928] (WW) NVIDIA(0): EDID's valid VertRefresh range (59.000-61.000 Hz) would
[3235442.928] (WW) NVIDIA(0): exclude this mode's VertRefresh (30.0 Hz); ignoring
[3235442.928] (WW) NVIDIA(0): VertRefresh check for mode "1920x1080".

I have no problems with the resolution or refresh rate being used. The message here is just an indication that the EDID information that the display is providing is inconsistent with itself. As indicated in the message, the driver is behaving sanely and just ignoring the VertRefresh range which is incorrect.

Quote:

[3235443.093] (WW) NVIDIA(0): Option "TwinViewXineramaInfoOrder" requested "CRT", but no
[3235443.093] (WW) NVIDIA(0): such display device could be found, or all display devices
[3235443.093] (WW) NVIDIA(0): by that name are currently unavailable.
[3235443.093] (WW) NVIDIA(0): Option "TwinViewXineramaInfoOrder" requested "TV", but no such
[3235443.093] (WW) NVIDIA(0): display device could be found, or all display devices by
[3235443.093] (WW) NVIDIA(0): that name are currently unavailable.

I am not using Xinerama and these messages have no relevance to my setup.

Quote:

[3235443.094] (EE) NVIDIA: Failed to load module "dri2" (module does not exist, 0)
[3235443.094] (II) NVIDIA(0): The X server will not be able to send the VDPAU driver name to
[3235443.094] (II) NVIDIA(0): libvdpau.

Again, this is the message regarding the naming interface for VDPAU, but the DRI modules are not necessary and the driver functions correctly without loading the DRI extensions.

Quote:

Once your X setup is cleaned up and there are no more warnings or errors in the log, if you still have the problem, you may need to disable MSI interrupts. Either the motherboard or the video card might be having problems with using that interrupt mechanism. To disable MSI, you'll need to pass the parm NVreg_EnableMSI=0 to the nvidia kernel driver.

I have been using MSI interrupts ever since I began using this video card without problems (until upgrading to 295.xx). I am reporting a regression in the 295.xx series driver. MSI interrupts worked perfectly fine with all driver series prior to 295.xx. I need to upgrade to 295.xx to avoid segmentation faults related to OpenGL multithreading in the 290.xx driver series, that were fixed in the 295.xx series.

PhoenixUT · 04-03-12, 03:46 PM

ISR hangs are still happening with the 295.33 drivers.

Code:

irq 50: nobody cared (try booting with the "irqpoll" option)
Pid: 0, comm: swapper Tainted: P            3.1.1 #5
Call Trace:
 [<c1065fe1>] ? __report_bad_irq+0x21/0xc0
 [<c106619e>] ? note_interrupt+0x11e/0x1d0
 [<f604adbf>] ? nv_kern_isr+0x2f/0x70 [nvidia]
 [<c1064626>] ? handle_irq_event_percpu+0x66/0x140
 [<c1067d52>] ? irq_move_masked_irq+0x82/0xb0
 [<c1066840>] ? irq_check_poll+0x20/0x20
 [<c106472c>] ? handle_irq_event+0x2c/0x50
 [<c1066840>] ? irq_check_poll+0x20/0x20
 [<c1066894>] ? handle_edge_irq+0x54/0xd0
 <IRQ>  [<c1003ead>] ? do_IRQ+0x3d/0xc0
 [<c1037091>] ? irq_exit+0x31/0xa0
 [<c1019e11>] ? smp_apic_timer_interrupt+0x51/0x90
 [<c1037270>] ? irq_enter+0x60/0x60
 [<c1277e69>] ? common_interrupt+0x29/0x30
 [<c1037270>] ? irq_enter+0x60/0x60
 [<c10372ae>] ? __do_softirq+0x3e/0xf0
 [<c1037270>] ? irq_enter+0x60/0x60
 <IRQ>  [<c10370ce>] ? irq_exit+0x6e/0xa0
 [<c1003eb6>] ? do_IRQ+0x46/0xc0
 [<c1019e11>] ? smp_apic_timer_interrupt+0x51/0x90
 [<c1277e69>] ? common_interrupt+0x29/0x30
 [<c1009902>] ? mwait_idle+0x42/0x60
 [<c1001bf4>] ? cpu_idle+0x54/0x90
 [<c136c6c7>] ? start_kernel+0x26c/0x271
 [<c136c299>] ? kernel_init+0x117/0x117
handlers:
[<f604ad90>] nv_kern_isr
Disabling IRQ #50
NVRM: Xid (0000:07:00): 8, Channel 00000003
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: Xid (0000:07:00): 8, Channel 00000001
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: Xid (0000:07:00): 8, Channel 00000001
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: Xid (0000:07:00): 8, Channel 00000001
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context

PhoenixUT · 04-18-12, 04:23 PM

Two more ISR hangs. I'll try upgrading to 295.40 but I don't have high hopes. There is no mention of any related fix, and none of the past 295.xx updates have helped.

It would be good to know if there are any more debug options that could be added to provide more information used to root cause this problem. It seems these reports are falling on deaf ears...

Code:

irq 50: nobody cared (try booting with the "irqpoll" option)
Pid: 1894, comm: lircd Tainted: P            3.1.1 #8
Call Trace:
 [<c1065fe1>] ? __report_bad_irq+0x21/0xc0
 [<c106619e>] ? note_interrupt+0x11e/0x1d0
 [<f54e7dbf>] ? nv_kern_isr+0x2f/0x70 [nvidia]
 [<c1064626>] ? handle_irq_event_percpu+0x66/0x140
 [<c1066840>] ? irq_check_poll+0x20/0x20
 [<c106472c>] ? handle_irq_event+0x2c/0x50
 [<c1066840>] ? irq_check_poll+0x20/0x20
 [<c1066894>] ? handle_edge_irq+0x54/0xd0
 <IRQ>  [<c1003ead>] ? do_IRQ+0x3d/0xc0
 [<c1037091>] ? irq_exit+0x31/0xa0
 [<c1019e11>] ? smp_apic_timer_interrupt+0x51/0x90
 [<c1037270>] ? irq_enter+0x60/0x60
 [<c12841e9>] ? common_interrupt+0x29/0x30
 [<c1037270>] ? irq_enter+0x60/0x60
 [<c10372ae>] ? __do_softirq+0x3e/0xf0
 [<c1037270>] ? irq_enter+0x60/0x60
 <IRQ>  [<c10370ce>] ? irq_exit+0x6e/0xa0
 [<c1003eb6>] ? do_IRQ+0x46/0xc0
 [<c1036990>] ? sys_gettimeofday+0x30/0x80
 [<c12841e9>] ? common_interrupt+0x29/0x30
handlers:
[<f54e7d90>] nv_kern_isr
Disabling IRQ #50
NVRM: Xid (0000:07:00): 8, Channel 00000005
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
nvidia 0000:07:00.0: irq 50 for MSI/MSI-X
nvidia 0000:07:00.0: PCI INT A disabled

Code:

nvidia 0000:07:00.0: enabling device (0002 -> 0003)
nvidia 0000:07:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
nvidia 0000:07:00.0: setting latency timer to 64
vgaarb: device changed decodes: PCI:0000:07:00.0,olddecodes=none,decodes=none:owns=io+mem
NVRM: loading NVIDIA UNIX x86 Kernel Module  295.33  Sat Mar 17 14:56:23 PDT 2012
nvidia 0000:07:00.0: irq 50 for MSI/MSI-X
NVRM: Xid (0000:07:00): 28, CCMDs 00000006 00007476 00000610 00000000 00000000
NVRM: Xid (0000:07:00): 28, CCMDs 00000006 00007476 00000610 00000000 00000000
NVRM: Xid (0000:07:00): 28, CCMDs 00000007 00007476 00000400 54530201 00000000
irq 50: nobody cared (try booting with the "irqpoll" option)
Pid: 31941, comm: mythfrontend Tainted: P            3.1.1 #8
Call Trace:
 [<c1065fe1>] ? __report_bad_irq+0x21/0xc0
 [<f3c4a6ac>] ? mvs_94xx_isr+0x5c/0x120 [mvsas]
 [<c106619e>] ? note_interrupt+0x11e/0x1d0
 [<fac6edbf>] ? nv_kern_isr+0x2f/0x70 [nvidia]
 [<c1064626>] ? handle_irq_event_percpu+0x66/0x140
 [<c1066840>] ? irq_check_poll+0x20/0x20
 [<c106472c>] ? handle_irq_event+0x2c/0x50
 [<c1066840>] ? irq_check_poll+0x20/0x20
 [<c1066894>] ? handle_edge_irq+0x54/0xd0
 <IRQ>  [<c1003ead>] ? do_IRQ+0x3d/0xc0
 [<c1037091>] ? irq_exit+0x31/0xa0
 [<c1019e11>] ? smp_apic_timer_interrupt+0x51/0x90
 [<c1037270>] ? irq_enter+0x60/0x60
 [<c12841e9>] ? common_interrupt+0x29/0x30
 [<c1037270>] ? irq_enter+0x60/0x60
 [<c10372ae>] ? __do_softirq+0x3e/0xf0
 [<c1037270>] ? irq_enter+0x60/0x60
 <IRQ>  [<c10370ce>] ? irq_exit+0x6e/0xa0
 [<c1003eb6>] ? do_IRQ+0x46/0xc0
 [<c1037091>] ? irq_exit+0x31/0xa0
 [<c1019e11>] ? smp_apic_timer_interrupt+0x51/0x90
 [<c12841e9>] ? common_interrupt+0x29/0x30
handlers:
[<fac6ed90>] nv_kern_isr
Disabling IRQ #50
NVRM: Xid (0000:07:00): 16, Head 00000000 Count 00125a77
nvidia 0000:07:00.0: irq 50 for MSI/MSI-X
NVRM: Xid (0000:07:00): 28, CCMDs 00000007 00007476 00000400 54530201 00000000
NVRM: Xid (0000:07:00): 28, CCMDs 00000006 00007476 00000610 00000000 00000000
irq 50: nobody cared (try booting with the "irqpoll" option)
Pid: 32212, comm: mythfrontend Tainted: P            3.1.1 #8
Call Trace:
 [<c1065fe1>] ? __report_bad_irq+0x21/0xc0
 [<c106619e>] ? note_interrupt+0x11e/0x1d0
 [<fac6edbf>] ? nv_kern_isr+0x2f/0x70 [nvidia]
 [<c1064626>] ? handle_irq_event_percpu+0x66/0x140
 [<c1066840>] ? irq_check_poll+0x20/0x20
 [<c106472c>] ? handle_irq_event+0x2c/0x50
 [<c1066840>] ? irq_check_poll+0x20/0x20
 [<c1066894>] ? handle_edge_irq+0x54/0xd0
 <IRQ>  [<c1003ead>] ? do_IRQ+0x3d/0xc0
 [<c1037091>] ? irq_exit+0x31/0xa0
 [<c1019e11>] ? smp_apic_timer_interrupt+0x51/0x90
 [<c1037270>] ? irq_enter+0x60/0x60
 [<c12841e9>] ? common_interrupt+0x29/0x30
 [<c1037270>] ? irq_enter+0x60/0x60
 [<c10372ae>] ? __do_softirq+0x3e/0xf0
 [<c1037270>] ? irq_enter+0x60/0x60
 <IRQ>  [<c10370ce>] ? irq_exit+0x6e/0xa0
 [<c1003eb6>] ? do_IRQ+0x46/0xc0
 [<c12841e9>] ? common_interrupt+0x29/0x30
handlers:
[<fac6ed90>] nv_kern_isr
Disabling IRQ #50
NVRM: Xid (0000:07:00): 8, Channel 00000004
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: Xid (0000:07:00): 16, Head 00000000 Count 000021e2
nvidia 0000:07:00.0: PCI INT A disabled
nvidia 0000:07:00.0: enabling device (0002 -> 0003)
nvidia 0000:07:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
nvidia 0000:07:00.0: setting latency timer to 64
vgaarb: device changed decodes: PCI:0000:07:00.0,olddecodes=none,decodes=none:owns=io+mem
NVRM: loading NVIDIA UNIX x86 Kernel Module  295.33  Sat Mar 17 14:56:23 PDT 2012
nvidia 0000:07:00.0: irq 50 for MSI/MSI-X
NVRM: Xid (0000:07:00): 28, CCMDs 00000007 00007476 00000400 54530201 00000000

PhoenixUT · 04-19-12, 01:07 AM

Same problem still occurring with 295.40.

Code:

NVRM: loading NVIDIA UNIX x86 Kernel Module  295.40  Thu Apr  5 21:28:09 PDT 2012
nvidia 0000:07:00.0: irq 50 for MSI/MSI-X
nvidia 0000:07:00.0: irq 50 for MSI/MSI-X
irq 50: nobody cared (try booting with the "irqpoll" option)
Pid: 1894, comm: lircd Tainted: P            3.1.1 #8
Call Trace:
 [<c1065fe1>] ? __report_bad_irq+0x21/0xc0
 [<c106619e>] ? note_interrupt+0x11e/0x1d0
 [<fac73e9f>] ? nv_kern_isr+0x2f/0x70 [nvidia]
 [<c1064626>] ? handle_irq_event_percpu+0x66/0x140
 [<c1066840>] ? irq_check_poll+0x20/0x20
 [<c106472c>] ? handle_irq_event+0x2c/0x50
 [<c1066840>] ? irq_check_poll+0x20/0x20
 [<c1066894>] ? handle_edge_irq+0x54/0xd0
 <IRQ>  [<c1003ead>] ? do_IRQ+0x3d/0xc0
 [<c1037091>] ? irq_exit+0x31/0xa0
 [<c1019e11>] ? smp_apic_timer_interrupt+0x51/0x90
 [<c1037270>] ? irq_enter+0x60/0x60
 [<c12841e9>] ? common_interrupt+0x29/0x30
 [<c1037270>] ? irq_enter+0x60/0x60
 [<c10372ae>] ? __do_softirq+0x3e/0xf0
 [<c1037270>] ? irq_enter+0x60/0x60
 <IRQ>  [<c10370ce>] ? irq_exit+0x6e/0xa0
 [<c1003eb6>] ? do_IRQ+0x46/0xc0
 [<c1036990>] ? sys_gettimeofday+0x30/0x80
 [<c12841e9>] ? common_interrupt+0x29/0x30
handlers:
[<fac73e70>] nv_kern_isr
Disabling IRQ #50
nvidia 0000:07:00.0: PCI INT A disabled
nvidia 0000:07:00.0: enabling device (0002 -> 0003)
nvidia 0000:07:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
nvidia 0000:07:00.0: setting latency timer to 64
vgaarb: device changed decodes: PCI:0000:07:00.0,olddecodes=none,decodes=none:owns=io+mem
NVRM: loading NVIDIA UNIX x86 Kernel Module  295.40  Thu Apr  5 21:28:09 PDT 2012
nvidia 0000:07:00.0: irq 50 for MSI/MSI-X
nvidia 0000:07:00.0: irq 50 for MSI/MSI-X

PhoenixUT · 04-20-12, 11:32 AM

And another.. 2 months, and still not even a sign that this is being investigated.

Code:

NVRM: Xid (0000:07:00): 28, CCMDs 00000006 00007476 00000610 00000000 00000000
irq 50: nobody cared (try booting with the "irqpoll" option)
Pid: 0, comm: swapper Tainted: P            3.1.1 #8
Call Trace:
 [<c1065fe1>] ? __report_bad_irq+0x21/0xc0
 [<c106619e>] ? note_interrupt+0x11e/0x1d0
 [<f9a74e9f>] ? nv_kern_isr+0x2f/0x70 [nvidia]
 [<c1064626>] ? handle_irq_event_percpu+0x66/0x140
 [<c1066840>] ? irq_check_poll+0x20/0x20
 [<c106472c>] ? handle_irq_event+0x2c/0x50
 [<c1066840>] ? irq_check_poll+0x20/0x20
 [<c1066894>] ? handle_edge_irq+0x54/0xd0
 <IRQ>  [<c1003ead>] ? do_IRQ+0x3d/0xc0
 [<c1037091>] ? irq_exit+0x31/0xa0
 [<c1019e11>] ? smp_apic_timer_interrupt+0x51/0x90
 [<c1037270>] ? irq_enter+0x60/0x60
 [<c12841e9>] ? common_interrupt+0x29/0x30
 [<c1037270>] ? irq_enter+0x60/0x60
 [<c10200d8>] ? vmalloc_fault+0x128/0x180
 [<c10372ae>] ? __do_softirq+0x3e/0xf0
 [<c1037270>] ? irq_enter+0x60/0x60
 <IRQ>  [<c10370ce>] ? irq_exit+0x6e/0xa0
 [<c1003eb6>] ? do_IRQ+0x46/0xc0
 [<c1019e11>] ? smp_apic_timer_interrupt+0x51/0x90
 [<c12841e9>] ? common_interrupt+0x29/0x30
 [<c1009902>] ? mwait_idle+0x42/0x60
 [<c1001bf4>] ? cpu_idle+0x54/0x90
 [<c137d6c7>] ? start_kernel+0x26c/0x271
 [<c137d299>] ? kernel_init+0x117/0x117
handlers:
[<f9a74e70>] nv_kern_isr
Disabling IRQ #50
NVRM: Xid (0000:07:00): 8, Channel 00000004
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: Xid (0000:07:00): 16, Head 00000000 Count 00071073
nvidia 0000:07:00.0: PCI INT A disabled
nvidia 0000:07:00.0: enabling device (0002 -> 0003)
nvidia 0000:07:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
nvidia 0000:07:00.0: setting latency timer to 64
vgaarb: device changed decodes: PCI:0000:07:00.0,olddecodes=none,decodes=none:owns=io+mem
NVRM: loading NVIDIA UNIX x86 Kernel Module  295.40  Thu Apr  5 21:28:09 PDT 2012
nvidia 0000:07:00.0: irq 50 for MSI/MSI-X

02-13-12, 11:27 AM	#2
PhoenixUT Registered User Join Date: Oct 2004 Posts: 11	Re: Random video hangs after upgrading from 290.10 to 295.9 and 295.17 Just wanted to provide a quick update. After reverting back to the 290.10 driver, the crashes from libnvidia-tls.so are back, but I haven't had any issues with the ISR, and unhandled interrupts after downgrading. If there's any more information I can provide that would be useful just let me know.

03-25-12, 04:38 PM	#7
alan242 Registered User Join Date: Sep 2006 Posts: 20	Re: Random video hangs after upgrading from 290.10 to 295.9 and 295.17 Well, in your original post, your bug report shows there's problems with your X setup. Specifically, [3235440.663] (WW) Warning, couldn't open module dri [3235440.663] (II) UnloadModule: "dri" [3235440.663] (II) Unloading dri [3235440.663] (EE) Failed to load module "dri" (module does not exist, 0) [3235440.663] (II) LoadModule: "dri2" [3235440.663] (WW) Warning, couldn't open module dri2 [3235440.663] (II) UnloadModule: "dri2" [3235440.663] (II) Unloading dri2 [3235440.663] (EE) Failed to load module "dri2" (module does not exist, 0) [3235442.928] (WW) NVIDIA(0): The EDID for Mitsubishi MEUSPTV10 (DFP-0) contradicts itself: [3235442.928] (WW) NVIDIA(0): mode "1920x1080" is specified in the EDID; however, the [3235442.928] (WW) NVIDIA(0): EDID's valid VertRefresh range (59.000-61.000 Hz) would [3235442.928] (WW) NVIDIA(0): exclude this mode's VertRefresh (30.0 Hz); ignoring [3235442.928] (WW) NVIDIA(0): VertRefresh check for mode "1920x1080". [3235443.093] (WW) NVIDIA(0): Option "TwinViewXineramaInfoOrder" requested "CRT", but no [3235443.093] (WW) NVIDIA(0): such display device could be found, or all display devices [3235443.093] (WW) NVIDIA(0): by that name are currently unavailable. [3235443.093] (WW) NVIDIA(0): Option "TwinViewXineramaInfoOrder" requested "TV", but no such [3235443.093] (WW) NVIDIA(0): display device could be found, or all display devices by [3235443.093] (WW) NVIDIA(0): that name are currently unavailable. and lastly [3235443.094] (EE) NVIDIA: Failed to load module "dri2" (module does not exist, 0) [3235443.094] (II) NVIDIA(0): The X server will not be able to send the VDPAU driver name to [3235443.094] (II) NVIDIA(0): libvdpau. So you need to figure out what's causing those issues. Once your X setup is cleaned up and there are no more warnings or errors in the log, if you still have the problem, you may need to disable MSI interrupts. Either the motherboard or the video card might be having problems with using that interrupt mechanism. To disable MSI, you'll need to pass the parm NVreg_EnableMSI=0 to the nvidia kernel driver.

03-06-12, 01:42 PM	#5
PhoenixUT Registered User Join Date: Oct 2004 Posts: 11	Re: Random video hangs after upgrading from 290.10 to 295.9 and 295.17 Any suggestions or feedback on this sighting? I really am at a loss as to what I can do to further debug these hangs. I have verified that the problem exists in all 295.xx releases and does not occur at all in the 290.xx releases. Please let me know if there is any further info that would be of help.