Created attachment 135344 [details]
gpu crash dump
dmesg requested me to make a bug report:
[ 5185.440496] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 5185.440498] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 5185.440499] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 5185.440500] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 5185.440502] [drm] GPU crash dump saved to /sys/class/drm/card0/error
This is my first time submitting a bug here, so if information is missing please ask for it. Additional information: its an acer aspire 5742g laptop with intel core i5-450M processor en nvidia geforce gt 540M running arch linux.
this command: lspci -k | grep -A 2 -E "(VGA|3D)", produces the following output:
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)
Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics Controller
Kernel driver in use: i915
01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 540M] (rev a1)
Subsystem: Acer Incorporated [ALI] GF108M [GeForce GT 540M]
Kernel modules: nouveau, nvidia_drm, nvidia
Maybe incidental, but the decoder warned about:
0x0028d01c: 0x60003f01: URB_FENCE: cs vfe sf clip gs vs
0x0028d020: 0x04d80014: vs fence: 20, clip_fence: 77, gs_fence: 512
0x0028d024: 0x12230000: sf fence: 0, vfe_fence: 192, cs_fence: 290
clip fence < gs fence!
sf fence < clip fence!
Could be, no idea. I was just surprised my computer froze, then `dmesg` told me to report a bug, so i did.
i don't understand that decoder warning, i just assume my hardware is starting to wear (given its a >5 year old laptop with intense use)
Hello Stetim94, Is this reproducible? Can you share your Mesa version? Thanks.
-- 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/1648.