nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   Error detected 1 426, 260.19.06, loss of VDPAU v-sync on second monitor (http://www.nvnews.net/vbulletin/showthread.php?t=157915)

mocharhw 12-12-10 12:27 PM

Error detected 1 426, 260.19.06, loss of VDPAU v-sync on second monitor
 
I'm having a problem that I never experienced before. Sometimes mplayer will crash and seem to destroy the vdpau overlay presentation queue. I can tell because I lose vsync on my second monitor (using TwinView). Using the vdpau debug environment variables I see this when starting mplayer.

Code:

VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 1 426
VDPAU nvidia: Backtrace:
--: /usr/lib/vdpau/libvdpau_nvidia.so.1 [0xb3a44000] DSO load base
00: /usr/lib/vdpau/libvdpau_nvidia.so.1 [0xb3a692d8]
01: /usr/lib/vdpau/libvdpau_nvidia.so.1 [0xb3a651f8]
02: /usr/lib/vdpau/libvdpau_nvidia.so.1 [0xb3a5fd1c]

Using version 260.19.06 with a 9500GT card. Composite is disabled in xorg.conf. Is this issue fixed in the latest version of the driver? Thanks.

mocharhw 12-12-10 02:16 PM

Re: Error detected 1 426, 260.19.06, loss of VDPAU v-sync on second monitor
 
1 Attachment(s)
Answer my own question, the latest driver does not fix the problem. This seems to be related to a lot of different errors discussed in this forum.

mocharhw 12-13-10 02:28 AM

Re: Error detected 1 426, 260.19.06, loss of VDPAU v-sync on second monitor
 
256.xx doesn't have this problem but has massive 2D slowdowns elsewhere. 195.xx doesn't work with x server 1.9. Only 260.xx is having this problem but I can't go back to 256.xx. For now I'm using a script to call the vdpau sync variable to set to the television before starting smplayer. Please fix this bug.

Stephen Warren 12-13-10 02:03 PM

Re: Error detected 1 426, 260.19.06, loss of VDPAU v-sync on second monitor
 
mocharw, Can you please describe what causes MPlayer to crash in the first place; that will help us reproduce your problem.

Also, once MPlayer has crashed, does it actually exit the process, or is some failed process still hanging around by not working? If the MPlayer process is still running, this could cause the failure you're seeing. Perhaps try:

ps auxww|grep mplayer

after the crash and when you see the problem.

mocharhw 12-13-10 03:05 PM

Re: Error detected 1 426, 260.19.06, loss of VDPAU v-sync on second monitor
 
Stephen,

You have the same first thought as me. In each case when mplayer did crash it left behind a dead process, but I always made sure to killall mplayer and checked that they were all dead before testing again. It was actually some setting in smplayer that was causing mplayer to crash. Running the same videos with just mplayer was ok. I'm using an SVN mplayer by the way, but not at my box right now to give you all the details.

When smplayer caused mplayer to crash I recall it was always some error about the demuxer.

I've been running this exact same hardware and external monitors for the past year with drivers back to the 185.xx series without problems. What are some tests I can perform or traces I can run to determine what process is holding the overlay queue hostage? Thanks.

mocharhw 12-14-10 01:45 AM

Re: Error detected 1 426, 260.19.06, loss of VDPAU v-sync on second monitor
 
1 Attachment(s)
Okay, was able to reproduce in a more scientific manner. smplayer doesn't have anything to do with it. The problem seems to have something to do with vdpau and fullscreen and possibly twinview. The test below starts by rebooting machine and then ran mplayer to watch a 30 minute video. Everything was fine the first time around, then I started stopping and restarting mplayer and switching back and forth from fullscreen.

Getting error 1 2335 everytime I go fullscreen on my secondary monitor. After stopping and restarting mplayer and going fullscreen 3 times, it then started giving me the 1 426 error and at that point I permanently lose vsync on the secondary monitor, vdpau is always using blit queue at that point. Only way to temporarily fix is to reboot. I'm using the Ubuntu repo version of the nvidia driver, the very latest version made no difference.

Attaching an nvidia bug report log which was run after getting the results pasted below.

Note in the tests below, I'm simply running the command line "mplayer FILE", and my config file looks like this:

Code:

ao=pulse
vo=vdpau
vc=ffh264vdpau,ffmpeg12vdpau,ffwmv3vdpau,ffvc1vdpau,

Was seeing this at first, while still having vsync on second monitor:
Code:

MPlayer SVN-r32566-4.4.5 (C) 2000-2010 MPlayer Team
.
.
.
VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 1 2335  occurs when going to fullscreen

Started seeing this after losing vsync on second monitor:
Code:

VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 1 426  I know vdpau is using the blit queue when I start to see this error
A:  6.0 V:  6.0 A-V:  0.000 ct:  0.000 182/182  2%  5%  0.4% 0 0
  =====  PAUSE  =====
No bind found for key 'MOUSE_BTN0'.-MOUSE_BTN0_DBL                       
VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 1 2335 switched to fullscreen here

Saw this one time when switching to fullscreen on secondary monitor, same video file.
Code:

VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 1 426 it always starts with this one
A:  5.4 V:  5.4 A-V:  0.000 ct:  0.000 164/164  2%  6%  0.4% 0 0
  =====  PAUSE  =====
No bind found for key 'MOUSE_BTN0'.-MOUSE_BTN0_DBL                       
VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 1 2335
VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 2 666

[vdpau] Display preemption detected
[vdpau] Error when calling vdp_presentation_queue_block_until_surface_idle: The display was pre-empted, or a fatal error occurred.
VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 0 533
[vdpau] Error when calling vdp_video_mixer_render: An invalid handle value was provided.
[vdpau] Attempting to recover from preemption.
VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 1 426
VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 0 5751
[vdpau] Error when calling vdp_video_mixer_render: An invalid handle value was provided.
[vdpau] Recovered from display preemption.

Saw this when switching back and forth to fullscreen on primary monitor, same video file:
Code:

VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 1 426
A:  3.5 V:  3.5 A-V: -0.000 ct:  0.000 107/107  3%  4%  0.5% 0 0
VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 1 2335
VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 0 7757
VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 1 2335
VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 0 2324

[vdpau] Display preemption detected
[vdpau] Error when calling vdp_output_surface_create: The display was pre-empted, or a fatal error occurred.
VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 0 533
VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 0 533
[vdpau] Error when calling vdp_output_surface_create: An invalid handle value was provided.
VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 0 533
VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 0 533
[vdpau] Error when calling vdp_output_surface_create: An invalid handle value was provided.
VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 0 533
[vdpau] Error when calling vdp_presentation_queue_block_until_surface_idle: An invalid handle value was provided.
VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 0 533
[vdpau] Error when calling vdp_video_mixer_render: An invalid handle value was provided.
[vdpau] Attempting to recover from preemption.
VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 1 426
VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.06  Mon Sep 13 07:05:35 PDT 2010
VDPAU nvidia: Error detected 0 5751
[vdpau] Error when calling vdp_video_mixer_render: An invalid handle value was provided.
[vdpau] Recovered from display preemption.

Got this in dmesg at some point during the above problems:
Code:

[ 7326.104936] NVRM: Xid (0001:00): 13, 0004 00000000 0000502d 0000060c 00000258 00000040
[ 7737.247916] NVRM: Xid (0001:00): 13, 0004 00000000 0000502d 0000060c 00000400 00000040


mocharhw 12-16-10 03:05 AM

Re: Error detected 1 426, 260.19.06, loss of VDPAU v-sync on second monitor
 
Same problem with latest driver. It took awhile longer to happen this time. I was acutally able to watch about 1.5 hours of videos and switch them back and forth from fullscreen and back without problem. Then I opened another video and I started getting this error again.

Code:

VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  260.19.26  Sun Nov 28 22:58:32 PST 2010
VDPAU nvidia: Error detected 1 426


Stephen Warren 01-03-11 12:50 PM

Re: Error detected 1 426, 260.19.06, loss of VDPAU v-sync on second monitor
 
mocharhw,

Thanks for the detailed information. It sounds like there are two bugs:

1) When toggling full-screen/window, sometimes VDPAU experiences a fatal error.

