Hi, > The hang is 100% reproducible. I haven't tried reverting to > check that the hang disappears (to rule out e.g. a new hardware > fault), but that's probably a good sanity-check for me to do > soon.
I got a serial port hooked up to the machine. Here's the last thing we see on the kernel console and in the Xorg log: [drm:radeon_fence_wait] *ERROR* fence(df3689b0:0x0000A1A5) 552ms timeout [drm:radeon_fence_wait] *ERROR* last signaled fence(0x0000A1A5) [drm:radeon_fence_wait] *ERROR* fence(df368d70:0x0000A1AE) 505ms timeout going to reset GPU [drm] RB2D reset succeed (RBBM_STATUS=0x8007C100) [drm] CP reset succeed (RBBM_STATUS=0x8006C100) [drm] radeon: cp idle (0x00008080) [drm] radeon: ring at 0x00000000C0000000 [drm] ring test succeeded in 2 usecs [drm] GPU reset succeed (RBBM_STATUS=0x00000140) [drm:radeon_fence_wait] *ERROR* fence(df368d70:0x0000A1AE) 556ms timeout [drm:radeon_fence_wait] *ERROR* last signaled fence(0x0000A1AE) [drm:radeon_fence_wait] *ERROR* fence(df368730:0x0000BD1E) 516ms timeout [drm:radeon_fence_wait] *ERROR* last signaled fence(0x0000BD1E) [drm:radeon_fence_wait] *ERROR* fence(df3689b0:0x0000BD24) 506ms timeout going to reset GPU [drm] RB2D reset succeed (RBBM_STATUS=0x8007C100) [drm] CP reset succeed (RBBM_STATUS=0x8002C100) [drm] radeon: cp idle (0x00008080) radeon: wait for empty RBBM fifo failed ! Bad things might happen. Failed to wait GUI idle while programming pipes. Bad things might happen. [drm] radeon: ring at 0x00000000C0000000 <machine hung> - Chris. -- Chris Ball <c...@laptop.org> One Laptop Per Child _______________________________________________ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com