Mailing List Archive: MythTV: Users

VDPAU Error: DISPLAY PRE-EMPTED. Aborting playback.

Index | Next | Previous | View Threaded

tortise at paradise

Jul 5, 2009, 6:39 AM

Post #1 of 13 (2150 views)
Permalink

VDPAU Error: DISPLAY PRE-EMPTED. Aborting playback.

Hi

I've run up a recent fresh mythbuntu 8.10, updated with JYA's latest with 20787, 2400 AMD, 9400GT PCI, 180.60. I've had a lot of
problems getting this box stable, other different hardware behaves much better. Maybe the motherboard and video card are not fully
compatible. (?) I append some NVIDIA comment. The AMD2400 previously performed well in an earlier life using a AGP 5200. Without
vdpau playback is jerky, with the CPU maxing out. With vdpau playback is smooth for ~10 - 60 seconds till it errors out. CPU still
seems to run 50 to 70%.

This problem repeatedly occurs within a minute of playing recorded SD mpeg2 (from DVB-S) files from a separate mythtv server, it is
readily repeatable.

I get:

2009-07-06 01:07:48.233 VDPAU Error: DISPLAY PRE-EMPTED. Aborting playback.
2009-07-06 01:07:48.235 NVP: Error condition detected in videoOutput after Show(), aborting playback.

I also append the full command output.
Can anyone suggest what I do with this from here please?

mythtv3:~$ export DISPLAY=:0.0 && mythfrontend
2009-07-06 01:06:22.918 Using runtime prefix = /usr
2009-07-06 01:06:23.454 XScreenSaver support enabled
2009-07-06 01:06:23.455 DPMS is active.
2009-07-06 01:06:23.456 Empty LocalHostName.
2009-07-06 01:06:23.456 Using localhost value of mythtv3
2009-07-06 01:06:23.489 New DB connection, total: 1
2009-07-06 01:06:23.501 Connected to database 'mythconverg' at host: 10.119.30.2
32
2009-07-06 01:06:23.503 Closing DB connection named 'DBManager0'
2009-07-06 01:06:23.505 Primary screen 0.
2009-07-06 01:06:23.507 Connected to database 'mythconverg' at host: 10.119.30.2
32
2009-07-06 01:06:23.509 Using screen 0, 1920x1080 at 0,0
2009-07-06 01:06:23.549 New DB connection, total: 2
2009-07-06 01:06:23.551 Connected to database 'mythconverg' at host: 10.119.30.2
32
2009-07-06 01:06:23.555 mythfrontend version: 0.21.20080304-1 www.mythtv.org
2009-07-06 01:06:23.556 Enabled verbose msgs: important general
2009-07-06 01:06:24.884 No theme dir: /home/david/.mythtv/themes/Mythbuntu-8.04
2009-07-06 01:06:24.886 Primary screen 0.
2009-07-06 01:06:24.887 Using screen 0, 1920x1080 at 0,0
2009-07-06 01:06:24.889 No theme dir: /home/david/.mythtv/themes/Mythbuntu-8.04
2009-07-06 01:06:24.890 Switching to square mode (Mythbuntu-8.04)
2009-07-06 01:06:24.941 Using the Qt painter
2009-07-06 01:06:24.944 lirc init success using configuration file: /home/david/
.mythtv/lircrc
2009-07-06 01:06:24.944 JoystickMenuClient Error: Joystick disabled - Failed to
read /home/david/.mythtv/joystickmenurc
2009-07-06 01:06:29.384 Specified base font 'medium' does not exist for font clo
ck
2009-07-06 01:06:29.384 Specified base font 'medium' does not exist for font sma
ll
2009-07-06 01:06:29.384 Specified base font 'medium' does not exist for font med
ium
2009-07-06 01:06:29.385 Specified base font 'medium' does not exist for font lar
ge
2009-07-06 01:06:29.393 Loading from: /usr/share/mythtv/themes/Mythbuntu-8.04/ba
se.xml
2009-07-06 01:06:30.052 Loading from: /usr/share/mythtv/themes/default/base.xml
2009-07-06 01:06:43.559 Registering Internal as a media playback plugin.
2009-07-06 01:06:45.929 MonitorRegisterExtensions(0x100, gif,jpg,png)
2009-07-06 01:06:48.283 MonitorRegisterExtensions(0x40, ogg,mp3,aac,flac)
SIP listening on IP Address 10.119.30.233:5060 NAT address 10.119.30.233
SIP: Cannot register; proxy, username or password not set
2009-07-06 01:06:53.551 NetworkControl: Listening for remote connections on port 6546
2009-07-06 01:06:53.553 No theme dir: /home/david/.mythtv/themes/Mythbuntu-8.04
2009-07-06 01:07:14.375 XMLParse::LoadTheme using /usr/share/mythtv/themes/Mythbuntu-8.04/ui.xml
2009-07-06 01:07:15.131 Connecting to backend server: 10.119.30.232:6543 (try 1 of 5)
2009-07-06 01:07:15.132 Using protocol version 40
2009-07-06 01:07:19.640 AFD: Opened codec 0x9d9ca10, id(MPEG2VIDEO) type(Video)
2009-07-06 01:07:19.641 AFD: codec MP3 has 2 channels
2009-07-06 01:07:19.641 AFD: Opened codec 0x9fcd1d0, id(MP3) type(Audio)
2009-07-06 01:07:23.349 TV: Attempting to change from None to WatchingPreRecorded
2009-07-06 01:07:23.415 AFD: Opened codec 0x9fcaa10, id(MPEG2VIDEO) type(Video)
2009-07-06 01:07:23.416 AFD: codec MP3 has 2 channels
2009-07-06 01:07:23.416 AFD: Opened codec 0x9fcca40, id(MP3) type(Audio)
2009-07-06 01:07:23.457 DPMS Deactivated
2009-07-06 01:07:27.130 AFD: Opened codec 0xa0bdd90, id(MPEGVIDEO_VDPAU) type(Video)
2009-07-06 01:07:27.130 AFD: codec MP3 has 2 channels
2009-07-06 01:07:27.131 AFD: Opened codec 0x9fc9750, id(MP3) type(Audio)
2009-07-06 01:07:27.525 Opening audio device 'default'. ch 2(2) sr 48000
2009-07-06 01:07:27.525 Opening ALSA audio device 'default'.
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL /dev/mixer
2009-07-06 01:07:27.547 AudioOutput Warning: Mixer attach error -2: No such file or directory
Check Mixer Name in Setup: '/dev/mixer'
2009-07-06 01:07:27.931 WriteAudio: buffer underrun
2009-07-06 01:07:28.089 WriteAudio: buffer underrun
2009-07-06 01:07:28.158 WriteAudio: buffer underrun
2009-07-06 01:07:28.337 WriteAudio: buffer underrun
2009-07-06 01:07:28.403 WriteAudio: buffer underrun
2009-07-06 01:07:28.505 WriteAudio: buffer underrun
2009-07-06 01:07:28.588 WriteAudio: buffer underrun
2009-07-06 01:07:28.741 WriteAudio: buffer underrun
2009-07-06 01:07:28.808 WriteAudio: buffer underrun
2009-07-06 01:07:29.195 OSD Theme Dimensions W: 640 H: 480
2009-07-06 01:07:29.836 TV: Changing from None to WatchingPreRecorded
2009-07-06 01:07:29.842 New DB connection, total: 3
2009-07-06 01:07:29.843 Realtime priority would require SUID as root.
2009-07-06 01:07:29.845 Connected to database 'mythconverg' at host: 10.119.30.232
2009-07-06 01:07:29.948 Video timing method: USleep with busy wait

