Comment # 6 on bug 1183872 from
Created attachment 847713 [details]
dmesg with call trace referencing i915 after connecting a screen by HDMI

>FWIW I think this is a laptop-only issue.
Or a GeminiLake-only issue. But yes it doesn't seem to affect every device
using i915.

Is the external display connected only to the laptop's HDMI?
Yes, that's the only external screen connected to the only HDMI port on that
laptop. There's also the internal screen of course.

>or is some other cable simultaneously connected to some other device's output even though not powered up?
No

>Please give the gitlab issues URL
https://gitlab.freedesktop.org/drm/intel/-/issues/3285

>And, any attemp to kdump wasn't successful?
Nope, I didn't had any luck with kdump, ended up disabling it since I never got
any logs but still consumed the 210MB of memory. On the bright side just a few
hours ago I finally got a dmesg log with a call trace that reference i915 in
it.
It can be found on the link but I'll attach it here for completeness.


You are receiving this mail because: