nanogui: Thread: nano-X: GsRead failed -1 0: 131

Hi

I am struggling with an error.
Am running a demo setup where a nano-x app is started and exited  many many times.

But the sometimes the app stops, i get "nano-X: GsRead failed -1 0: 131" on terminal, and the app i wrote is not killable as it sits in kernelspace lock'd in a disk read.
looks like this in ps

  907 root        652 S   nano-X
  913 root        272 S   nanowm
  915 root            DW  [pmmd_big]


Looking in the source it seams that the error on terminal is coming from the server.
If I look in /proc/915/fd no files is open by pmmd_big

I only found few pointers in archive about this, but no real help.

Regards

Martin Hansen

> But the sometimes the app stops, i get "nano-X: GsRead failed -1 0: 131" on terminal, and the app i wrote is not killable as it sits in kernelspace 
> lock'd in a disk read.
Further logging shows that it is the call to getNectEvent, and even getNectEventTimeout, I sense a smell of error in the select() in uClib.


Regards 

Martin Hansen

> Further logging shows that it is the call to getNectEvent, and even 
> getNectEventTimeout, I sense a smell of error in the select() in uClib.

Well, the client will be hanging on a pipe read from the
network socket connection to the server.  Could be
a strange kernel issue where for some reason the
client process can't be awoken and hangs after the
other process side of the pipe is killed... ?

If you only have one application running, then you
can use the LINK_APP_INTO_SERVER option
and eliminate the pipe connection.

Regards,

Greg