2009-07-06 01:07:48.233 VDPAU Error: DISPLAY PRE-EMPTED. Aborting playback.
2009-07-06 01:07:48.235 NVP: Error condition detected in videoOutput after Show(), aborting playback.
2009-07-06 01:07:48.241 TV: Attempting to change from WatchingPreRecorded to None
2009-07-06 01:08:57.754 TV: Changing from WatchingPreRecorded to None
2009-07-06 01:08:57.755 TV: Attempting to change from None to None
2009-07-06 01:08:58.466 DPMS Reactivated.
2009-07-06 01:09:00.646 AFD: Opened codec 0xa460880, id(MPEG2VIDEO) type(Video)
2009-07-06 01:09:00.647 AFD: codec MP3 has 2 channels
2009-07-06 01:09:00.647 AFD: Opened codec 0x9fb7ed0, id(MP3) type(Audio)
2009-07-06 01:09:06.023 AFD: Opened codec 0xa460860, id(MPEG2VIDEO) type(Video)
2009-07-06 01:09:06.023 AFD: codec MP3 has 2 channels
2009-07-06 01:09:06.023 AFD: Opened codec 0x9fb7ea0, id(MP3) type(Audio)
2009-07-06 01:09:08.413 NVP: prebuffering pause
2009-07-06 01:09:09.728 NVP: prebuffering pause
................

