TBSDTV Community Forum

I now have Windows 7 running from a USB drive but I could still use some advice on suitable test SW.

Yes, it's the first 8 bytes that appears to be left from the last packet that used the same buffer in memory. I suppose it could be driver related but since it's 8 bytes in the "middle" of a 64KB buffer my first guess would be HW. I'd be happy to test in Windows too if I could get some adv...

Derrick Wrote:Could you check this with windows as well?

Possibly, if Windows could be run from a CD or USB drive and I could get some suggestions on SW to use for tuning and capturing full TS.

Please let me know if anyone is looking into this.

Btw, I forgot to mention that the bad packet seems to be located at an arbitrary position in the DMA buffer, not at a boundary. I had added a packet index counter to syslog, see below. Count = 204 means packet nr 348 - 204 = 144 in DMA buffer. Mar 6 18:27:36 PE2950 kernel: [267060.428630] TS packet ...

I've now captured the failing stream on two tuners simultaneously for comparison. The two captured streams were identical except for a few bytes in one packet that caused the continuity counter errors. The bytes that differed were bytes at offset 2-7. The bad packet started with 47 02 03 93 01 95 51...

I agree, it does sound like insufficient data transfer performance somewhere in the system and I've been examining IRQ timings and PCIe buffer transfers for hours today. Btw, my computer is a Dell PowerEdge 2950 III with dual Xeon L5420 @ 2.5GHz. I tried your proposed driver but the problem remained...

I am suffering from continuity counter errors despite having a seemingly fine signal on the affected tuner (SNR > 90%). I can reproduce one failure mode using the test script below. When one tuner is in use there are no cc errors, when the other three tuners are enabled I start getting errors as can...