On Thu, May 26, 2016 at 05:54:30PM -0400, Andre Smagin wrote: > On Sat, 14 May 2016 21:01:29 +0200 (CEST) > [email protected] wrote: > > > >Synopsis: radeon(4) drm crashing on current/amd64 > [...] > > drm:pid77501:radeon_fence_wait_empty_locked *ERROR* error waiting for > > ring[3] to become idle (-1601868) > > > I am seeing the same issue, very infrequently (may be once every week or two): > > drm:pid55825:radeon_fence_wait_empty_locked *ERROR* error waiting for ring[3] > to become idle (-6007676) > i3(49392): syscall 97 "inet" > > Not sure what happens to i3 as X crashes, but I get that pledge message every > time. > (Previously mentioned i3 to dcoppa, but before realizing it was related to > radeon issue.)
I combed through the i3 source code hoping to get an indication what might be the cause for that socket(2) call breaking a pledge promise i3. I couldn't find anything: all socket calls are with AF_LOCAL that should be covered by the "unix" pledge. Without seeing a ktrace output, I don't think I can make any progress here.