From NVIDIA (forum):
compared to the PCI-E version of a card, I'd expect the PCI version to suffer from performance and, potentially, compatibility
problems. The bus interface bandwidth is greatly reduced, certain features like non-coherent system memory accesses are unavailable,
32-bit PCI cards are unable to address memory above 4GB, limiting the pool of memory available to it, etc.. The graphics driver
stack may also take paths not as well exercised.
the limitations I pointed out are not NVIDIA specific, they are limitations of the PCI bus. In terms of adequacy of the 32-bit PCI
bus's for streaming video, I don't have a good sense for the amounts of data being streamed (Stephen will have a much better idea),
though I'd expect them to vary. Available bandwidth and latencies will also vary with the bus topology, the presence of other
devices on the bus in question, their type and DMA characteristics, etc.. It is my understanding that the GPU(s) in question are
PCI-E GPUs bridged to PCI, which has additional implications.
Due to all of the above, I can't say whether a PCI card would satisfy your requirements. As to driver issues: if PCI specific bugs
are identified (I'm not aware of any at this point), I'd expect us to want to resolve them, but chances are they'd be prioritized
behind more generic ones.

Profiles in place:
< W: 1920 H: 720, decoder: VDPAU, renderer: VDPAU, Deinterlacer: Advanced 2X
>= W: 0 H: 720, decoder: VDPAU, renderer: VDPAU, Deinterlacer: Temporal 2X

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

thecovert at gmail

Jul 13, 2009, 6:23 AM

Post #2 of 13 (1982 views)
Permalink

Re: VDPAU Error: DISPLAY PRE-EMPTED. Aborting playback. [In reply to]

On Sun, Jul 5, 2009 at 11:39 PM, Tortise<tortise [at] paradise> wrote:
> I get:
>
> 2009-07-06 01:07:48.233 VDPAU Error: DISPLAY PRE-EMPTED. Aborting playback.
> 2009-07-06 01:07:48.235 NVP: Error condition detected in videoOutput after Show(), aborting playback.

I had this problem recently with my Mythtv Installation. Updated to
Nvidia 185 drivers and it was all fixed. I also have 180 drivers.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

david at shay

Jul 19, 2009, 11:09 AM

Post #3 of 13 (1934 views)
Permalink

Re: VDPAU Error: DISPLAY PRE-EMPTED. Aborting playback. [In reply to]

On Mon, Jul 13, 2009 at 8:23 AM, covert covert <thecovert [at] gmail> wrote:

> On Sun, Jul 5, 2009 at 11:39 PM, Tortise<tortise [at] paradise> wrote:
> > I get:
> >
> > 2009-07-06 01:07:48.233 VDPAU Error: DISPLAY PRE-EMPTED. Aborting
> playback.
> > 2009-07-06 01:07:48.235 NVP: Error condition detected in videoOutput
> after Show(), aborting playback.
>
>
> I had this problem recently with my Mythtv Installation. Updated to
> Nvidia 185 drivers and it was all fixed. I also have 180 drivers.
>
> Seeing this same thing on a PCI bus 8400 GT. Neither 180.60 or 185.18.14
fixed it. Running trunk 20947 right now. I *perhaps* *think* I didn't see
this with either some older version of the NVIDIA driver or some older
version of trunk, not sure which since both changed. But I was also in
"prototype" mode at that point -- now I am trying to temporarily use this
machine as a "production" node. Especially since my Zotac ION is being RMA'd
for a bad memory bus controller...

I've tried without any interlacer at all, and still see the issue, as well.
Also, to reduce any of the other possibilities, I'm running with a very
light window manager (ratpoison) instead of kde/kdm which I was running.

Not sure where to go at this point - myth bug, nvidia driver bug, or what...
I'm back to XvMC and SD content right now.

bill at bbqninja

Jul 19, 2009, 4:56 PM

Post #4 of 13 (1931 views)
Permalink

Re: VDPAU Error: DISPLAY PRE-EMPTED. Aborting playback. [In reply to]

On Mon, Jul 20, 2009 at 4:09 AM, David Shay<david [at] shay> wrote:
>
>
> On Mon, Jul 13, 2009 at 8:23 AM, covert covert <thecovert [at] gmail> wrote:
>>
>> On Sun, Jul 5, 2009 at 11:39 PM, Tortise<tortise [at] paradise> wrote:
>> > I get:
>> >
>> > 2009-07-06 01:07:48.233 VDPAU Error: DISPLAY PRE-EMPTED. Aborting
>> > playback.
>> > 2009-07-06 01:07:48.235 NVP: Error condition detected in videoOutput
>> > after Show(), aborting playback.
>>
>>
>> I had this problem recently with my Mythtv Installation. Updated to
>> Nvidia 185 drivers and it was all fixed. I also have 180 drivers.
>>
> Seeing this same thing on a PCI bus 8400 GT. �Neither 180.60 or 185.18.14
> fixed it. Running trunk 20947 right now. I *perhaps* *think* I didn't see
> this with either some older version of the NVIDIA driver or some older
> version of trunk, not sure which since both changed. �But I was also in
> "prototype" mode at that point -- now I am trying to temporarily use this
> machine as a "production" node. Especially since my Zotac ION is being RMA'd
> for a bad memory bus controller...
> I've tried without any interlacer at all, and still see the issue, as well.
> Also, to reduce any of the other possibilities, I'm running with a very
> light �window manager (ratpoison) instead of kde/kdm which I was running.
> Not sure where to go at this point - myth bug, nvidia driver bug, or what...
> �I'm back to XvMC and SD content right now.

try the VDPAU enabled mplayer to eliminate (or not) myth.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jyavenard at gmail

Jul 21, 2009, 8:52 PM

Post #5 of 13 (1897 views)
Permalink

Re: VDPAU Error: DISPLAY PRE-EMPTED. Aborting playback. [In reply to]

Hi

2009/7/21 Jean-Yves Avenard <jyavenard [at] gmail>:
> You're using the VDPAU backport which can not recover from such error:
> if you get such error it stops any playback.
>
> use mythtv trunk, it can recover from such errors.
>

I'm building new 0.21-fixes packages with VDPAU support against the
just release nvidia drivers 190.16 ; they are supposed to handle
corrupted h264 streams better. you can see how they go ...

Jean-Yves
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

thecovert at gmail

Jul 21, 2009, 9:20 PM

Post #6 of 13 (1911 views)
Permalink

Re: VDPAU Error: DISPLAY PRE-EMPTED. Aborting playback. [In reply to]

On Wed, Jul 22, 2009 at 1:52 PM, Jean-Yves Avenard<jyavenard [at] gmail> wrote:
> Hi
>
> 2009/7/21 Jean-Yves Avenard <jyavenard [at] gmail>:
>> You're using the VDPAU backport which can not recover from such error:
>> if you get such error it stops any playback.
>>
>> use mythtv trunk, it can recover from such errors.
>>
>
> I'm building new 0.21-fixes packages with VDPAU support against the
> just release nvidia drivers 190.16 ; they are supposed to handle
> corrupted h264 streams better. you can see how they go ...
>
> Jean-Yves

I eagerly await the package :) About the last problem left in a system
I am building.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

