Comment 4 for bug 1938163

Revision history for this message
Julian Andres Klode (juliank) wrote :

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.