Description of problem: The laptop suddenly locks up and CPUs fan ramp up to full speed. Graphics are still displayed, and audio keeps playing, but mouse cursor won't move, no keyboard input and display is frozen. After power cycling I find this in the journal: Mar 13 15:39:10 t460 kernel: [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling Mar 13 15:41:12 t460 kernel: BUG: unable to handle kernel NULL pointer dereference at 00000000000000e4 Mar 13 15:41:12 t460 kernel: IP: intel_hpd_irq_storm_reenable_work+0x82/0x160 [i915] Mar 13 15:41:12 t460 kernel: PGD 0 P4D 0 Mar 13 15:41:12 t460 kernel: Oops: 0000 [#1] SMP PTI Mar 13 15:41:12 t460 kernel: Modules linked in: vfat fat rfcomm fuse xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun devlink nfs lockd grace fscache ccm nf_conntrack_net Mar 13 15:41:12 t460 kernel: snd_hda_codec snd_hda_core btusb uvcvideo btrtl btbcm snd_hwdep iwlwifi videobuf2_vmalloc videobuf2_memops irqbypass videobuf2_v4l2 intel_cstate Mar 13 15:41:12 t460 kernel: CPU: 4 PID: 3952 Comm: kworker/4:2 Not tainted 4.14.14-300.fc27.x86_64 #1 Mar 13 15:41:12 t460 kernel: Hardware name: LENOVO 20FXS0BB0Q/20FXS0BB0Q, BIOS R07ET63W (2.03 ) 03/15/2016 Mar 13 15:41:12 t460 kernel: Workqueue: events intel_hpd_irq_storm_reenable_work [i915] Mar 13 15:41:12 t460 kernel: task: ffff947e56d28000 task.stack: ffffa6750d414000 Mar 13 15:41:12 t460 kernel: RIP: 0010:intel_hpd_irq_storm_reenable_work+0x82/0x160 [i915] Mar 13 15:41:12 t460 kernel: RSP: 0018:ffffa6750d417e50 EFLAGS: 00010086 Mar 13 15:41:12 t460 kernel: RAX: ffff947f776db000 RBX: 0000000000000005 RCX: 0000000000000055 Mar 13 15:41:12 t460 kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffffffffc0282314 Mar 13 15:41:12 t460 kernel: RBP: ffff947f768e2ad4 R08: 0000000000000005 R09: 0000000000000003 Mar 13 15:41:12 t460 kernel: R10: ffff947f768e02f8 R11: ffff947ef7a81fc0 R12: ffff947f768e2b10 Mar 13 15:41:12 t460 kernel: R13: ffff947f768e0000 R14: ffffffffc049eaa0 R15: ffff947f768e2b18 Mar 13 15:41:12 t460 kernel: FS: 0000000000000000(0000) GS:ffff947fa1500000(0000) knlGS:0000000000000000 Mar 13 15:41:12 t460 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 13 15:41:12 t460 kernel: CR2: 00000000000000e4 CR3: 000000015f20a006 CR4: 00000000003606e0 Mar 13 15:41:12 t460 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Mar 13 15:41:12 t460 kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Mar 13 15:41:12 t460 kernel: Call Trace: Mar 13 15:41:12 t460 kernel: process_one_work+0x184/0x3a0 Mar 13 15:41:12 t460 kernel: worker_thread+0x2e/0x380 Mar 13 15:41:12 t460 kernel: ? process_one_work+0x3a0/0x3a0 Mar 13 15:41:12 t460 kernel: kthread+0x11a/0x130 Mar 13 15:41:12 t460 kernel: ? kthread_park+0x60/0x60 Mar 13 15:41:12 t460 kernel: ret_from_fork+0x32/0x40 Mar 13 15:41:12 t460 kernel: Code: 83 c5 10 83 fb 09 74 50 83 7d 00 01 75 ee 48 8d 74 24 08 c7 45 00 00 00 00 00 4c 89 ef e8 f7 a8 e4 ff eb 0f 48 8b 90 00 04 00 00 <39> 9a e4 Mar 13 15:41:12 t460 kernel: RIP: intel_hpd_irq_storm_reenable_work+0x82/0x160 [i915] RSP: ffffa6750d417e50 Mar 13 15:41:12 t460 kernel: CR2: 00000000000000e4 Mar 13 15:41:12 t460 kernel: ---[ end trace 747864eed6b5c8c7 ]--- Version-Release number of selected component (if applicable): 4.14.14-300.fc27.x86_64 Also seen with 4.14.18-300.fc27.x86_64 How reproducible: Completely random. Not seen in months of using this laptop, then suddenly hits 4 times today. Possibly related to use of a docking station today. Steps to Reproduce: 1. Unable to reproduce reliably at all
The 4.14.14 is old, please update to a newer kernel version
Unfortunately I'm unable to reproduce the problem further, whether with the 4.14.14 kernel or any newer one. I think perhaps the laptop was not docked quite correctly, and that triggered the reported interrupt storm and/or some hard to reach codepath. So I won't be able to provide more than the stack trace shown above.
If you can't reproduce the problem, I think it makes sense to close the bug. Feel free to reopen if you see the problem again.
Looks like I'm hitting this a few times a day with latest greatest Fedora. I just went from 27 to 28 to see if this would be fixed. I'm using my Notebook on the docking station with a 3 display setup. This is what I found in my logs : May 18 12:05:35 juri.ber.redhat.com kernel: [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling May 18 12:07:37 juri.ber.redhat.com kernel: BUG: unable to handle kernel NULL pointer dereference at 00000000000000ec May 18 12:07:37 juri.ber.redhat.com kernel: IP: intel_hpd_irq_storm_reenable_work+0x82/0x160 [i915] May 18 12:07:37 juri.ber.redhat.com kernel: PGD 0 P4D 0 May 18 12:07:37 juri.ber.redhat.com kernel: Oops: 0000 [#1] SMP PTI May 18 12:07:37 juri.ber.redhat.com kernel: Modules linked in: rfcomm fuse ccm xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun devlink nf_conntrack_netbios_ns nf_conntrack_broadcast x> May 18 12:07:37 juri.ber.redhat.com kernel: mei_wdt iTCO_vendor_support iwlmvm snd_hda_codec_realtek wmi_bmof snd_soc_core snd_hda_codec_generic kvm mac80211 snd_compress snd_pcm_dmaengine> May 18 12:07:37 juri.ber.redhat.com kernel: pps_core video target_core_mod May 18 12:07:37 juri.ber.redhat.com kernel: CPU: 1 PID: 1074 Comm: kworker/1:2 Not tainted 4.16.8-300.fc28.x86_64 #1 May 18 12:07:37 juri.ber.redhat.com kernel: Hardware name: LENOVO 20FAS2BN0F/20FAS2BN0F, BIOS N1CET40W (1.08 ) 03/09/2016 May 18 12:07:37 juri.ber.redhat.com kernel: Workqueue: events intel_hpd_irq_storm_reenable_work [i915] May 18 12:07:37 juri.ber.redhat.com kernel: RIP: 0010:intel_hpd_irq_storm_reenable_work+0x82/0x160 [i915] May 18 12:07:37 juri.ber.redhat.com kernel: RSP: 0018:ffffaf6a4b703e50 EFLAGS: 00010086 May 18 12:07:37 juri.ber.redhat.com kernel: RAX: ffff93874a1f1800 RBX: 0000000000000005 RCX: 0000000000000003 May 18 12:07:37 juri.ber.redhat.com kernel: RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000002 May 18 12:07:37 juri.ber.redhat.com kernel: RBP: ffff93880364acac R08: ffff93874a1f1838 R09: 0000000000000000 May 18 12:07:37 juri.ber.redhat.com kernel: R10: 0000000000000000 R11: 00000acbfaa8b800 R12: ffff93880364ace8 May 18 12:07:37 juri.ber.redhat.com kernel: R13: ffff938803648000 R14: ffffffffc05905a8 R15: ffff93880364acf0 May 18 12:07:37 juri.ber.redhat.com kernel: FS: 0000000000000000(0000) GS:ffff938821480000(0000) knlGS:0000000000000000 May 18 12:07:37 juri.ber.redhat.com kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 18 12:07:37 juri.ber.redhat.com kernel: CR2: 00000000000000ec CR3: 000000049e20a006 CR4: 00000000003606e0 May 18 12:07:37 juri.ber.redhat.com kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 May 18 12:07:37 juri.ber.redhat.com kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 May 18 12:07:37 juri.ber.redhat.com kernel: Call Trace: May 18 12:07:37 juri.ber.redhat.com kernel: process_one_work+0x187/0x340 May 18 12:07:37 juri.ber.redhat.com kernel: worker_thread+0x2e/0x380 May 18 12:07:37 juri.ber.redhat.com kernel: ? pwq_unbound_release_workfn+0xd0/0xd0 May 18 12:07:37 juri.ber.redhat.com kernel: kthread+0x112/0x130 May 18 12:07:37 juri.ber.redhat.com kernel: ? kthread_create_worker_on_cpu+0x70/0x70 May 18 12:07:37 juri.ber.redhat.com kernel: ? do_syscall_64+0x74/0x180 May 18 12:07:37 juri.ber.redhat.com kernel: ? SyS_exit_group+0x10/0x10 May 18 12:07:37 juri.ber.redhat.com kernel: ret_from_fork+0x35/0x40 May 18 12:07:37 juri.ber.redhat.com kernel: Code: 83 c5 10 83 fb 09 74 50 83 7d 00 01 75 ee c7 45 00 00 00 00 00 48 8d 74 24 08 4c 89 ef e8 17 51 e8 ff eb 0f 48 8b 90 18 04 00 00 <39> 9a ec> May 18 12:07:37 juri.ber.redhat.com kernel: RIP: intel_hpd_irq_storm_reenable_work+0x82/0x160 [i915] RSP: ffffaf6a4b703e50 May 18 12:07:37 juri.ber.redhat.com kernel: CR2: 00000000000000ec May 18 12:07:37 juri.ber.redhat.com kernel: ---[ end trace 3227364a23e4c51a ]---
Created attachment 1447270 [details] Kernel log of hang Similar symptoms just happened for me (4.16.13), log attached. If I work out how to reproduce it, is there any particular information which would be helpful?
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.