Re: [vdr] ERROR: driver buffer overflow on device 1
Hi, i have the same problem vdr-1.7.14 xine-lib-1.2 (cvs, patched with last VDPAU patches) xineliboutput (last from cvs) i'm using vdpau it happen only on hd channels, mostly on complex frame (snow, fire, an very fast actions), seems not related to high HD transfer. CPU usage is very low. The picture freeze fro 1 sec then start again. if i exit from (frontend) vdr-sxfe and start again it works. (config are ok, speedoveraccurancy=1, ecc..) Did anyone solve it ? Il giorno dom, 21/03/2010 alle 08.58 +0100, Reinhard Nissl ha scritto: 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 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ERROR: driver buffer overflow on device 1
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
Re: [vdr] ERROR: driver buffer overflow on device 1
Hi, Am 21.03.2010 16:36, schrieb Peter Odéus: 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. I would happily do that if you can guide on how to backtrace xine. When xine is unresponsive, type something like that: gdb /path/to/xine `pidof xine` At the gdb prompt, issue the following command: thread apply all bt and provide the output. 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
Re: [vdr] ERROR: driver buffer overflow on device 1
I have experienced this problem several times today while on HD h264 channels. Like previously posted: Mar 12 15:02:23 vdr: [20675] buffer usage: 70% (tid=20674) Mar 12 15:02:24 vdr: [20675] buffer usage: 80% (tid=20674) Mar 12 15:02:24 vdr: [20675] buffer usage: 90% (tid=20674) Mar 12 15:02:25 vdr: [20675] buffer usage: 100% (tid=20674) VDR was unresponsive and had to be restarted to fix. Best regards, Derek Sorry, forgot to mention this is with VDR-1.7.13... I confirm - with vdr 1.7.13 still have the same issue I assume, you both use vdr-xine. It would be a good idea to create a backtrace in that situation to rule out vdr-xine as source of this issue. yes, I'm using the vdr-xine 093 please advice how should I use backtrace When VDR is unresponsive, type something like that: gdb /path/to/vdr `pidof vdr` At the gdb prompt, issue the following command: thread apply all bt and provide the output. but with my buffer overflow problem the vdr is working without any deadlock. I can such messages only in syslog. That's why I can't do backtrace Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ERROR: driver buffer overflow on device 1
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: (gdb) thread apply all bt Thread 10 (Thread 0xb7648b70 (LWP 4030)): #0 0x0018a422 in __kernel_vsyscall () #1 0x00c5c142 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0x0811a56e in cCondVar::TimedWait (this=0x9d7fac4, Mutex=..., TimeoutMs=1000) at thread.c:127 #3 0x080afd3e in cDvbTuner::Action (this=0x9d7f508) at dvbdevice.c:389 #4 0x08119d40 in cThread::StartThread (Thread=0x9d7f508) at thread.c:257 #5 0x00c5780e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #6 0x0074f8de in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 9 (Thread 0xb6e47b70 (LWP 4031)): #0 0x0018a422 in __kernel_vsyscall () #1 0x00741c96 in poll () from /lib/tls/i686/cmov/libc.so.6 #2 0x080ff76a in cSectionHandler::Action (this=0x9d6f610) at sections.c:184 #3 0x08119d40 in cThread::StartThread (Thread=0x9d6f610) at thread.c:257 #4 0x00c5780e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #5 0x0074f8de in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 8 (Thread 0xb6646b70 (LWP 4032)): #0 0x0018a422 in __kernel_vsyscall () #1 0x00741c96 in poll () from /lib/tls/i686/cmov/libc.so.6 ---Type return to continue, or q return to quit--- #2 0x0811f97b in cPoller::Poll (this=0x64, TimeoutMs=100) at tools.c:1195 #3 0x002a513d in PluginXine::cXineRemote::Action (this=0x9d842d8) at xineRemote.c:157 #4 0x08119d40 in cThread::StartThread (Thread=0x9d842e8) at thread.c:257 #5 0x00c5780e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #6 0x0074f8de in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 7 (Thread 0xb5e1ab70 (LWP 4033)): #0 0x0018a422 in __kernel_vsyscall () #1 0x00c5c142 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0x0811a56e in cCondVar::TimedWait (this=0xb5e1d7b8, Mutex=..., TimeoutMs=100) at thread.c:127 #3 0x00298ead in PluginXine::cXineLib::Action (this=0xb5e1d260) at xineLib.c:2632 #4 0x08119d40 in cThread::StartThread (Thread=0xb5e1d260) at thread.c:257 #5 0x00c5780e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #6 0x0074f8de in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 6 (Thread 0xb5619b70 (LWP 4034)): #0 0x0018a422 in __kernel_vsyscall () #1 0x00c5c142 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 ---Type return to continue, or q return to quit--- #2 0x0811a56e in cCondVar::TimedWait (this=0xb5e1d310, Mutex=..., TimeoutMs=100) at thread.c:127 #3 0x002a6278 in PluginXine::cXineExternal::Action (this=0xb5e1d2b8) at xineExternal.c:204 #4 0x08119d40 in cThread::StartThread (Thread=0xb5e1d2b8) at thread.c:257 #5 0x00c5780e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #6 0x0074f8de in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 5 (Thread 0xb4e18b70 (LWP 4035)): #0 0x0018a422 in __kernel_vsyscall () #1 0x00c5ec8b in read () from /lib/tls/i686/cmov/libpthread.so.0 #2 0x00113901 in cRemoteDevInput::getKey() () from /usr/lib/vdr/libvdr-remote.so.1.7.10 #3 0x00113d87 in cRemoteGeneric::Action() () from /usr/lib/vdr/libvdr-remote.so.1.7.10 #4 0x08119d40 in cThread::StartThread (Thread=0x9d867f0) at thread.c:257 #5 0x00c5780e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #6 0x0074f8de in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 4 (Thread 0xb4617b70 (LWP 4036)): #0 0x0018a422 in __kernel_vsyscall () #1 0x00741c96 in poll () from /lib/tls/i686/cmov/libc.so.6 #2 0x0811f97b in cPoller::Poll (this=0x32, TimeoutMs=50) at tools.c:1195 ---Type return to continue, or q return to quit--- #3 0x080f9028 in cKbdRemote::ReadKey (this=0x9d86910
Re: [vdr] ERROR: driver buffer overflow on device 1
The problem occurs when running xine with dxr3 output (xine --verbose=1 -V dxr3 -A alsa vdr:/tmp/vdr-xi/stream) hmm, when disabling color bar output of the dxr3 card, I do get a picture (albeit it is blackwhite, wrong size and of terrible quality), but at least vdr stays responsive and out of trouble... /Peter Odéus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ERROR: driver buffer overflow on device 1
On 14 March 2010 21:47, Reinhard Nissl rni...@gmx.de wrote: Hi, Am 14.03.2010 12:46, schrieb Goga777: I have experienced this problem several times today while on HD h264 channels. Like previously posted: Mar 12 15:02:23 vdr: [20675] buffer usage: 70% (tid=20674) Mar 12 15:02:24 vdr: [20675] buffer usage: 80% (tid=20674) Mar 12 15:02:24 vdr: [20675] buffer usage: 90% (tid=20674) Mar 12 15:02:25 vdr: [20675] buffer usage: 100% (tid=20674) VDR was unresponsive and had to be restarted to fix. Best regards, Derek Sorry, forgot to mention this is with VDR-1.7.13... I confirm - with vdr 1.7.13 still have the same issue I assume, you both use vdr-xine. It would be a good idea to create a backtrace in that situation to rule out vdr-xine as source of this issue. yes, I'm using the vdr-xine 093 please advice how should I use backtrace I see similar problems with xineliboutput, but I'm not sure it's exactly the same problem. I don't have to restart VDR, restarting the vdr-sxfe client is sufficient. In the logs I get Mar 17 13:54:43 htpc vdr: [3710] [xine..put] cXinelibServer::Play_PES Buffer overflow (TCP/PIPE) Mar 17 13:54:43 htpc vdr: [3710] [xine..put] cXinelibServer::Play_PES Buffer overflow (TCP/PIPE) Mar 17 13:54:43 htpc vdr: [3710] [xine..put] cXinelibServer::Play_PES Buffer overflow (TCP/PIPE) [ repeat X times..] Mar 17 13:54:54 htpc vdr: [3710] [xine..put] cXinelibServer::Play_PES Buffer overflow (TCP/PIPE) Mar 17 13:54:54 htpc vdr: [3710] [xine..put] cXinelibServer::Play_PES Buffer overflow (TCP/PIPE) Mar 17 13:54:54 htpc vdr: [3710] [xine..put] cXinelibServer: Too many TCP buffer overflows, dropping client Mar 17 13:54:54 htpc vdr: [3710] [xine..put] cXinelibServer::Play_PES Write/Queue error (TCP/PIPE) Mar 17 13:54:54 htpc vdr: [3710] [xine..put] Closing connection 0 Sometimes the logs has the buffer usage messages as well; Mar 16 01:38:17 htpc vdr: [8370] [xine..put] cXinelibServer::Play_PES Buffer overflow (TCP/PIPE) Mar 16 01:38:17 htpc vdr: [8370] [xine..put] cXinelibServer: Too many TCP buffer overflows, dropping client Mar 16 01:38:17 htpc vdr: [8370] [xine..put] cXinelibServer::Play_PES Write/Queue error (TCP/PIPE) Mar 16 01:38:19 htpc vdr: [8371] buffer usage: 70% (tid=8370) Mar 16 01:38:19 htpc vdr: [8371] buffer usage: 80% (tid=8370) Mar 16 01:38:19 htpc vdr: [8371] buffer usage: 90% (tid=8370) Mar 16 01:38:19 htpc vdr: [8371] buffer usage: 100% (tid=8370) Mar 16 01:38:20 htpc vdr: [8370] ERROR: thread 8429 won't end (waited 3 seconds) - canceling it... Mar 16 01:38:20 htpc vdr: [8370] [xine..put] Closing connection 0 Mar 16 01:38:20 htpc vdr: [8371] buffer usage: 60% (tid=8370) This is a problem since the vdr-sxfe client doesn't exit, it just freezes. It would be better if it exit, then it could reconnect if scripted to do so. Some output from gdb; [r...@htpc ~]# gdb /usr/local/bin/vdr `pidof vdr` GNU gdb (GDB) Fedora (7.0.1-33.fc12) Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i686-redhat-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/local/bin/vdr...done. Attaching to program: /usr/local/bin/vdr, process 1809 Reading symbols from /usr/lib/libjpeg.so.62...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libjpeg.so.62 Reading symbols from /lib/libpthread.so.0...(no debugging symbols found)...done. [Thread debugging using libthread_db enabled] [New Thread 0xaf599b70 (LWP 3711)] [New Thread 0xb17f8b70 (LWP 3710)] [New Thread 0xb21f9b70 (LWP 1822)] [New Thread 0xb35fbb70 (LWP 1820)] [New Thread 0xb3ffcb70 (LWP 1819)] [New Thread 0xb49fdb70 (LWP 1818)] [New Thread 0xb53feb70 (LWP 1817)] [New Thread 0xb5dffb70 (LWP 1815)] [New Thread 0xb6b1bb70 (LWP 1814)] Loaded symbols for /lib/libpthread.so.0 Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /lib/libcap.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libcap.so.2 Reading symbols from /lib/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/librt.so.1 Reading symbols from /usr/lib/libfreetype.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libfreetype.so.6 Reading symbols from /usr/lib/libfontconfig.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libfontconfig.so.1 Reading symbols from /usr/lib/libstdc++.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libstdc++.so.6 Reading symbols from /lib/libm.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.6 Reading symbols from /lib/libgcc_s.so.1...(no debugging symbols found)...done.
Re: [vdr] ERROR: driver buffer overflow on device 1
Am 17.03.2010 07:23, schrieb Torgeir Veimo: On 14 March 2010 21:47, Reinhard Nissl rni...@gmx.de wrote: Hi, Am 14.03.2010 12:46, schrieb Goga777: I have experienced this problem several times today while on HD h264 channels. Like previously posted: Mar 12 15:02:23 vdr: [20675] buffer usage: 70% (tid=20674) Mar 12 15:02:24 vdr: [20675] buffer usage: 80% (tid=20674) Mar 12 15:02:24 vdr: [20675] buffer usage: 90% (tid=20674) Mar 12 15:02:25 vdr: [20675] buffer usage: 100% (tid=20674) VDR was unresponsive and had to be restarted to fix. Best regards, Derek Sorry, forgot to mention this is with VDR-1.7.13... I confirm - with vdr 1.7.13 still have the same issue I assume, you both use vdr-xine. It would be a good idea to create a backtrace in that situation to rule out vdr-xine as source of this issue. yes, I'm using the vdr-xine 093 please advice how should I use backtrace I see similar problems with xineliboutput, but I'm not sure it's exactly the same problem. I don't have to restart VDR, restarting the vdr-sxfe client is sufficient. Hmm, looks like xine / vdr-sxfe would be to blame. There are some cases where vdpau leaks images while decoding h264 video and when no more images are left, xine / vdr-sxfe freezes and vdr runs into an buffer overflow. Does this happen too when not using vdpau? 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
Re: [vdr] ERROR: driver buffer overflow on device 1
Hi, Am 13.03.2010 11:30, schrieb Goga777: I have experienced this problem several times today while on HD h264 channels. Like previously posted: Mar 12 15:02:23 vdr: [20675] buffer usage: 70% (tid=20674) Mar 12 15:02:24 vdr: [20675] buffer usage: 80% (tid=20674) Mar 12 15:02:24 vdr: [20675] buffer usage: 90% (tid=20674) Mar 12 15:02:25 vdr: [20675] buffer usage: 100% (tid=20674) VDR was unresponsive and had to be restarted to fix. Best regards, Derek Sorry, forgot to mention this is with VDR-1.7.13... I confirm - with vdr 1.7.13 still have the same issue I assume, you both use vdr-xine. It would be a good idea to create a backtrace in that situation to rule out vdr-xine as source of this issue. 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
Re: [vdr] ERROR: driver buffer overflow on device 1
I have experienced this problem several times today while on HD h264 channels. Like previously posted: Mar 12 15:02:23 vdr: [20675] buffer usage: 70% (tid=20674) Mar 12 15:02:24 vdr: [20675] buffer usage: 80% (tid=20674) Mar 12 15:02:24 vdr: [20675] buffer usage: 90% (tid=20674) Mar 12 15:02:25 vdr: [20675] buffer usage: 100% (tid=20674) VDR was unresponsive and had to be restarted to fix. Best regards, Derek Sorry, forgot to mention this is with VDR-1.7.13... I confirm - with vdr 1.7.13 still have the same issue I assume, you both use vdr-xine. It would be a good idea to create a backtrace in that situation to rule out vdr-xine as source of this issue. yes, I'm using the vdr-xine 093 please advice how should I use backtrace thanks Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ERROR: driver buffer overflow on device 1
Hi, Am 14.03.2010 12:46, schrieb Goga777: I have experienced this problem several times today while on HD h264 channels. Like previously posted: Mar 12 15:02:23 vdr: [20675] buffer usage: 70% (tid=20674) Mar 12 15:02:24 vdr: [20675] buffer usage: 80% (tid=20674) Mar 12 15:02:24 vdr: [20675] buffer usage: 90% (tid=20674) Mar 12 15:02:25 vdr: [20675] buffer usage: 100% (tid=20674) VDR was unresponsive and had to be restarted to fix. Best regards, Derek Sorry, forgot to mention this is with VDR-1.7.13... I confirm - with vdr 1.7.13 still have the same issue I assume, you both use vdr-xine. It would be a good idea to create a backtrace in that situation to rule out vdr-xine as source of this issue. yes, I'm using the vdr-xine 093 please advice how should I use backtrace When VDR is unresponsive, type something like that: gdb /path/to/vdr `pidof vdr` At the gdb prompt, issue the following command: thread apply all bt and provide the output. 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
Re: [vdr] ERROR: driver buffer overflow on device 1
I have experienced this problem several times today while on HD h264 channels. Like previously posted: Mar 12 15:02:23 vdr: [20675] buffer usage: 70% (tid=20674) Mar 12 15:02:24 vdr: [20675] buffer usage: 80% (tid=20674) Mar 12 15:02:24 vdr: [20675] buffer usage: 90% (tid=20674) Mar 12 15:02:25 vdr: [20675] buffer usage: 100% (tid=20674) VDR was unresponsive and had to be restarted to fix. Best regards, Derek Sorry, forgot to mention this is with VDR-1.7.13... I confirm - with vdr 1.7.13 still have the same issue Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ERROR: driver buffer overflow on device 1
On Fri, Mar 5, 2010 at 7:31 AM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: What about VDR 1.7.11 and 1.7.13 (just to further narrow this down)? I have experienced this problem several times today while on HD h264 channels. Like previously posted: Mar 12 15:02:23 vdr: [20675] buffer usage: 70% (tid=20674) Mar 12 15:02:24 vdr: [20675] buffer usage: 80% (tid=20674) Mar 12 15:02:24 vdr: [20675] buffer usage: 90% (tid=20674) Mar 12 15:02:25 vdr: [20675] buffer usage: 100% (tid=20674) VDR was unresponsive and had to be restarted to fix. Best regards, Derek ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ERROR: driver buffer overflow on device 1
On Fri, Mar 12, 2010 at 3:08 PM, VDR User user@gmail.com wrote: On Fri, Mar 5, 2010 at 7:31 AM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: What about VDR 1.7.11 and 1.7.13 (just to further narrow this down)? I have experienced this problem several times today while on HD h264 channels. Like previously posted: Mar 12 15:02:23 vdr: [20675] buffer usage: 70% (tid=20674) Mar 12 15:02:24 vdr: [20675] buffer usage: 80% (tid=20674) Mar 12 15:02:24 vdr: [20675] buffer usage: 90% (tid=20674) Mar 12 15:02:25 vdr: [20675] buffer usage: 100% (tid=20674) VDR was unresponsive and had to be restarted to fix. Best regards, Derek Sorry, forgot to mention this is with VDR-1.7.13... ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ERROR: driver buffer overflow on device 1
On 24.02.2010 18:11, Joerg Bornkessel wrote: Perhaps it's the same problem as I have with my unmodded FF-Card Same here on vdr-1.7.12 with reel snap -r14440 ( starts on update to vdr-1.7.11 ) terractec-1200 dvb-c card latest vanilla kernel sources. this is on all sky channels with resolution 1920 x 1080 If i go down to vdr-1.7.10, all problems are gone. What about VDR 1.7.11 and 1.7.13 (just to further narrow this down)? Klaus, In my case its fixed with recompile 'our all beloved' plugin ** with another CXXFLAGS ( 1.7.13 not tested yet ) Sorry, my fault :( -- Regards Gentoo Developer Joerg Bornkessel hd_bru...@gentoo.org ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ERROR: driver buffer overflow on device 1
On 24.02.2010 18:11, Joerg Bornkessel wrote: Perhaps it's the same problem as I have with my unmodded FF-Card Same here on vdr-1.7.12 with reel snap -r14440 ( starts on update to vdr-1.7.11 ) terractec-1200 dvb-c card latest vanilla kernel sources. this is on all sky channels with resolution 1920 x 1080 If i go down to vdr-1.7.10, all problems are gone. What about VDR 1.7.11 and 1.7.13 (just to further narrow this down)? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ERROR: driver buffer overflow on device 1
On 24.2.2010 20:05, VDR User wrote: On Tue, Feb 23, 2010 at 10:49 AM, Joscejo...@welho.com wrote: localhost vdr: [2626] buffer usage: 70% (tid=2625) localhost vdr: [2626] buffer usage: 80% (tid=2625) localhost vdr: [2626] buffer usage: 90% (tid=2625) localhost vdr: [2626] buffer usage: 100% (tid=2625) localhost vdr: [2626] ERROR: driver buffer overflow on device 1 localhost vdr: [2626] ERROR: driver buffer overflow on device 1 (repeated over and over again) I have experienced this problem as well. However, I thought xine-lib was the culprit. I don't recall seeing it after updating my xine-lib however so you may want to try that. I've been using xine-lib-1.2 revision 11427. I don't use xine-lib, so that can't be it. Josce ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ERROR: driver buffer overflow on device 1
On 24.2.2010 09:18, Falk Spitzberg wrote: Am Dienstag, den 23.02.2010, 20:49 +0200 schrieb Josce: vdr-1.7.12 + reelbox + 2 Anysee E30C USB devices Sadly quite often my vdr stops working, with the following error: localhost vdr: [2626] buffer usage: 70% (tid=2625) localhost vdr: [2626] buffer usage: 80% (tid=2625) localhost vdr: [2626] buffer usage: 90% (tid=2625) localhost vdr: [2626] buffer usage: 100% (tid=2625) localhost vdr: [2626] ERROR: driver buffer overflow on device 1 localhost vdr: [2626] ERROR: driver buffer overflow on device 1 (repeated over and over again) Does it happen on all channels? I have the same problem, but only with HD channels. When i switch to a different channel. the problem goes away until it comes up after a while. I assume that the hdplayer on the eHD card gets stuck. Yes it seems to happen on all channels. Josce ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ERROR: driver buffer overflow on device 1
Perhaps it's the same problem as I have with my unmodded FF-Card ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ERROR: driver buffer overflow on device 1
Perhaps it's the same problem as I have with my unmodded FF-Card Same here on vdr-1.7.12 with reel snap -r14440 ( starts on update to vdr-1.7.11 ) terractec-1200 dvb-c card latest vanilla kernel sources. this is on all sky channels with resolution 1920 x 1080 If i go down to vdr-1.7.10, all problems are gone. -- Regards Gentoo Developer Joerg Bornkessel hd_bru...@gentoo.org ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ERROR: driver buffer overflow on device 1
On Tue, Feb 23, 2010 at 10:49 AM, Josce jo...@welho.com wrote: localhost vdr: [2626] buffer usage: 70% (tid=2625) localhost vdr: [2626] buffer usage: 80% (tid=2625) localhost vdr: [2626] buffer usage: 90% (tid=2625) localhost vdr: [2626] buffer usage: 100% (tid=2625) localhost vdr: [2626] ERROR: driver buffer overflow on device 1 localhost vdr: [2626] ERROR: driver buffer overflow on device 1 (repeated over and over again) I have experienced this problem as well. However, I thought xine-lib was the culprit. I don't recall seeing it after updating my xine-lib however so you may want to try that. I've been using xine-lib-1.2 revision 11427. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] ERROR: driver buffer overflow on device 1
vdr-1.7.12 + reelbox + 2 Anysee E30C USB devices Sadly quite often my vdr stops working, with the following error: localhost vdr: [2626] buffer usage: 70% (tid=2625) localhost vdr: [2626] buffer usage: 80% (tid=2625) localhost vdr: [2626] buffer usage: 90% (tid=2625) localhost vdr: [2626] buffer usage: 100% (tid=2625) localhost vdr: [2626] ERROR: driver buffer overflow on device 1 localhost vdr: [2626] ERROR: driver buffer overflow on device 1 (repeated over and over again) Just killing vdr and reloading the DVB driver doesn't fix this. I have to reboot the machine to get everything working again. Now I was wondering, when this happens how can I make vdr exit with say exit code 9, so that I can make the runvdr reboot the machine. Thanks, Josce ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ERROR: driver buffer overflow on device 1
Am Dienstag, den 23.02.2010, 20:49 +0200 schrieb Josce: vdr-1.7.12 + reelbox + 2 Anysee E30C USB devices Sadly quite often my vdr stops working, with the following error: localhost vdr: [2626] buffer usage: 70% (tid=2625) localhost vdr: [2626] buffer usage: 80% (tid=2625) localhost vdr: [2626] buffer usage: 90% (tid=2625) localhost vdr: [2626] buffer usage: 100% (tid=2625) localhost vdr: [2626] ERROR: driver buffer overflow on device 1 localhost vdr: [2626] ERROR: driver buffer overflow on device 1 (repeated over and over again) Does it happen on all channels? I have the same problem, but only with HD channels. When i switch to a different channel. the problem goes away until it comes up after a while. I assume that the hdplayer on the eHD card gets stuck. Just killing vdr and reloading the DVB driver doesn't fix this. I have to reboot the machine to get everything working again. Now I was wondering, when this happens how can I make vdr exit with say exit code 9, so that I can make the runvdr reboot the machine. Thanks, Josce ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] ERROR: driver buffer overflow on device 1 on 1080i channels
Hi my configuration is HVR-4000+firmware version 1.23.86.1+S2-Liplianin VDR 1.7.8+vdr-xine 0.9.3 Debian SID + kernel 2.6.30 AMD Sempron(tm) Processor 2800+ NVIDIA Sparkle GeForce 8400 GS 512 MB (GPU G98 A2) fanles PCI + Nvidia 185.18.14 + xine-vdpau rev. 273 with 1080i channels and temporal or half temporal_spatial deinterlacing I always have jerky and stuttering audio and video With bob , half temporal - no problems does it possible to fix that problem ? Jul 7 18:55:17 arvdr vdr: [4361] ERROR: skipped 287597 bytes to sync on TS packet on device 1 Jul 7 18:55:17 arvdr vdr: [4362] buffer usage: 10% (tid=4361) Jul 7 18:55:17 arvdr vdr: [4361] ERROR: skipped 1731910 bytes to sync on TS packet on device 1 Jul 7 18:55:17 arvdr vdr: [4361] TS continuity error (8) Jul 7 18:55:17 arvdr vdr: [4361] PES packet shortened to 2550 bytes (expected: 3470 bytes) Jul 7 18:55:18 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:55:18 arvdr vdr: [4362] buffer usage: 80% (tid=4361) Jul 7 18:55:18 arvdr vdr: [4362] buffer usage: 90% (tid=4361) Jul 7 18:55:19 arvdr vdr: [4362] buffer usage: 100% (tid=4361) Jul 7 18:55:20 arvdr vdr: [4362] ERROR: driver buffer overflow on device 1 Jul 7 18:55:20 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:55:21 arvdr vdr: [4361] ERROR: skipped 847891 bytes to sync on TS packet on device 1 Jul 7 18:55:21 arvdr vdr: [4361] TS continuity error (12) Jul 7 18:55:21 arvdr vdr: [4361] TS continuity error (9) Jul 7 18:55:23 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:55:23 arvdr vdr: [4362] buffer usage: 80% (tid=4361) Jul 7 18:55:23 arvdr vdr: [4362] buffer usage: 90% (tid=4361) Jul 7 18:55:23 arvdr vdr: [4362] buffer usage: 100% (tid=4361) Jul 7 18:55:24 arvdr vdr: [4362] ERROR: driver buffer overflow on device 1 Jul 7 18:55:25 arvdr vdr: [4362] buffer usage: 10% (tid=4361) Jul 7 18:55:25 arvdr vdr: [4361] ERROR: skipped 1899195 bytes to sync on TS packet on device 1 Jul 7 18:55:25 arvdr vdr: [4361] ERROR: skipped 391032 bytes to sync on TS packet on device 1 Jul 7 18:55:26 arvdr vdr: [4361] TS continuity error (1) Jul 7 18:55:28 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:55:28 arvdr vdr: [4362] buffer usage: 80% (tid=4361) Jul 7 18:55:28 arvdr vdr: [4362] buffer usage: 90% (tid=4361) Jul 7 18:55:28 arvdr vdr: [4362] buffer usage: 100% (tid=4361) Jul 7 18:55:30 arvdr vdr: [4362] ERROR: driver buffer overflow on device 1 Jul 7 18:55:31 arvdr vdr: [4361] ERROR: skipped 982908 bytes to sync on TS packet on device 1 Jul 7 18:55:31 arvdr vdr: [4361] ERROR: skipped 882439 bytes to sync on TS packet on device 1 Jul 7 18:55:31 arvdr vdr: [4362] buffer usage: 0% (tid=4361) Jul 7 18:55:31 arvdr vdr: [4361] TS continuity error (3) Jul 7 18:55:33 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:55:33 arvdr vdr: [4362] buffer usage: 80% (tid=4361) Jul 7 18:55:33 arvdr vdr: [4362] buffer usage: 90% (tid=4361) Jul 7 18:55:33 arvdr vdr: [4362] buffer usage: 100% (tid=4361) Jul 7 18:55:35 arvdr vdr: [4362] ERROR: driver buffer overflow on device 1 Jul 7 18:55:36 arvdr vdr: [4361] ERROR: skipped 331513 bytes to sync on TS packet on device 1 Jul 7 18:55:36 arvdr vdr: [4361] ERROR: skipped 1719014 bytes to sync on TS packet on device 1 Jul 7 18:55:36 arvdr vdr: [4361] TS continuity error (11) Jul 7 18:55:36 arvdr vdr: [4361] TS continuity error (5) Jul 7 18:55:36 arvdr vdr: [4362] buffer usage: 0% (tid=4361) Jul 7 18:58:15 arvdr vdr: [4362] buffer usage: 90% (tid=4361) Jul 7 18:58:15 arvdr vdr: [4362] buffer usage: 100% (tid=4361) Jul 7 18:58:19 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:58:19 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:58:19 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:58:19 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:58:19 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:58:19 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:58:19 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:58:19 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:58:19 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:58:22 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:58:22 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:58:22 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:58:22 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:58:23 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:58:23 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:58:23 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:58:23 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:58:23 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:58:23 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:58:23 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:58:23 arvdr vdr: [4362] buffer usage: 60% (tid=4361) Jul 7 18:58:23 arvdr vdr: [4362] buffer usage: 70% (tid=4361) Jul 7 18:58:23