marius at schrecker

Jul 21, 2009, 10:56 PM

Post #7 of 13 (1897 views)
Permalink

Re: VDPAU Error: DISPLAY PRE-EMPTED. Aborting playback. [In reply to]

What is the current status of these problems in relation to trunk? Jean-Yves has done a fantastic job of providing fixes and methods for getting VDPAU, framerate/refresh sync, and many other issues to work against 0.21-fixes, and I'm guessing that some, but not all of these are backports from trunk.

I've just bought a HD-PVR, but haven't had time to set it up yet. Will need VDPAU when I do. Lets hope Nvidia 190* is better than 185*

Cheers!

Marius

On Wed Jul 22 6:20 , covert covert sent:

On Wed, Jul 22, 2009 at 1:52 PM, Jean-Yves Avenard<jyavenard [at] gmail> wrote:
> Hi
>
> 2009/7/21 Jean-Yves Avenard <jyavenard [at] gmail>:
>> You're using the VDPAU backport which can not recover from such error:
>> if you get such error it stops any playback.
>>
>> use mythtv trunk, it can recover from such errors.
>>
>
> I'm building new 0.21-fixes packages with VDPAU support against the
> just release nvidia drivers 190.16 ; they are supposed to handle
> corrupted h264 streams better. you can see how they go ...
>
> Jean-Yves

I eagerly await the package :) About the last problem left in a system
I am building.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jyavenard at gmail

Jul 21, 2009, 11:12 PM

Post #8 of 13 (1890 views)
Permalink

Re: VDPAU Error: DISPLAY PRE-EMPTED. Aborting playback. [In reply to]

Hi

2009/7/22 Marius Schrecker <marius [at] schrecker>:
> I've just bought a HD-PVR, but haven't had time to set it up yet. Will need
> VDPAU when I do. Lets hope Nvidia 190* is better than 185*
>

Been running 190.16 drivers for about one hour ; still plenty of
segfault in libGL ; changing channels make mythtv segfault.

