Bug description: After X starts, this message apepars randomly in dmesg : [drm] HPD interrupt storm detected on connector HDMI-A-1 : switching from hotplug detection to polling When it happens, the display freezes (including sound) for a few seconds, sometimes more (to the point I'm forced to hard shutdown) System environment: -- chipset: GM45 -- system architecture: 64-bit -- xf86-video-intel: 1:2.99.917-1 -- xserver: 1.19.3 -- mesa: 2.1 Mesa 17.0.5 -- kernel: 4.9.102 -- Linux distribution: Hyperbola GNU/Linux -- Machine or mobo model: Thinkpad T400 R8KMZN2 -- Display connector: Internal (LVDS) 1440x900 Reproducing steps: Start X, after a few seconds (or minutes), the display freezes, when it happens, this message appears in dmesg : [drm] HPD interrupt storm detected on connector HDMI-A-1 : switching from hotplug detection to polling Additional info: - T400 is running Libreboot bios, the issue happens with late KMS and early KMS. ->>> Issue is not present with 4.16.12 kernel <<<-
Created attachment 139810 [details] Logs added (dmesg, lspci, mkinitpcio...) Logs added (dmesg, lspci, mkinitpcio...)
Created attachment 139811 [details] Log (dmesg) from remote console SSH after display is fully freezed Log (dmesg) from remote console SSH after display is fully freezed
If you need more info or logs, let me know, it is the first time I report a bug.
Can you try with latest drm-tip: https://cgit.freedesktop.org/drm-tip and send dmesg with drm.debug=0x1e log_buf_len=4M?. drm-tip currently on Linux version 4.17.0-rc6. Do not cut (no greps etc) logs but keep them intact.
reference to build kernel: https://01.org/linuxgraphics/documentation/build-guide-0 (drm-tip part only)
Created attachment 139818 [details] dmesg log (4.17 drm-tip : drm.debug=0x1e log_buf_len=4M) dmesg log (4.17 drm-tip : drm.debug=0x1e log_buf_len=4M)
(In reply to Jani Saarinen from comment #4) > Can you try with latest drm-tip: https://cgit.freedesktop.org/drm-tip and > send dmesg with drm.debug=0x1e log_buf_len=4M?. > > drm-tip currently on Linux version 4.17.0-rc6. > > Do not cut (no greps etc) logs but keep them intact. Hello, Sorry, it took me a while to clone (slow network) & compile. I added the dmesg log with 4.17 drm-tip
The issue is not present with drm-tip as well. No freeze.
based on this resolving as works in upstream. Hopefully these got in to 4.18 kernel.
The issue is that the distro I use only package 4.9.x kernel. (LTS) I don't understand much how drm fixes are handled for LTS kernels. Will 4.9.x LTS kernel receive a patch for i915 drm ? Sorry if it sounds dumb, I don't have much experience with that. I can certainly compile a kernel from 4.16 branch until then though. Thanks for your help.
Jani, can you comment how this goes?
(In reply to aether from comment #10) > The issue is that the distro I use only package 4.9.x kernel. (LTS) > I don't understand much how drm fixes are handled for LTS kernels. Will > 4.9.x LTS kernel receive a patch for i915 drm ? > Sorry if it sounds dumb, I don't have much experience with that. I can > certainly compile a kernel from 4.16 branch until then though. > Thanks for your help. This is the upstream bugzilla, the issue is fixed upstream, case closed. For backports, we'd need to know *which* commit fixed the issue. Here we have no clue. If you come up with a reverse bisect indicating which commit fixed the issue upstream, and if the fix is small enough, we can request the stable kernel maintainers to backport the fix. Otherwise, you can file a bug against your distro.
(In reply to Jani Nikula from comment #12) > (In reply to aether from comment #10) > > The issue is that the distro I use only package 4.9.x kernel. (LTS) > > I don't understand much how drm fixes are handled for LTS kernels. Will > > 4.9.x LTS kernel receive a patch for i915 drm ? > > Sorry if it sounds dumb, I don't have much experience with that. I can > > certainly compile a kernel from 4.16 branch until then though. > > Thanks for your help. > > This is the upstream bugzilla, the issue is fixed upstream, case closed. > > For backports, we'd need to know *which* commit fixed the issue. Here we > have no clue. If you come up with a reverse bisect indicating which commit > fixed the issue upstream, and if the fix is small enough, we can request the > stable kernel maintainers to backport the fix. > > Otherwise, you can file a bug against your distro. Alright, thanks for the complementary information.
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.