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

Newegg Daily Deals

Reply
 
Thread Tools
Old 09-27-10, 05:34 PM   #1
jnorthco
Registered User
 
Join Date: Sep 2010
Posts: 3
Default Kernel oops from vdpau mplayer in 256.35

Hi,

I'm attempting to use a Quadro NVS 420 to run 4 separate screens, with a separate mplayer process on each screen playing a VDPAU-accelerated video.

This regularly causes the kernel to oops with a null pointer dereference in the middle of the nvidia driver. The machine in question locks hard, even the SysRq key has no effect.

I was able to get logs of the oops using the netconsole module, the syslog on the machine in question usually ends up corrupt since I have to physically remove power in order to reboot the machine.

I've included a couple of crash logs, and the nvidia-bug-report file. I've also tried an earlier 195 series driver with basically the same results.

If I turn off VDPAU in mplayer, and use CPU decoding, everything seems to play fine.

mplayer is using this command line, once per screen:

mplayer -quiet -fixed-vo -ac null -vo vdpau,xv -vc ffmpeg12vdpau,ffh264vdpau,ffwmv3vdpau,ffvc1vdpau, -ss 0 -zoom 1920x1080+0+0 /path/to/video

Right now, the problem is always reproducible - as soon as I start the mplayers, the system crashes immediately, before I even see one frame of video.

Please let me know if there is any other information I can provide, or if there is anything else I should try.

James
Attached Files
File Type: txt nvidia-kernel-oops.txt (13.2 KB, 114 views)
File Type: bz2 nvidia-bug-report.log.bz2 (96.2 KB, 83 views)
jnorthco is offline   Reply With Quote
Old 09-27-10, 06:12 PM   #2
Stephen Warren
Moderator
 
Stephen Warren's Avatar
 
Join Date: Aug 2005
Posts: 1,327
Default Re: Kernel oops from vdpau mplayer in 256.35

Thanks for the information. I have filed a bug report to investigate this. In the meantime, can you please try our latest release, 260.19.06, to see if this problem has already been fixed. Thanks.
Stephen Warren is offline   Reply With Quote
Old 09-29-10, 11:42 AM   #3
jnorthco
Registered User
 
Join Date: Sep 2010
Posts: 3
Default Re: Kernel oops from vdpau mplayer in 256.35

The most recent 260.19 shows the same problem for me. Oddly, this seems most likely to happen immediately following a reboot, if I delay starting X for a while after bootup sometimes mplayer starts correctly.

