David Johnson wrote: >Hi all, > >I'm using a Nebula DVB-T PCI card with the mt352 frontend [1] and am having >problems with the card stopping sending data. I'm using the DVB drivers in >kernel 2.6.13-rc4, which are very close to if not identical to those in the >current dvb-kernel CVS. > >I'm using mplayer as a viewer (I've tried with others too and get the same >issue, so I'm confident this isn't a viewer bug) which starts up OK and I can >watch TV. However after a random time, normally between 10 seconds and 10 >minutes, the card stops sending data and mplayer dies: > >dvb_streaming_read, attempt N. 6 failed with errno 0 when reading 1640 bytes >dvb_streaming_read, attempt N. 5 failed with errno 0 when reading 1640 bytes >dvb_streaming_read, attempt N. 4 failed with errno 0 when reading 1640 bytes >dvb_streaming_read, attempt N. 3 failed with errno 0 when reading 1640 bytes >dvb_streaming_read, attempt N. 2 failed with errno 0 when reading 1640 bytes >dvb_streaming_read, attempt N. 1 failed with errno 0 when reading 1640 bytes >dvb_streaming_read, attempt N. 6 failed with errno 0 when reading 2048 bytes >dvb_streaming_read, attempt N. 5 failed with errno 0 when reading 2048 bytes >dvb_streaming_read, attempt N. 4 failed with errno 0 when reading 2048 bytes >dvb_streaming_read, attempt N. 3 failed with errno 0 when reading 2048 bytes >dvb_streaming_read, attempt N. 2 failed with errno 0 when reading 2048 bytes >dvb_streaming_read, attempt N. 1 failed with errno 0 when reading 2048 bytes >dvb_streaming_read, return 0 bytes >TS_PARSE: COULDN'T SYNC > >As I'm watching TV, I'm getting lots of the following messages in demsg: > >bt878(0): irq FDSR FBUS risc_pc=1fc66010 >bt878(0): irq FBUS risc_pc=1fc66158 >bt878(0): irq FBUS risc_pc=1fc66158 >bt878(0): irq FBUS risc_pc=1fc66040 >bt878(0): irq FBUS risc_pc=1fc66040 >bt878(0): irq FBUS risc_pc=1fc66198 >bt878(0): irq FBUS risc_pc=1fc661a0 >bt878(0): irq FBUS risc_pc=1fc66080 >bt878(0): irq FDSR FBUS risc_pc=1fc660b8 >bt878(0): irq FBUS risc_pc=1fc66170 >bt878(0): irq FBUS risc_pc=1fc66210 >bt878(0): irq FDSR FBUS risc_pc=1fc66210 >bt878(0): irq FDSR FBUS risc_pc=1fc66210 >bt878(0): irq FDSR FBUS risc_pc=1fc66210 >bt878(0): irq FDSR FBUS risc_pc=1fc66210 >bt878(0): irq FDSR FBUS risc_pc=1fc66210 >bt878(0): irq FDSR FBUS risc_pc=1fc66210 >bt878(0): irq FDSR FBUS risc_pc=1fc66210 >bt878(0): irq FDSR FBUS risc_pc=1fc66210 >bt878(0): irq FDSR FBUS risc_pc=1fc66210 >bt878(0): irq FDSR FBUS risc_pc=1fc66210 >bt878(0): irq FDSR FBUS risc_pc=1fc66210 >bt878(0): irq FDSR FBUS risc_pc=1fc66210 >bt878(0): irq FDSR FBUS risc_pc=1fc66210 >bt878(0): irq FDSR FBUS risc_pc=1fc66210 >bt878(0): irq FDSR FBUS risc_pc=1fc66210 >bt878(0): irq FDSR FBUS risc_pc=1fc66210 >bt878(0): irq FDSR FBUS risc_pc=1fc66210 >bt878(0): irq FDSR FBUS risc_pc=1fc66210 >bt878(0): irq FDSR FBUS risc_pc=1fc66210 >bt878(0): irq FDSR FBUS risc_pc=1fc66210 >bt878(0): irq FDSR FBUS risc_pc=1fc66210 > >Then when the card stops sending data and mplayer dies, I get the following in >dmesg: > >bt878(0): IRQ lockup, cleared int mask > >If I restart mplayer it opens the card fine and I can carry on where I left >off - until it happens again. > >Any advice would be greatfully received and I'd be more than happy to help >debug this if it's a bug (as long as someone tells me how!). > >Thanks in advance, >David. > >[1] made to work using the code from this patch: >http://www.linuxtv.org/pipermail/linux-dvb/2005-April/001479.html > >_______________________________________________ > >linux-dvb@xxxxxxxxxxx >http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > > > I had exactly the same problem with a avermedia 771 with the same front end. The way I fixed it was to edit drivers/media/dvb/bt8xx/bt878.c on line 330 changing 20 to 120, this number I think is the number of errors a device can handle before giving up, a better solution would be to attempt to restart the stream rather than simply stopping it. Matt
