On Wed, Nov 08, 2017 at 12:07:15PM +0100, Richard Genoud wrote: > (maybe if there was more than one CPU on the board, I could do > something, but that's not the case) I reproduced the problem with nosmp option. I think we need to check also for ENOENT error (not only for ENODEV). Will post the fix in a second. Thanks for reporting and debugging Stanislaw