2) When VDPAU experiences a fatal error, sometimes (or always), the overlay presentation queue is no longer available to subsequent application instances.

We have had a number of reports of both these issues, and do have internal bugs filed to reproduce and investigate/fix them. Unfortunately, we haven't yet been able to reproduce the issues, but will continue to try to do so.

mocharhw 01-03-11 01:34 PM

Re: Error detected 1 426, 260.19.06, loss of VDPAU v-sync on second monitor
 
Thanks for the update. Just to be clear, I only started experiencing this problem with x server 1.9 and nvidia 260.xx. I had this same hardware in service prior without any problems.

Is there anything I can do to help you debug?

Stephen Warren 01-10-11 10:42 AM

Re: Error detected 1 426, 260.19.06, loss of VDPAU v-sync on second monitor
 
There were a number of VDPAU-related changes made in the 260 series, so I can believe you only started seeing this with 260.*.

I think we've essentially reproduced the second problem I listed above now, by running "kill -9" against MPlayer, rather than having it experience an error itself.

We'll keep trying to repro (1), and try to find out what the cause of problem (2) is.

mocharhw 01-21-11 11:56 PM

Re: Error detected 1 426, 260.19.06, loss of VDPAU v-sync on second monitor
 
Still having these problems with 260.19.36. No change.

