Ok, I have to admit that I haven't updated the kernel and the driver since I have to stick with 2.4.x kernels for some time and the latest cvs version won't compile with 2.4. I'll probably move to the newer versions (or backport the latest linuxdvb to 2.4), but I want to track down this problem to make sure the same problem won't occur again. Actually I have some interesting register dumps common to all boxes with the same problem. After the flexcop chipset stopped generating interrupts even with the good signal status, the register 0x20c (Status register : reading this register deasserts INTA) is read 0x00000100 (Data_receive_error). But shouldn't this register have been already cleared in the interrupt handler? Is this normal that this bit can be still set and the interrupt is not generated? All 8 boxes I tested resulted in the same register values on 0x20c. And reading this register didn't make the flexcop to generate interrupts again. Is there anything I could do to debug it further (in both s/w and h/w wise)? Here's more register dumps: #1 [INBT:104907]# ./dreg 0 Rx[0x000] = 0x06540001 [INBT:104907]# ./dreg 4 Rx[0x004] = 0x00758001 [INBT:104907]# ./dreg 8 Rx[0x008] = 0x0656ac70 [INBT:104907]# ./dreg 8 Rx[0x008] = 0x0656ac70 [INBT:104907]# ./dreg 0xc Rx[0x00c] = 0x0655d601 [INBT:104907]# ./dreg 0x208 Rx[0x208] = 0x000380c1 [INBT:104907]# ./dreg 0x604 Rx[0x604] = 0x08000000 [INBT:104907]# ./dreg 0x20c Rx[0x20c] = 0x00000100 [INBT:104907]# ./dreg 0x700 Rx[0x700] = 0x045a8000 [INBT:104907]# ./dreg 0x714 Rx[0x714] = 0x00000069 #2 [INBT:104825]# ./dreg 0 Rx[0x000] = 0x06540001 [INBT:104825]# ./dreg 4 Rx[0x004] = 0x00758001 [INBT:104825]# ./dreg 4 Rx[0x004] = 0x00758001 [INBT:104825]# ./dreg 8 Rx[0x008] = 0x065798e8 [INBT:104825]# ./dreg 8 Rx[0x008] = 0x065798e8 [INBT:104825]# ./dreg 0xc Rx[0x00c] = 0x0655d601 [INBT:104825]# ./dreg 0x208 Rx[0x208] = 0x000380c1 [INBT:104825]# ./dreg 0x20c Rx[0x20c] = 0x00000100 [INBT:104825]# ./dreg 0x20c Rx[0x20c] = 0x00000000 [INBT:104825]# ./dreg 0x208 Rx[0x208] = 0x000380c1 [INBT:104825]# ./dreg 0x604 Rx[0x604] = 0x08000080 [INBT:104825]# ./dreg 0x700 Rx[0x700] = 0x045a8000 [INBT:104825]# ./dreg 0x604 Rx[0x604] = 0x08000080 [INBT:104825]# ./dreg 0x714 Rx[0x714] = 0x00000069 On 4/14/05, Patrick Boettcher <patrick.boettcher@xxxxxxx> wrote: > On Thu, 14 Apr 2005, Q-ha Park wrote: > > > Hi, > > > >> > >>> b2c2 flexcop chipset doesn't generate interrupts while receiving data > >>> continuously appx. for 10 days. I think some people on the list > >>> already experienced the same problem, but it wasn't obvious where the > >>> root cause of this. Is anyone after this? > >> > >> Which drivers/kernel are you using? > >> > > I'm using the old kernel, 2.4.20 with linuxtv-dvb-1.1.1 > > _A lot_ of work has been done on skystar2-driver since then. Even the > name has changed :). > > The modules are now called (when compiled) b2c2-flexcop.ko and > b2c2-flexcop-pci.ko. > > If you are using "normal" machines I suggest you try the version from CVS > together with 2.6.9 (or higher). > > best regards > Patrick. > > -- > Mail: patrick.boettcher@xxxxxxx > WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/ > > _______________________________________________ > > linux-dvb@xxxxxxxxxxx > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >
