2014-07-08 9:57 GMT+04:00, Martin Decky <[email protected]>: > There are actually very few places where ETIMEOUT is returned. It can be > returned by async_wait_timeout() and fibril_condvar_wait_timeout(). Not > sure how it might happen in compositor, as far as I can tell it does not > use any routines with timeout. > > Are you sure this is not some spurious error again, caused by protocol > desynchronization?
I see I confused you. It was before your patch for graph.c, so of course it happens due to protocol desynchronization. I wanted to know the exact cause of compositor output freezing. I examined return code in visualizer_update_damaged_region() and saw that it becomes ETIMEOUT after vs_enumerate_modes() fais to retrieve nth element in list and executes "else" branch answering ENOENT to iid. So I wasn't right, it is not hangup. _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
