On tor, 2006-02-23 at 22:18 +0100, Jörg Dreßler wrote:
> Hi,
> yes, i get this too:
> Feb 22 18:43:13 fortress kernel: bt878(0): irq FDSR risc_pc=312311d0
> Feb 22 18:43:13 fortress kernel: bt878(0): irq SCERR risc_pc=31231000
> Feb 22 18:43:13 fortress kernel: bt878(0): irq FDSR risc_pc=31231008
> Feb 22 18:43:13 fortress kernel: bt878(0): irq FDSR risc_pc=31231008
> {...}
> Feb 22 21:04:51 fortress kernel: bt878(0): irq FDSR risc_pc=31231008
> Feb 22 21:04:51 fortress kernel: bt878(0): irq FDSR risc_pc=31231008
> Feb 22 21:04:51 fortress kernel: bt878(0): IRQ lockup, cleared int mask
>
> at the beginning and in between.
So at least you have the same issue as me, except it seems to happen
much more often for you than for me. According to the documentation for
the bt878 SCERR is a fatal error and capturing must be completly
restarted. Current code does nothing with this error except printing
above mentioned line, this obviously need to be fixed. unloading and
reloading all relevant modules supposedly cleans this situation, but I
don't think it worked for me, I had to reboot...
Regards
Sigmund
>
> Jörg
>
> > The FBUS error you see in your first case means the card had to dump
> > data because it didn't get access to the pci bus before it's internal
> > buffer overflowed. The controlreg change you did should reduce the
> > chances of getting the FBUS error, it should however (as I understand
> > it) not have anything to do with your other problems. What are the last
> > few messages before the mentioned 40-50 pages? (tip: install a sysloger
> > with "last message repeated NN times" feature). I have on some occations
> > gotten a SCERR error which usually gets followed by log patterns such as
> > what you show in the second example.
> >
> > Also, please try latest v4l-dvb from hg, to make sure you are not
> > suffering from an allready fixed bug.
> >
> > Sigmund
> >
>
_______________________________________________
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
