<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Loading i915 kernel module breaks NVMe PCI device on the new Coffee Lake box" href="https://bugs.freedesktop.org/show_bug.cgi?id=108546#c22">Comment # 22</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Loading i915 kernel module breaks NVMe PCI device on the new Coffee Lake box" href="https://bugs.freedesktop.org/show_bug.cgi?id=108546">bug 108546</a> from <a class="email" href="mailto:ville.syrjala@linux.intel.com" title="Ville Syrjala <ville.syrjala@linux.intel.com>"> Ville Syrjala</a> <pre>(In reply to Takashi Iwai from <a href="show_bug.cgi?id=108546#c10">comment #10</a>) > So I tried to hack around the function, just like > > --- a/drivers/gpu/drm/i915/intel_hdmi.c > +++ b/drivers/gpu/drm/i915/intel_hdmi.c > @@ -1921,7 +1921,7 @@ intel_hdmi_detect(struct drm_connector *connector, > bool force) > > intel_display_power_get(dev_priv, POWER_DOMAIN_GMBUS); > > - if (IS_ICELAKE(dev_priv) && > + if (//IS_ICELAKE(dev_priv) && > !intel_digital_port_connected(encoder)) > goto out; > > > ... and this seems working. No NVMe-related errors are seen after this. > > I don't mean that this is the right fix, but it indicates that poking the > HDMI detection for HDMI-3 screws up the NVMe on PCIe, apparently. Hmm. I wonder if the gmbus pins are wired up to some other use, but somehow they are still muxed such that gmbus can control them. That definitely sounds like a BIOS bug, or potentially a pinctrl driver bug.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>