Dnia 2009-03-17, o godz. 14:06:26 Jakub Paweł Głazik <zytek-lists@nuxi.pl> napisał(a):
I'm using TechnoTrend 1500/1600 cards (Premium-S) and they like to lockup randomly. For example I'm seeing situation when one of two configured adapters hangs and I get output only from one adapter.
dvr.c has a hack for Flexcop cards and on debug output I have seen that bouncing filter works for TT card reanimation but every now and then it does not. I would like to detect such situation, getstream could die and I would do some scripting for bringing everything up again (module reload or even reboot).
Should it be implemented in internal watchdog or in dvr_stuck_timer, maybe some retry-counter with SIGABR when reanimation does not work for a card after N tries?
I just got another card lockup: [346021.608205] dvb-ttpci: StopHWFilter error cmd 0b08 0001 0004 ret fffffe00 resp cede c01a pid 213 [346021.609881] dvb-ttpci: StopHWFilter error cmd 0b08 0001 0006 ret fffffe00 resp cede c01a pid 518 [346021.610421] dvb-ttpci: StopHWFilter error cmd 0b08 0001 0008 ret fffffe00 resp cede c01a pid 710 [346067.468097] dvb-ttpci: StopHWFilter error cmd 0b08 0001 000a ret fffffe00 resp cede c01a pid 518 [346067.469808] dvb-ttpci: StopHWFilter error cmd 0b08 0001 000b ret fffffe00 resp cf61 c01a pid 710 Getstream does not detect it. 2009-03-17 16:03:25.970 dvr: inputstats: 9 pids 4942 pkt/s 929097 byte/s It streams data but the data is invalid (not playable). This is TT card's bug as I googled (ARM crashes on the card), to bad it is invisible to getstream. If think this is another issue, one being not able to reanimate card after lockup (detectable), second - these TT cards ARM crashing and delivering garbage (not detectable ?). Any ideas how to workaround that? -- .: Jakub Paweł Głazik, .: email & jabber: zytek<at>nuxi.pl