Open derkling opened 6 years ago
Hi,
Yes we had such behaviour but we still need to investigate further.
Thanks for the details
No updates on this issue?
@derkling I'm trying to reproduce your issue, but I haven't been successful so far. What is your setup exactly? How many probes are connected and what parameters do you pass over to iio-capture? How long does it need to run usually before it causes the issue?
While using an ACME CAPE for long running experiments, it happens quite frequently that we need to reboot the device because of iio-capture failing to write the
in_oversampling_ratio
attribute of a device.Not sure what's the reasons for that problem, maybe it's the driver stuck or this tool sending a wrong sequence of commands.
Have you ever noticed anything similar? If not, which kind of feedback can be useful to debug the issue.
What I can share so fare is that, once the problem occurs and the iio-capture command fails on the HOST side, if I login to the ACME cape and I try a write I still get the same error, e.g.:
The device has these tasks running:
As you can notice there is a "dead" grep (pid: 6707) for all the attributes of a device... which I don't where it comes from and I suppose it's part of the device-side of iio-capture.
Is there any other information I can provide to track down this issue?