[ 37.549477] BUG: unable to handle kernel NULL pointer dereference at (null)
[ 37.549497] IP: [<f0761e80>] _nv000919rm+0x4/0x7 [nvidia]
[ 37.549638] *pde = bfa3f067
[ 37.549644] Oops: 0000 [#1] SMP
[ 37.549656] last sysfs file: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/0000:02:02.0/0000:04:00.0/class
[ 37.549662] Modules linked in: tun snd_hda_codec_analog lp snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd psmouse soundcore nvidia(P) iptable_filter ip_tables serio_raw snd_page_alloc dell_wmi netconsole ppdev x_tables shpchp configfs parport_pc parport dcdbas usbhid intel_agp e1000e agpgart
[ 37.549736]
[ 37.549740] Pid: 2094, comm: mplayer Tainted: P (2.6.31-14-generic #48-Ubuntu) OptiPlex 780
[ 37.549744] EIP: 0060:[<f0761e80>] EFLAGS: 00010286 CPU: 1
[ 37.549865] EIP is at _nv000919rm+0x4/0x7 [nvidia]
[ 37.549868] EAX: 00000000 EBX: 00000000 ECX: ee0dd800 EDX: 00000000
[ 37.549872] ESI: 00000000 EDI: f0e69b00 EBP: ea475248 ESP: ea7c5c3c
[ 37.549877] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[ 37.549881] Process mplayer (pid: 2094, ti=ea7c4000 task=ea696480 task.ti=ea7c4000)
[ 37.549886] Stack:
[ 37.549888] f07622d6 eab43000 00000000 ea475eb0 ee9bb240 ee0dd800 f0762f1e eab43000[ 37.550431] [<f075e2dd>] ? _nv023910rm+0x72/0x85 [nvidia]
[ 37.550551] [<f075ee94>] ? _nv023925rm+0x33/0x14c [nvidia]
[ 37.550722] [<f0a5ae0c>] ? _nv018989rm+0x2e1/0x96e [nvidia]
[ 37.550890] [<f0a51bad>] ? _nv018967rm+0x95/0xd5 [nvidia]
[ 37.551033] [<f0b6c769>] ? _nv002164rm+0x59/0x81 [nvidia]
[ 37.551176] [<f0b719d9>] ? rm_isr_bh+0x52/0x7d [nvidia]
[ 37.551327] [<f0b8c76b>] ? nv_kern_isr_bh+0x3b/0x80 [nvidia]
[ 37.551333] [<c014a217>] ? tasklet_action+0xa7/0xc0
[ 37.551339] [<c014b3b0>] ? __do_softirq+0x90/0x1a0
[ 37.551343] [<c018f8fc>] ? handle_IRQ_event+0x4c/0x140
[ 37.551351] [<c0121270>] ? ack_apic_level+0x60/0x230
[ 37.551354] [<c014b4fd>] ? do_softirq+0x3d/0x40
[ 37.551357] [<c014b63d>] ? irq_exit+0x5d/0x70
[ 37.551362] [<c0104f10>] ? do_IRQ+0x50/0xc0
[ 37.551529] [<f09c80e2>] ? _nv014699rm+0x40/0x75 [nvidia]
[ 37.551696] [<f09c2378>] ? _nv014787rm+0x6b/0x75 [nvidia]
[ 37.551700] [<c01039b0>] ? common_interrupt+0x30/0x40
[ 37.551843] [<f0b7007b>] ? _nv003590rm+0x80/0x88 [nvidia]
[ 37.551848] [<c0570920>] ? _spin_unlock_irqrestore+0x10/0x20
[ 37.551992] [<f0b919e4>] ? os_release_sema+0x44/0x80 [nvidia]
[ 37.552136] [<f0b680f5>] ? _nv021921rm+0x9/0x12 [nvidia]
[ 37.552251] [<f071b2a0>] ? _nv003336rm+0x223/0x22f [nvidia]
[ 37.552254] [<f071b2cb>] ? _nv002080rm+0x1f/0x23 [nvidia]
[ 37.552254] [<f070379d>] ? _nv001764rm+0x2b/0x4e [nvidia]
[ 37.552254] [<f0b74edf>] ? _nv002162rm+0x4e7/0x520 [nvidia]
[ 37.552254] [<f0b71a42>] ? rm_ioctl+0x3e/0x6d [nvidia]
[ 37.552254] [<f0b8f87d>] ? nv_kern_ioctl+0x14d/0x480 [nvidia]
[ 37.552254] [<c01338fd>] ? __enqueue_entity+0x9d/0xc0
[ 37.552254] [<c01333fa>] ? set_next_entity+0x12a/0x160
[ 37.552254] [<f0b8fbfb>] ? nv_kern_unlocked_ioctl+0x1b/0x30 [nvidia]
[ 37.552254] [<f0b8fbe0>] ? nv_kern_unlocked_ioctl+0x0/0x30 [nvidia]
[ 37.552254] [<c01f4c9c>] ? vfs_ioctl+0x1c/0x90
[ 37.552254] [<c01f4fc1>] ? do_vfs_ioctl+0x71/0x310
[ 37.552254] [<c01f52bf>] ? sys_ioctl+0x5f/0x80
[ 37.552254] [<c010336c>] ? syscall_call+0x7/0xb
[ 37.552254] [<c020462a>] ? change_mnt_propagation+0xca/0x1e0
[ 37.552254] Code: da 0f b6 42 0f 8b 4c 24 18 88 04 19 0f b6 45 03 88 42 0f 43 83 fb 07 76 d7 b8 00 00 00 00 83 c5 18 5b 5e 5f c3 90 90 8b 44 24 08 <8b> 00 c3 8b 54 24 0c 8b 44 24 08 89 10 c3 8b 54 24 04 8b 44 24
[ 37.552254] EIP: [<f0761e80>] _nv000919rm+0x4/0x7 [nvidia] SS:ESP 0068:ea7c5c3c
[ 37.552254] CR2: 0000000000000000
[ 37.553510] ---[ end trace eba9e85d267af804 ]---
[ 37.553514] Kernel panic - not syncing: Fatal exception in interrupt
[ 37.553518] Pid: 2094, comm: mplayer Tainted: P D 2.6.31-14-generic #48-Ubuntu
[ 37.553522] Call Trace:
[ 37.553526] [<c056e41c>] ? printk+0x18/0x1c
[ 37.553534] [<c056e360>] panic+0x43/0xe7
[ 37.553538] [<c0571765>] oops_end+0xc5/0xd0
[ 37.553543] [<c0128ad4>] no_context+0xb4/0xd0
[ 37.553546] [<c0128b2d>] __bad_area_nosemaphore+0x3d/0x1a0
[ 37.553550] [<c056fab5>] ? schedule_hrtimeout_range+0x135/0x150
[ 37.553553] [<c0127c38>] ? default_spin_lock_flags+0x8/0x10
[ 37.553556] [<c05707da>] ? _spin_lock_irqsave+0x2a/0x40
[ 37.553560] [<c015c5ab>] ? add_wait_queue+0x3b/0x50
[ 37.553566] [<c01f64e0>] ? __pollwait+0x60/0xd0
[ 37.553572] [<c0128ca2>] bad_area_nosemaphore+0x12/0x20
[ 37.553576] [<c0572ea6>] do_page_fault+0x2f6/0x380
[ 37.553580] [<c04897de>] ? pci_conf1_read+0xbe/0xf0
[ 37.553585] [<c0572bb0>] ? do_page_fault+0x0/0x380
[ 37.553590] [<c0570be3>] error_code+0x73/0x80
[ 37.553702] [<f07100d8>] ? _nv021079rm+0x8a/0xc9 [nvidia]
[ 37.553821] [<f0761e80>] ? _nv000919rm+0x4/0x7 [nvidia]
[ 37.553942] [<f07622d6>] ? _nv018553rm+0x5b/0x1b0 [nvidia]
[ 37.554061] [<f0762f1e>] ? _nv005140rm+0x372/0x759 [nvidia]
[ 37.554181] [<f075e58d>] ? _nv023923rm+0x37/0xe7 [nvidia]
[ 37.554301] [<f075e2dd>] ? _nv023910rm+0x72/0x85 [nvidia]
[ 37.554422] [<f075ee94>] ? _nv023925rm+0x33/0x14c [nvidia]
[ 37.554590] [<f0a5ae0c>] ? _nv018989rm+0x2e1/0x96e [nvidia]
[ 37.554756] [<f0a51bad>] ? _nv018967rm+0x95/0xd5 [nvidia]
[ 37.554902] [<f0b6c769>] ? _nv002164rm+0x59/0x81 [nvidia]
[ 37.555044] [<f0b719d9>] ? rm_isr_bh+0x52/0x7d [nvidia]
[ 37.555185] [<f0b8c76b>] ? nv_kern_isr_bh+0x3b/0x80 [nvidia]
[ 37.555188] [<c014a217>] ? tasklet_action+0xa7/0xc0
[ 37.555194] [<c014b3b0>] ? __do_softirq+0x90/0x1a0
[ 37.555199] [<c018f8fc>] ? handle_IRQ_event+0x4c/0x140
[ 37.555203] [<c0121270>] ? ack_apic_level+0x60/0x230
[ 37.555207] [<c014b4fd>] ? do_softirq+0x3d/0x40
[ 37.555215] [<c014b63d>] ? irq_exit+0x5d/0x70
[ 37.555219] [<c0104f10>] ? do_IRQ+0x50/0xc0
[ 37.555385] [<f09c80e2>] ? _nv014699rm+0x40/0x75 [nvidia]
[ 37.555551] [<f09c2378>] ? _nv014787rm+0x6b/0x75 [nvidia]
[ 37.555555] [<c01039b0>] ? common_interrupt+0x30/0x40
[ 37.555697] [<f0b7007b>] ? _nv003590rm+0x80/0x88 [nvidia]
[ 37.555700] [<c0570920>] ? _spin_unlock_irqrestore+0x10/0x20
[ 37.555842] [<f0b919e4>] ? os_release_sema+0x44/0x80 [nvidia]
[ 37.555985] [<f0b680f5>] ? _nv021921rm+0x9/0x12 [nvidia]
[ 37.556098] [<f071b2a0>] ? _nv003336rm+0x223/0x22f [nvidia]
[ 37.556210] [<f071b2cb>] ? _nv002080rm+0x1f/0x23 [nvidia]
[ 37.556319] [<f070379d>] ? _nv001764rm+0x2b/0x4e [nvidia]
[ 37.556474] [<f0b74edf>] ? _nv002162rm+0x4e7/0x520 [nvidia]
[ 37.556622] [<f0b71a42>] ? rm_ioctl+0x3e/0x6d [nvidia]
[ 37.556770] [<f0b8f87d>] ? nv_kern_ioctl+0x14d/0x480 [nvidia]
[ 37.556776] [<c01338fd>] ? __enqueue_entity+0x9d/0xc0
[ 37.556781] [<c01333fa>] ? set_next_entity+0x12a/0x160
[ 37.556922] [<f0b8fbfb>] ? nv_kern_unlocked_ioctl+0x1b/0x30 [nvidia]
[ 37.557066] [<f0b8fbe0>] ? nv_kern_unlocked_ioctl+0x0/0x30 [nvidia]
[ 37.557071] [<c01f4c9c>] ? vfs_ioctl+0x1c/0x90
[ 37.557074] [<c01f4fc1>] ? do_vfs_ioctl+0x71/0x310
[ 37.557079] [<c01f52bf>] ? sys_ioctl+0x5f/0x80
[ 37.557084] [<c010336c>] ? syscall_call+0x7/0xb
[ 37.557087] [<c020462a>] ? change_mnt_propagation+0xca/0x1e0
jnorthco is offline   Reply With Quote
Old 10-04-10, 12:04 PM   #4
Stephen Warren
Moderator
 
Stephen Warren's Avatar
 
Join Date: Aug 2005
Posts: 1,327
Default Re: Kernel oops from vdpau mplayer in 256.35

Thanks. I added that new information to the bug report.
Stephen Warren is offline   Reply With Quote
Old 12-09-10, 06:04 AM   #5
sandipt
NVIDIA Corporation
 
sandipt's Avatar
 
Join Date: Dec 2010
Posts: 260
Default Re: Kernel oops from vdpau mplayer in 256.35

Hello jnorthco,
I can't repro this issue with ubuntu 9.10 with 4 monitors with separate X server.
I tried playing video with latest mplayer with ubutu 9.10 OS with command specified by you.

When playing mpeg video on 4 screens one this I observed is that CPU utilization is going very high 99% with "Compiz" desktop effect.
Video playing was very slow . For "None" Basic desktop effect there is no any issue.


Please provide more information :

- Are you still facing this issue ? If yes! then Repro. steps in details
- Set : System > Preferences > Appearance > Visual Effects (tab) > None. and Let us know issue repro OR not ?
- Mplayer version and downloaded URL
- What type of cables you are using to connect 4 monitors to graphics card i.e. DVI, DP etc.... ?
- CD/DVD or Video file type i.e. mpeg. avi etc....

Last edited by sandipt; 12-11-10 at 11:18 AM. Reason: more info
sandipt is offline   Reply With Quote
Old 01-12-11, 06:01 AM   #6
sandipt
NVIDIA Corporation
 
sandipt's Avatar
 
Join Date: Dec 2010
Posts: 260
Default Re: Kernel oops from vdpau mplayer in 256.35

Hi jnorthco,
Can you provide requested details ?
sandipt is offline   Reply With Quote
Old 01-18-11, 12:20 PM   #7
Stephen Warren
Moderator
 
Stephen Warren's Avatar
 
Join Date: Aug 2005
Posts: 1,327
Default Re: Kernel oops from vdpau mplayer in 256.35

Unfortunately, we haven't been able to reproduce this problem internally. Due to this, we have closed the internal issue report and are not actively investigating it further.
Stephen Warren 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 01:43 PM.


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