>
> 041ad449683bb2d54a7f082d78ec15bbc958a175 introduced stats gathering
> into the dib7000p code which seems to generate a lot more i2c traffic which
> would exacerbate the problem, if one existed. The timing (May/June) very
> roughly matches what I remember too. When my recording stops, so do the
> "Next all layers stats available in..." messages, although that could be for
> other reasons.
>
> Anyway, I'll comment out the call to dib7000p_get_stats and see if it makes a
> difference.
>
That didn't help.
Having chmod 0000'd /dev/dvb/adapter1 so that mythtv can't open the second tuner, things have been absolutely solid for a week. As soon as I let mythtv access the second tuner it hangs almost immediately.
Based on a bunch of printk's I added, the tuner loses sync/lock which would explain why buffer delivery stops. I had been looking in the wrong place. I can't see anything happening when this happens though, it doesn't seem to coincide with gathering stats or anything but I can't be completely sure.
Other things I have observed when things stop working are:
DiB7000P: i2c read error (often)
DiB0070 I2C read failed (less often)
DiB0070 I2C write failed (less often)
NMI: PCI system error (SERR) for reason b1 on CPU 0. (rarely)
Where could the two tuners be treading on each other?
Thanks
James
��.n��������+%������w��{.n�����{��g����^n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�
