[vdr] Re: ERROR (dvbapi.c,550): DVB driver buffer overflow

[tfrerichs@gmx.de]

 Hi Klaus, 

thanks for your response. 

Lastly I recognized that the dma harddisk transfer is not used on my system
although it is enabled via the SUSE 7.2 configuration. 

I remember there was a description somewhere saying that ASUS p5a/SUSE 7.2
isworking well with vdr with onboard ide interface?!

Thomas




tfrerichs@gmx.de wrote:
>
>Dear all,
>
>after successful installation of vdr (current one is 0.97 with driver
>dvb-20011030) i got the following errors in /var/log/messages when
recording.
>Has anyone an idea what the cause of it is?
>My system is an ASUS p5a, AMD KII/550, 96 MBytes RAM, Siemens DVB-S,
>WD600AB harddisk.
>
>Nov  5 13:30:01 vdr vdr[998]: output thread started (pid=998)
>Nov  5 13:30:01 vdr vdr[999]: input thread started (pid=999)
>Nov  5 13:30:05 vdr vdr[999]: buffer usage: 76%
>Nov  5 13:30:05 vdr last message repeated 4 times
>Nov  5 13:30:05 vdr vdr[999]: buffer usage: 77%
>Nov  5 13:30:05 vdr last message repeated 5 times
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 78%
>Nov  5 13:30:06 vdr last message repeated 4 times
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 79%
>Nov  5 13:30:06 vdr last message repeated 3 times
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 80%
>Nov  5 13:30:06 vdr last message repeated 4 times
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 81%
>Nov  5 13:30:06 vdr last message repeated 4 times
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 82%
>Nov  5 13:30:06 vdr last message repeated 4 times
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 83%
>Nov  5 13:30:06 vdr last message repeated 4 times
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 84%
>Nov  5 13:30:06 vdr last message repeated 5 times
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 85%
>Nov  5 13:30:06 vdr last message repeated 4 times
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 86%
>Nov  5 13:30:06 vdr last message repeated 5 times
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 87%
>Nov  5 13:30:06 vdr last message repeated 3 times
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 88%
>Nov  5 13:30:06 vdr last message repeated 3 times
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 89%
>Nov  5 13:30:06 vdr last message repeated 3 times
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 90%
>Nov  5 13:30:06 vdr last message repeated 4 times
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 91%
>Nov  5 13:30:06 vdr last message repeated 5 times
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 92%
>Nov  5 13:30:06 vdr last message repeated 4 times
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 93%
>Nov  5 13:30:06 vdr last message repeated 4 times
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 94%
>Nov  5 13:30:06 vdr last message repeated 5 times
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 95%
>Nov  5 13:30:06 vdr last message repeated 6 times
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 96%
>Nov  5 13:30:06 vdr last message repeated 4 times
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 97%
>Nov  5 13:30:06 vdr last message repeated 2 times
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 98%
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 98%
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 99%
>Nov  5 13:30:06 vdr last message repeated 5 times
>Nov  5 13:30:06 vdr vdr[999]: buffer usage: 100%

VDR's buffer (which is 1MB in size) has run full of video data.

>Nov  5 13:30:08 vdr vdr[999]: ERROR (dvbapi.c,550): DVB driver buffer
overflow
>Nov  5 13:30:12 vdr last message repeated 3 times
>Nov  5 13:30:14 vdr vdr[998]: ERROR: skipped 120 byte to sync on TS packet
>Nov  5 13:30:14 vdr vdr[999]: ERROR (dvbapi.c,550): DVB driver buffer
overflow
>Nov  5 13:30:15 vdr vdr[998]: ERROR: skipped 64 byte to sync on TS packet
>Nov  5 13:30:16 vdr vdr[998]: ERROR: skipped 64 byte to sync on TS packet
>Nov  5 13:30:17 vdr vdr[999]: ERROR (dvbapi.c,550): DVB driver buffer
overflow
>Nov  5 13:30:18 vdr vdr[998]: ERROR: skipped 16 byte to sync on TS packet

Now it's getting really ugly, since the DVB driver's internal buffer has
also
run full.

Looks as if VDR is unable to write anything to disk - but then again I would
expect some other error messages regarding disk access errors.
This is really strange, I can't see why this is happeneing...

Which channel are you trying to record?
Does this happen with _any_ channel or only on specific ones?

Klaus
-- 
_______________________________________________________________

Klaus Schmidinger                       Phone: +49-8635-6989-10
CadSoft Computer GmbH                   Fax:   +49-8635-6989-40
Hofmark 2                               Email:   kls@cadsoft.de
D-84568 Pleiskirchen, Germany           URL:     www.cadsoft.de[1]
_______________________________________________________________




--- Links ---
   1 http://www.cadsoft.de/