glxgears: *possible* hang in MAIN graphics engine
glxgears: *possible* hang in MAIN graphics engine
- Subject: glxgears: *possible* hang in MAIN graphics engine
- From: René J.V. Bertin <email@hidden>
- Date: Sun, 29 Mar 2015 16:38:55 +0200
This may be nothing but it sure feels worrisome :
1) run /opt/X11/bin/glxgears from the current XQuartz version
2) after a bit, close its window through the close button on the titlebar
3) fear the whole computer crashed for a couple of seconds
4) Find the following message on the terminal
XIO: fatal IO error 22 (Invalid argument) on X server ":0"
after 27 requests (27 known processed) with 0 events remaining.
Exit 1
5) check the system.log and see
Mar 29 16:30:23 Portia kernel[0]: stampWait: Overflowed checking for stamp 0x5421285d on MAIN ring: called from
Mar 29 16:30:23 Portia kernel[0]: timestamp = 0x5421285c
Mar 29 16:30:23 Portia kernel[0]: **** Debug info for *possible* hang in MAIN graphics engine ****
Mar 29 16:30:23 Portia kernel[0]: ring head = 0x6020c8b0, wrap count = 769
Mar 29 16:30:23 Portia kernel[0]: ring tail = 0x0000c8b0
Mar 29 16:30:23 Portia kernel[0]: ring control = 0x0000f001 enabled, auto report disabled, not waiting, semaphore not waiting, length = 0x010 4KB pages
Mar 29 16:30:23 Portia kernel[0]: timestamps = 0x5421285c
Mar 29 16:30:23 Portia kernel[0]: Semaphore register values:
Mar 29 16:30:23 Portia kernel[0]: VRSYNC: (0x12044) = 0x5421285c
Mar 29 16:30:23 Portia kernel[0]: BRSYNC: (0x22040) = 0x0
Mar 29 16:30:23 Portia kernel[0]: RVSYNC: (0x 2040) = 0x0
Mar 29 16:30:23 Portia kernel[0]: BVSYNC: (0x22044) = 0x0
Mar 29 16:30:23 Portia kernel[0]: RBSYNC: (0x 2044) = 0x0
Mar 29 16:30:23 Portia kernel[0]: VBSYNC: (0x12040) = 0x0
Mar 29 16:30:28 Portia kernel[0]: stampWait: Overflowed checking for stamp 0x5421285d on MAIN ring: called from
Mar 29 16:30:28 Portia kernel[0]: timestamp = 0x5421285c
Mar 29 16:30:28 Portia kernel[0]: **** Debug info for *possible* hang in MAIN graphics engine ****
Mar 29 16:30:28 Portia kernel[0]: ring head = 0x6020c8b0, wrap count = 769
Mar 29 16:30:28 Portia kernel[0]: ring tail = 0x0000c8b0
Mar 29 16:30:28 Portia kernel[0]: ring control = 0x0000f001 enabled, auto report disabled, not waiting, semaphore not waiting, length = 0x010 4KB pages
Mar 29 16:30:28 Portia kernel[0]: timestamps = 0x5421285c
Mar 29 16:30:28 Portia kernel[0]: Semaphore register values:
Mar 29 16:30:28 Portia kernel[0]: VRSYNC: (0x12044) = 0x5421285c
Mar 29 16:30:28 Portia kernel[0]: BRSYNC: (0x22040) = 0x0
Mar 29 16:30:28 Portia kernel[0]: RVSYNC: (0x 2040) = 0x0
Mar 29 16:30:28 Portia kernel[0]: BVSYNC: (0x22044) = 0x0
Mar 29 16:30:28 Portia kernel[0]: RBSYNC: (0x 2044) = 0x0
Mar 29 16:30:28 Portia kernel[0]: VBSYNC: (0x12040) = 0x0
Mar 29 16:30:33 Portia kernel[0]: stampWait: Overflowed checking for stamp 0x5421285d on MAIN ring: called from
Mar 29 16:30:33 Portia kernel[0]: timestamp = 0x5421285c
Mar 29 16:30:33 Portia kernel[0]: **** Debug info for *possible* hang in MAIN graphics engine ****
Mar 29 16:30:33 Portia kernel[0]: ring head = 0x6020c8b0, wrap count = 769
Mar 29 16:30:33 Portia kernel[0]: ring tail = 0x0000c8b0
Mar 29 16:30:33 Portia kernel[0]: ring control = 0x0000f001 enabled, auto report disabled, not waiting, semaphore not waiting, length = 0x010 4KB pages
Mar 29 16:30:33 Portia kernel[0]: timestamps = 0x5421285c
Mar 29 16:30:33 Portia kernel[0]: Semaphore register values:
Mar 29 16:30:33 Portia kernel[0]: VRSYNC: (0x12044) = 0x5421285c
Mar 29 16:30:33 Portia kernel[0]: BRSYNC: (0x22040) = 0x0
Mar 29 16:30:33 Portia kernel[0]: RVSYNC: (0x 2040) = 0x0
Mar 29 16:30:33 Portia kernel[0]: BVSYNC: (0x22044) = 0x0
Mar 29 16:30:33 Portia kernel[0]: RBSYNC: (0x 2044) = 0x0
Mar 29 16:30:33 Portia kernel[0]: VBSYNC: (0x12040) = 0x0
This is on a 13" MacBookPro8,1 with a 2.7Ghz i7 and Intel HD3000 graphics (and 12Gb RAM, so there should be 512Mb allocated for graphics).
All other things being equal, port:glxgears does not show this behaviour.
Is this a bug that will be addressed in a future XQuartz release (and/or that should be avoided because of implications for system stability)?
R.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden