After several hours running, the card stops receiving data
Posted: Thu Mar 21, 2013 1:44 amWe are seeing repeated problems with data just stopping.
This has occurred running just a single Quad S2 or a single Quad T2.
Symptoms:
After several hours running, the card stops receiving data. It continues to report itself locked when queried with FE_READ_STATUS, but the dvr fd never becomes readable again. Interrupts stop counting up. There is nothing in dmesg. Retuning the card doesn't fix it. A reboot of the machine does. Tested with kernels 3.7.9-030709-generic and linux-image-3.2.0-23-lowlatency on ubuntu.
I was using 130127 drivers. I've just noticed there is a new one 130318, which I'm going to try (would be nice if there was a change log which might say "fixed random hang of data stream"... But there isn't, so I'll just have to run it for a week).
Anyway, has anyone seen this? Any suggestions?
This has occurred running just a single Quad S2 or a single Quad T2.
Symptoms:
After several hours running, the card stops receiving data. It continues to report itself locked when queried with FE_READ_STATUS, but the dvr fd never becomes readable again. Interrupts stop counting up. There is nothing in dmesg. Retuning the card doesn't fix it. A reboot of the machine does. Tested with kernels 3.7.9-030709-generic and linux-image-3.2.0-23-lowlatency on ubuntu.
I was using 130127 drivers. I've just noticed there is a new one 130318, which I'm going to try (would be nice if there was a change log which might say "fixed random hang of data stream"... But there isn't, so I'll just have to run it for a week).
Anyway, has anyone seen this? Any suggestions?