mocharhw 02-22-11 11:30 AM

Re: Error detected 1 426, 260.19.06, loss of VDPAU v-sync on second monitor
 
Stephen,

For the last week I've been using beta 270.26 and I'm happy to say this problem is corrected in that version. In addition, I also no longer get the X server corruption as shown here, http://www.nvnews.net/vbulletin/show...8&postcount=28

Furthermore, everytime I switch mplayer to fullscreen I get the following message, but it doesn't seem to have any ill effects:

Code:

VDPAU nvidia: Version: NVIDIA VDPAU Driver Shared Library  270.26  Mon Feb 14 01:49:57 PST 2011
VDPAU nvidia: Error detected 1 2407

Additional observations about 270.26:

I'm still having problems with Flash 10.2.x like everyone else, but I assume that problem lies elsewhere.

Sometimes when opening a video with mplayer I get X server pauses as described here, http://www.nvnews.net/vbulletin/showthread.php?t=157499, and then if I look in /var/log/Xorg.0.log I have message blocks like this:

Code:

[ 88655.345] (II) XKB: reuse xkmfile /var/lib/xkb/server-DAEA4C886ED13CCB49EF0284D9D47E5611DB4ADA.xkm
[ 96002.616] [mi] EQ overflowing. The server is probably stuck in an infinite loop.
[ 96002.616]
Backtrace:
[ 96002.616] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80ef31b]
[ 96002.616] 1: /usr/bin/X (mieqEnqueue+0x1ab) [0x80ecb5b]
[ 96002.616] 2: /usr/bin/X (xf86PostMotionEventP+0xd2) [0x80bd662]
[ 96002.616] 3: /usr/lib/xorg/modules/input/evdev_drv.so (0xb4ce3000+0x4911) [0xb4ce7911]
[ 96002.616] 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb4ce3000+0x4a06) [0xb4ce7a06]
[ 96002.616] 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb4ce3000+0x5246) [0xb4ce8246]
[ 96002.616] 6: /usr/bin/X (0x8048000+0x62e7f) [0x80aae7f]
[ 96002.616] 7: /usr/bin/X (0x8048000+0x121b4e) [0x8169b4e]
[ 96002.616] 8: (vdso) (__kernel_sigreturn+0x0) [0xb7733400]
[ 96002.616] 9: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0xb5245000+0x3fe748) [0xb5643748]
[ 96002.616] 10: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0xb5245000+0x3fea91) [0xb5643a91]
[ 96002.616] 11: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0xb5245000+0x3feb09) [0xb5643b09]
[ 96003.926] nvLock: client timed out, taking the lock

These freezes are a completely random event and can't be tied to any particular video. In summary, from a users point of view I'd say 270.26 it's much improved over the 260.xx series, but not quite back to the stability of 195.xx.


All times are GMT -5. The time now is 07:55 AM.

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