Created attachment 137206 [details] /sys/class/drm/card1/error after first crash It seems to happen shortly after I start a VM in virtualbox (debian version 5.2.6-dfsg-2), so far two out of two times tried. uname -m: x86_64 (with amd64 userland) uname -r: 4.14.0-3-amd64 running debian unstable ThinkPad T460p with dual GPUs and 2560x1440 display panel
Created attachment 137207 [details] /sys/class/drm/card1/error after second crash
Created attachment 137208 [details] dmesg output, after both crashes
Created attachment 137209 [details] xrandr --verbose output
Three times out of three, so pretty consistent with starting the virtual box VM.
Downgrading the kernel to uname -r: 4.14.0-1-amd64 seems to have cured it
Nope, it didn't. Just took a bit longer to crash on 4.14.0-1-amd64
Created attachment 137210 [details] /sys/class/drm/card1/error on 4.14.0-1
Created attachment 137211 [details] dmesg on 4.14.0-1
virtualbox was not at fault. The actual culprit was xterm, when editing a long command line. Attaching screendump of xterm pre-crash. Starting to type "--exclude config" has invariably caused the crash before getting to the end of "--exclude", usually right before typing "l", but not always.
Created attachment 137214 [details] screen dump of xterm, pre-crash
said "--exclude config" is inserted where the cursor is in the screen dump, as the first --exclude option to rsync
Hi, which mesa version are you using?
(In reply to Elizabeth from comment #12) > Hi, which mesa version are you using? I was using (debian packaged) 17.3.5. I think it showed up (but not as bad) in 17.3.3, since I had occational crashes with that version. It seems to have gone away in 17.3.6.
*** This bug has been marked as a duplicate of bug 104411 ***
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.