Changing xrandr display refresh rate during VDPAU playback still crashes X.

It seems to be a tad more stable than 185.18.14 ; but barely...

With 180.60, mythtv never segault during videoplayback...
Jean-Yves
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jyavenard at gmail

Jul 21, 2009, 11:22 PM

Post #9 of 13 (1892 views)
Permalink

Re: VDPAU Error: DISPLAY PRE-EMPTED. Aborting playback. [In reply to]

Hi

2009/7/22 Jean-Yves Avenard <jyavenard [at] gmail>:
>
> Been running 190.16 drivers for about one hour ; still plenty of
> segfault in libGL ; changing channels make mythtv segfault.

After a bit more investigation, disabling OpenGL VSync in Settings ->
TV -> Playback prevents most issues ..

Jean-Yves
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

sonofzev at iinet

Jul 21, 2009, 11:42 PM

Post #10 of 13 (1892 views)
Permalink

Re: VDPAU Error: DISPLAY PRE-EMPTED. Aborting playback. [In reply to]

On Wed Jul 22 16:22 , Jean-Yves Avenard sent:

>Hi
>
>2009/7/22 Jean-Yves Avenard jyavenard [at] gmail>:
>>
>> Been running 190.16 drivers for about one hour ; still plenty of
>> segfault in libGL ; changing channels make mythtv segfault.
>
>After a bit more investigation, disabling OpenGL VSync in Settings ->
>TV -> Playback prevents most issues ..
>
>Jean-Yves

Does this result in ripping?
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

sonofzev at iinet

Jul 28, 2009, 5:19 PM

Post #11 of 13 (1753 views)
Permalink

Re: VDPAU Error: DISPLAY PRE-EMPTED. Aborting playback. [In reply to]

On Wed Jul 29 10:02 , Jean-Yves Avenard sent:

>2009/7/29 Tortise tortise [at] paradise>:
>> 185.18.29 Linux x86/x86-64 released
>> http://www.nvnews.net/vbulletin/showthread.php\?p=2056716 included
>>
>> "Enhanced VDPAU to better handle corrupt/invalid H.264 bitstreams on G84, G86,
G92, G94, G96, or GT200 GPUs. This should prevent
>> most cases of "display preemption" that are caused by bitstream errors."
>>
>> display preemption was also happening for me with mpg's, however I am not sure
if the source of the problem was bitstream errors?
>>
>> Here's hoping.....!
>
>This is the same text as with the 190.x drivers which you tried ...
>_______________________________________________
>mythtv-users mailing list
>mythtv-users [at] mythtv
>http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>)

After following someones advice on here (I'm not sure if it was JYA or J
Drescher) and unchecking the sync vertical to opengl I have not got one error. I
am using the 190.x drivers...

cheers

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

enigma at thedonnerparty

Jan 24, 2010, 4:01 PM

Post #12 of 13 (1264 views)
Permalink

Re: VDPAU Error: DISPLAY PRE-EMPTED. Aborting playback. [In reply to]

FWIW, here is my experience with a similar card:
http://www.nvnews.net/vbulletin/showpost.php?p=2161443&postcount=236
http://www.gossamer-threads.com/lists/mythtv/users/397753

My card is a Sparkle 9400 GT G96 512 MB PCI with the same problem. I have
also seen other reports of this issue with similar cards. I have sunk a ton
of time into this card trying to get it to work but I haven't been able to
eliminate the pre-emption errors. From the response I got in the Nvidia
thread, I doubt I ever will. IIRC, mplayer is a lot better at recovering
from the errors than Myth, so if you have need of a MythVideo only box it
still might be of some use to you.

enigma at thedonnerparty

Jan 24, 2010, 9:50 PM

Post #13 of 13 (1265 views)
Permalink

Re: VDPAU Error: DISPLAY PRE-EMPTED. Aborting playback. [In reply to]

On Sun, Jan 24, tortise at paradise wrote:
>
> Enigma, what's your CPU / Motherboard / Chipset?

I have tried the card with the following motherboards:

MSI Kt3 Ultra 2 (I think this one is KT333) [Athon XP processor]
PC Chips 848A (SiS chipset) [Athon XP processor]
MSI Hetis 915 (Intel 915? chipset) [Celeron @3.2 GHz]
Asus Pundit PH1 (Nvidia Nforce chipset) [Athlon 64 X2]

I have tried different power supplies with no change. I don't think
it is temperature related, I get the same errors with or without a fan
(the card ships fanless, it runs about 20 degrees cooler with a fan
attached). I have tried many different configurations, all with the
same result.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads