System freeze after plugging in dvi-monitor

sulking_sufferer · 2024-03-05 09:44:39

Hi all,

my old laptop freezes whenever I plug in a dvi-monitor (vga is working fine). Same issue if I boot with the cable plugged in. I am pretty sure this is a kernel issue. I ran into it before and changed to libre-lts kernel. This solved the issue for some months. But since it got updated I cannot get around this error.

using 6.6.14-gnu-1-lts

The important lines (I guess) from journalctl:

BUG: kernel NULL pointer dereference, address: 000000000000000a
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 0 P4D 0
Oops: 0000 [#1] PREEMPT SMP PTI
CPU: 0 PID: 9 Comm: kworker/0:1 Tainted: G          I        6.6.14-gnu-1-lts #1 0fb698ac033195ed84fa05304a314090a7c8>
Hardware name: LENOVO 7434AT7/7434AT7, BIOS CBET4000 1c84243 09/07/2016
Workqueue: i915-unordered i915_hotplug_work_func [i915]
RIP: 0010:intel_bios_encoder_supports_dp_dual_mode+0x9/0x60 [i915]
Code: 01 00 00 00 5b 5d 41 5c 41 5d c3 cc cc cc cc 66 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 66 0f 1f 00 >
RSP: 0018:ffffbb7b0005fca8 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff96e0048ab800 RCX: 0000000000000001
RDX: fffffffffffffffa RSI: ffff96e0008270c0 RDI: 0000000000000000
RBP: ffff96e0048a5000 R08: 0000000000000000 R09: ffffbb7b0005fc78
R10: 0000000000008c00 R11: 0000000000000400 R12: ffff96e004c78000
R13: ffff96e004c78000 R14: ffff96e0048a5000 R15: ffff96e0043b5700
FS:  0000000000000000(0000) GS:ffff96e168000000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000000000a CR3: 00000001f6e20000 CR4: 00000000000406f0
Call Trace:
 <TASK>
 ? __die+0x23/0x70
 ? page_fault_oops+0x171/0x4e0
 ? exc_page_fault+0x7f/0x180
 ? asm_exc_page_fault+0x26/0x30
 ? intel_bios_encoder_supports_dp_dual_mode+0x9/0x60 [i915 103bac1caaa15b57b7cfa94580ea923ea4ab5856]
 intel_hdmi_set_edid+0x282/0x2c0 [i915 103bac1caaa15b57b7cfa94580ea923ea4ab5856]
 intel_hdmi_detect+0x105/0x1e0 [i915 103bac1caaa15b57b7cfa94580ea923ea4ab5856]
 drm_helper_probe_detect_ctx+0x9d/0x110
 intel_encoder_hotplug+0x47/0x100 [i915 103bac1caaa15b57b7cfa94580ea923ea4ab5856]
 intel_hdmi_hotplug+0x12/0x30 [i915 103bac1caaa15b57b7cfa94580ea923ea4ab5856]
 i915_hotplug_work_func+0x280/0x390 [i915 103bac1caaa15b57b7cfa94580ea923ea4ab5856]
 process_one_work+0x174/0x340
 worker_thread+0x27b/0x3a0
 ? __pfx_worker_thread+0x10/0x10
 kthread+0xe8/0x120
 ? __pfx_kthread+0x10/0x10
 ret_from_fork+0x34/0x50
 ? __pfx_kthread+0x10/0x10
 ret_from_fork_asm+0x1b/0x30
 </TASK>
Modules linked in: 8021q garp mrp stp llc ccm joydev mousedev ath9k ath9k_common ath9k_hw kvm_intel ath snd_hda_codec>
CR2: 000000000000000a
---[ end trace 0000000000000000 ]---
RIP: 0010:intel_bios_encoder_supports_dp_dual_mode+0x9/0x60 [i915]
Code: 01 00 00 00 5b 5d 41 5c 41 5d c3 cc cc cc cc 66 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 66 0f 1f 00 >
RSP: 0018:ffffbb7b0005fca8 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff96e0048ab800 RCX: 0000000000000001
RDX: fffffffffffffffa RSI: ffff96e0008270c0 RDI: 0000000000000000
RBP: ffff96e0048a5000 R08: 0000000000000000 R09: ffffbb7b0005fc78
R10: 0000000000008c00 R11: 0000000000000400 R12: ffff96e004c78000
R13: ffff96e004c78000 R14: ffff96e0048a5000 R15: ffff96e0043b5700
FS:  0000000000000000(0000) GS:ffff96e168000000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000000000a CR3: 00000001f6e20000 CR4: 00000000000406f0
note: kworker/0:1[9] exited with irqs disabled

I tried this: https://bbs.archlinux.org/viewtopic.php?id=257710 without success.

Any other idea where to start?

seth · 2024-03-05 16:35:31

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Does the output work as expected and w/o crash when booting w/ it attached?
You could try to inject an EDID, https://wiki.archlinux.org/title/Kernel … s_and_EDID

Do you use a HDMI/DVI adapter?

sulking_sufferer · 2024-03-05 18:23:23

Well, journalctl returns some sensible information I cannot upload. Here is the output of dmesg https://0x0.st/H7fX.txt. This is before I plug in the cable. When I do, the errors from above come in.

I use no adapter but an old docking station with dvi-out. Not sure what is inside. Until yesterday (when it was still working) xrandr listed the dvi-connected monitor as HDMI2.

When I attach the monitor before booting, the system freezes before I get to the login screen.

As far as I understand the EDID-injection aims at fixing issues with an individual monitors. I don't think the problem lies there. I have the same issue with different monitors. All work when connect via VGA, none works when connected via DVI.

seth · 2024-03-05 19:07:03

The journal certainly has a lot of sensible but isn't supposed to contain any sensitive information.
(This made be guess your nationality before seeing it in the dmesg, btw )

The point of the edid injection is to avoid that codepath and maybe sidestep the issue, however I'm now more curious about

Until yesterday (when it was still working)

and

changed to libre-lts kernel. This solved the issue for some months. But since it got updated

What kernel were you running before?

There's no xhci in the dmesg, so this is likely some proprietary dock connection?
Have you btw. tried whether this is fixed in the main (6.7) kernel (I could imagine that you've kept the 6.1 kernels because it broke on 6.6 and now ran into that?)

If you inspect your older journals, where there other i915/drm/hdmi/dvi related warnings (that the system could just recover from)?

sulking_sufferer · 2024-03-05 21:16:58

Jep, thanks for the English coaching. netctl reports the names of my wifi-connections to journalctl and that information I would rather keep for myself. BTW does dmesg really disclose my nationality?

Since you are curious I give you a longer genesis story of my embarrassing situation: I didn't update my system for 2 or 3 months due to laziness. Yesterday I had to and ran into horrible pacman issues. pacman recovered only after I deleted its cache. Now this turns out be quite unfortunate, since I lost my old kernels. And to make things worse: I don't have any journal entries before yesterday. But as far as I remember there have never been other warnings then I am seeing now.

I was using linux-libre-lts 5.8 and the mini dock for the thinkpad t400 just did its job. I have two of those, both of which were working fine and both of which make problems now. I would be rather surprised if this was related to a proprietary issue. I am afraid I am haunted by something stupid I did in the past which I cannot remember.

linux-libre 6.7.4 doesn't work either. For stupid reasons, I don't feel ready to try the mainline kernel.

seth · 2024-03-05 21:41:54

The regdomain shows up. Also the MAC that your AP yells into the world. I can tell you it's a cisco device and google probably has it's coordinates in some database.
The SSID is about the least sensitive data in that mix, only maybe embarrassing (but nobody cares about that)

Now this turns out be quite unfortunate, since I lost my old kernels.

linux-libre isn't in the repos anyway - you'd have built that from the AUR. linux-libre-lts isn't even there, are you just trying to conceil that this is actually parabola?

[    4.841751] systemd[1]: systemd 253-1.parabola3-parabola running in system mode (+PAM +AUDIT -SELINUX -APPARMOR -IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT -QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +XKBCOMMON +UTMP -SYSVINIT default-hierarchy=unified)

Cause you failed with that…

I would be rather surprised if this was related to a proprietary issue.

Me too, I just wanted to clarify how the output is actually ultimately connected to the system.

linux-libre 6.7.4 doesn't work either.

My best advise is to at least try the actual, regular, evilish unfree kernel. And linux-firmware.
Basically, test whether you can boot the arch install iso w/o this particular problem.

sulking_sufferer · 2024-03-05 21:51:11

Thanks for your additional insights. I will turn evil and report if it helped.

Arch Linux

#1 2024-03-05 09:44:39

System freeze after plugging in dvi-monitor

#2 2024-03-05 16:35:31

Re: System freeze after plugging in dvi-monitor

#3 2024-03-05 18:23:23

Re: System freeze after plugging in dvi-monitor

#4 2024-03-05 19:07:03

Re: System freeze after plugging in dvi-monitor

#5 2024-03-05 21:16:58

Re: System freeze after plugging in dvi-monitor

#6 2024-03-05 21:41:54

Re: System freeze after plugging in dvi-monitor

#7 2024-03-05 21:51:11

Re: System freeze after plugging in dvi-monitor

Board footer