[vdr] Re: "Video Data Stream Broken" only happens with kernel.org Kernel on my system

["christian jacobsen" <Christian.Jacobsen@stageholding.de>]

Hallo, 

> Then I started getting "Video Data Stream Broken" errors and tried to
> find out what it was. It always happend when I was recoding something
> early in the morning when the Server was fresh started (Server is
> shutting down at night and started with nvram-wakeup).
> 
> I found the following in the syslog while starting the DVB driver :
> Aug 21 20:07:56 vdr vdr[1663]: video device offset is 0 
> Aug 21 20:07:56 vdr vdr[1687]: EIT processing thread started 
> (pid=1687)
> - master 
> Aug 21 20:07:56 vdr vdr[1688]: tuner thread started on device 1
> (pid=1688) 
> Aug 21 20:07:56 vdr vdr[1663]: probing /dev/dvb/adapter1/frontend0 
> Aug 21 20:07:56 vdr kernel: saa7146(1): irq loop 11 
> Aug 21 20:07:56 vdr kernel: saa7146(1): irq loop 12 
> Aug 21 20:07:56 vdr kernel: saa7146(1): irq loop 13 
> Aug 21 20:07:56 vdr kernel: saa7146(1): irq loop 14 
> Aug 21 20:07:56 vdr kernel: saa7146(1): irq loop 15 
> Aug 21 20:07:56 vdr kernel: saa7146(1): irq loop 16 
> Aug 21 20:07:56 vdr kernel: saa7146(1): irq loop 17 
> Aug 21 20:07:56 vdr kernel: saa7146(1): irq loop 18 
> Aug 21 20:07:56 vdr kernel: saa7146(1): irq loop 19 
> Aug 21 20:07:56 vdr kernel: saa7146(1): irq loop 20 
> Aug 21 20:07:56 vdr kernel: saa7146(1): irq loop 21 
> Aug 21 20:07:56 vdr kernel: saa7146(1): IRQ lockup, cleared int mask 
> Aug 21 20:07:56 vdr vdr[1690]: EIT processing thread started 
> (pid=1690) 
> Aug 21 20:07:56 vdr vdr[1691]: tuner thread started on device 2
> (pid=1691) 
> Aug 21 20:07:56 vdr vdr[1663]: probing /dev/dvb/adapter2/frontend0 
> Aug 21 20:07:56 vdr vdr[1663]: found 2 video devices
> 
> I found others having the same messages in the linux-dvb but no
> solution.
> It must have something to do with IRQ ;) though ... 

FYI.

Some very strange things happend ...

I earlyer found a way that the secondary card could have it's own IRQ
but it did not help..
10 days ago I tried again and on the first boot next day I had this
error again, but from the second day on it disappeared and now
everything is fine :)

The First card (rev. 1.6) don't mind sharing it's IRQ with the
Networkcard, previously the second card shared ist IRQ with that "card"
(onboard) !?

Well just wanted to tell that my troubles are gone.

Greetings
Christian Jacobsen