Sunday, May 8, 2011, 12:23:21 PM, you wrote: > I installed the latest s2-liplianin drivers, but I still seem to have > the same issue. The card works fine for some time after reboot, then I > am starting to get the following errors in the system log: > May 8 11:11:38 localhost kernel: ds3000_readreg: reg=0xa1(error=-5) > May 8 11:11:38 localhost kernel: ds3000_readreg: reg=0xa1(error=-5) > May 8 11:11:38 localhost kernel: ds3000_readreg: reg=0xa1(error=-5) > May 8 11:11:38 localhost kernel: ds3000_writereg: writereg > error(err == -5, reg == 0xa1, value == 0x7b) > May 8 11:11:38 localhost kernel: ds3000_readreg: reg=0xa2(error=-5) > May 8 11:11:38 localhost kernel: ds3000_writereg: writereg > error(err == -5, reg == 0xa2, value == 0xbb) > And then my machine just stops responding - even on the ssh sessions. > A friend of mine installed the same S470 card a few days ago. He's > using Fedora 14 (kernel 2.6.35) and he says his machine started to > 'hang' sporadically, too... I guess he might have a similar issue... > How could I track what is going on? Dear All, I still have this very annoying issue. I see no obvious reason, but my DVB-S card just stops locking the signal, I get really a lot of these errors in my syslog: May 9 19:04:33 localhost kernel: ds3000_readreg: reg=0xd(error=-5) May 9 19:04:33 localhost kernel: ds3000_writereg: writereg error(err == -5, reg == 0x03, value == 0x12) May 9 19:04:33 localhost kernel: ds3000_tuner_readreg: reg=0x3d(error=-5) May 9 19:04:33 localhost kernel: ds3000_writereg: writereg error(err == -5, reg == 0x03, value == 0x12) May 9 19:04:33 localhost kernel: ds3000_tuner_readreg: reg=0x21(error=-5) May 9 19:04:33 localhost kernel: ds3000_readreg: reg=0x8c(error=-5) May 9 19:04:33 localhost kernel: ds3000_readreg: reg=0x8d(error=-5) and then the machine just freezes. Could it be some buffer overflow? How could I track it? The machine is perfectly stable when S470 card is out... -- Best regards, Andrew -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
