https://bugs.freedesktop.org/show_bug.cgi?id=100995
Bug ID: 100995 Summary: System hang using OpenGL 4+ features Product: Mesa Version: 17.0 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel@lists.freedesktop.org Reporter: Paul.Hancock.17041993@live.com QA Contact: dri-devel@lists.freedesktop.org
This is easily reproducible via unigine's heaven benchmark, simply running it with normal tessellation settings results in the screen flashing black a few times and then an eventual system hang before anything even starts to render. A power cycle is the only way out.
Simply creating a 4.5 context will not trigger the bug, haven't been able to fully test what causes the hang specifically as accessible tools I've found are not compatible with mesa due to only creating a default context (which is currently 3.0), thus crashing on init.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689408
https://bugs.freedesktop.org/show_bug.cgi?id=100995
--- Comment #1 from Michel Dänzer michel@daenzer.net --- Please attach the output of glxinfo and dmesg and the Xorg log file.
https://bugs.freedesktop.org/show_bug.cgi?id=100995
--- Comment #2 from Paul Paul.Hancock.17041993@live.com --- Created attachment 131303 --> https://bugs.freedesktop.org/attachment.cgi?id=131303&action=edit errors that appear to be related to the hang
errors that appear to be related to the hang
https://bugs.freedesktop.org/show_bug.cgi?id=100995
--- Comment #3 from Paul Paul.Hancock.17041993@live.com --- Created attachment 131304 --> https://bugs.freedesktop.org/attachment.cgi?id=131304&action=edit glxinfo, should contain all the hardware and package info needed
glxinfo, should contain all the hardware and package info needed
https://bugs.freedesktop.org/show_bug.cgi?id=100995
--- Comment #4 from Paul Paul.Hancock.17041993@live.com --- Created attachment 131305 --> https://bugs.freedesktop.org/attachment.cgi?id=131305&action=edit dmesg
dmesg
(In reply to Michel Dänzer from comment #1)
Please attach the output of glxinfo and dmesg and the Xorg log file.
Already in the process of dumping files...
https://bugs.freedesktop.org/show_bug.cgi?id=100995
--- Comment #5 from Michel Dänzer michel@daenzer.net --- Is this a regression from an older version of Mesa? If so, can you bisect?
https://bugs.freedesktop.org/show_bug.cgi?id=100995
--- Comment #6 from Paul Paul.Hancock.17041993@live.com --- Created attachment 131306 --> https://bugs.freedesktop.org/attachment.cgi?id=131306&action=edit post-hang xorg log, may not be relevant
post-hang xorg log, may not be relevant
Xorg doesn't appear to keep old log files, or the log may have been lost as a result of the hang, not exactly willing to trigger the hang again at this particular time...
https://bugs.freedesktop.org/show_bug.cgi?id=100995
--- Comment #7 from Paul Paul.Hancock.17041993@live.com --- (In reply to Michel Dänzer from comment #5)
Is this a regression from an older version of Mesa? If so, can you bisect?
Don't know, never had any working previous versions due to outdated kernel and drivers (kubuntu 16.10). This is as close as I've gotten > 3.0 to work on this machine by upgrading to 17.04 (4.10 kernel).
https://bugs.freedesktop.org/show_bug.cgi?id=100995
Timothy Arceri t_arceri@yahoo.com.au changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO
--- Comment #8 from Timothy Arceri t_arceri@yahoo.com.au --- Is this working for you now?
Unigine heaven is used regularly for benchmarking and there are no other reports of this type as far as I'm aware.
https://bugs.freedesktop.org/show_bug.cgi?id=100995
Paul Paul.Hancock.17041993@live.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Resolution|--- |FIXED
--- Comment #9 from Paul Paul.Hancock.17041993@live.com --- (In reply to Timothy Arceri from comment #8)
Is this working for you now?
I've since removed linux from the system and handed it down to a family member, so it's not possible for me to test anymore. However I would expect the bug would have been fixed by now, according to the current RadeonFeature support table.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org