Created attachment 144411 [details] error dump
The ring buffers were trashed as if some stray writes went to address 0+.
Created attachment 144412 [details] journalctl priority 7 (debug)
i have the i915 chipset: Graphics: Device-1: Intel 3rd Gen Core processor Graphics vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0166 Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa alternate: intel compositor: kwin_x11 resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 4.2 Mesa 19.0.4 compat-v: 3.0 direct render: Yes
(In reply to jshand2013 from comment #3) i have the i915 driver: [CODE] Graphics: Device-1: Intel 3rd Gen Core processor Graphics vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0166 Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa alternate: intel compositor: kwin_x11 resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 4.2 Mesa >19.0.4 compat-v: 3.0 direct render: Yes [/CODE]
Please test with commit c84c9029d782a3a0d2a7f0522ecb907314d43e2c Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Fri Apr 19 12:17:47 2019 +0100 drm/i915/ringbuffer: EMIT_INVALIDATE *before* switch context heading to v5.1 via stable in the next few weeks. *** This bug has been marked as a duplicate of bug 111014 ***
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.