Hi, Am 18.03.2010 13:43, schrieb peter:
>>>> Does this happen too when not using vdpau? >> >> I'm not using vdpau (haven't got the hardware for it). >> >> vdr-1.7.10 >> xine-lib-1.2 >> >> The problem occurs when running xine with dxr3 output (xine --verbose=1 -V >> dxr3 -A alsa vdr:/tmp/vdr-xi/stream) >> >> Mar 18 13:26:43 vdr-desktop kernel: [ 6250.760298] em8300-0: adjusting scr: >> 30791 >> Mar 18 13:26:45 vdr-desktop kernel: [ 6252.872307] em8300-0: adjusting scr: >> 125823 >> Mar 18 13:27:05 vdr-desktop vdr: [4159] buffer usage: 70% (tid=4158) >> Mar 18 13:27:06 vdr-desktop vdr: [4159] buffer usage: 80% (tid=4158) >> Mar 18 13:27:06 vdr-desktop vdr: [4159] buffer usage: 90% (tid=4158) >> Mar 18 13:27:07 vdr-desktop vdr: [4159] buffer usage: 100% (tid=4158) >> Mar 18 13:27:18 vdr-desktop vdr: [4159] ERROR: driver buffer overflow on >> device 1 >> Mar 18 13:27:18 vdr-desktop vdr: [4159] buffer usage: 30% (tid=4158) >> Mar 18 13:27:18 vdr-desktop vdr: [4158] ERROR: skipped 11 bytes to sync on >> TS packet on device 1 >> Mar 18 13:27:18 vdr-desktop vdr: [4158] TS continuity error (3) >> Mar 18 13:27:18 vdr-desktop vdr: [4158] TS continuity error (11) >> Mar 18 13:27:18 vdr-desktop vdr: [4158] cAudioRepacker(0xC0): skipped 312 >> bytes while syncing on next audio frame >> >> However: >> >> When running without dxr3 (xine --verbose=1 -V xshm -A alsa >> vdr:/tmp/vdr-xine/stream) everything is fine. >> >> Here's gdb output from a bad run: Well, vdr-xine is writing to xine and blocks as xine doesn't read any input data. Would you be so kind and create a backtrace of xine when this happens again. And provide an "unwrapped" backtrace, e. g. by attaching the backtrace as a text file, which makes it easier to read, especially as xine has much more threads. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rni...@gmx.de _______________________________________________ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
