There are three possible causes
- firmware bug - kernel bug - user error (read-only variables), though why does that give I/O rather than ENOSPACE
I'm going to reassign this one to linux for a check on the kernel side, but I suspect it's a firmware issue.
There are three possible causes
- firmware bug
- kernel bug
- user error (read-only variables), though why does that give I/O rather than ENOSPACE
I'm going to reassign this one to linux for a check on the kernel side, but I suspect it's a firmware issue.