Created attachment 137380 [details] GPU crash dump and full dmesg Crash while running the chromium browser. Might be a duplicate. I cannot reproduce, just thought the crash log might be of interest. I've attached the GPU crash dump and full dmesg, but I don't have anything else because my machine locked up entirely a few minutes afterward. uname -m : x86_64 uname -r : 4.9.0-5-amd64 (Yes, I know I should update my kernel to the latest Debian backport.) lsb_release -d : Description: Debian GNU/Linux 9.3 (stretch) Partial output of "sudo dmidecode -t 2": # dmidecode 3.0 Getting SMBIOS data from sysfs. SMBIOS 2.6 present. Handle 0x0011, DMI type 2, 15 bytes Base Board Information Manufacturer: LENOVO Product Name: 4177CTO Version: Not Available Serial Number: <snip> Asset Tag: Not Available Features: Board is a hosting board Board is replaceable Location In Chassis: Not Available Chassis Handle: 0x0000 Type: Motherboard Contained Object Handles: 0 Version information from "apt-cache policy libdrm-intel1": libdrm-intel1: Installed: 2.4.89-1~bpo9+1 Candidate: 2.4.89-1~bpo9+1 Version table: *** 2.4.89-1~bpo9+1 100 100 http://ftp.us.debian.org/debian stretch-backports/main amd64 Packages 100 /var/lib/dpkg/status 2.4.74-1 500 500 http://ftp.us.debian.org/debian stretch/main amd64 Packages
Which mesa version do you have?
$ glxinfo | grep 'core profile version string' OpenGL core profile version string: 3.3 (Core Profile) Mesa 13.0.6 Is that sufficient, or should I provide glxinfo in entirety?
(In reply to Nathaniel Morck Beaver from comment #2) > $ glxinfo | grep 'core profile version string' > OpenGL core profile version string: 3.3 (Core Profile) Mesa 13.0.6 > > Is that sufficient, or should I provide glxinfo in entirety? That will be enough, thank you. Mesa 13 is quite old, if you're able to replicate with a recent release, mesa 17.3 or mesa 18, please attach a new crash dump. Also kernel 4.13 and up can provide more relevant information about the crash.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1688.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.