<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [BDW][EXT] igt@kms_flip@vblank-vs-dpms-suspend-interruptible hard LOCKUP on cpu 3" href="https://bugs.freedesktop.org/show_bug.cgi?id=100419#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [BDW][EXT] igt@kms_flip@vblank-vs-dpms-suspend-interruptible hard LOCKUP on cpu 3" href="https://bugs.freedesktop.org/show_bug.cgi?id=100419">bug 100419</a> from <a class="email" href="mailto:jani.nikula@intel.com" title="Jani Nikula <jani.nikula@intel.com>"> Jani Nikula</a> <pre>(In reply to Marta Löfstedt from <a href="show_bug.cgi?id=100419#c7">comment #7</a>) > FYI, if I blacklist the snd_hda_core, snd_hda_codec and snd_hda_intel I of > course doesn't hit the issue, we could consider doing this for the CI system > in order to stop being blocked by this issue. (In reply to Daniel Vetter from <a href="show_bug.cgi?id=100419#c9">comment #9</a>) > Just fyi, if audio can't/won't fix this I guess we need to consider removing > the sound trees from drm-tip again. I'm not against including them in our > trees (it makes a lot of sense), but there's a lot of trouble coming from > the audio side. Audio needs to keep up their side of this bargain here. IMO blacklisting audio in our CI or excluding the audio tree from drm-tip are self deception, and postponing the inevitable breakage until audio and our trees are merged to Linus' tree. We *never* want to be in a situation where we see the issues at -rc1 and have limited time and options to resolve issues, under pressure. Seeing the issues *now* in CI is a fundamentally good thing, and if there are problems with that, we need to seek other solutions than dodging them. One thing to do is to involve the audio folks more in graphics CI and graphics bugs. There is value for *them* in what we do here, and they should be interested and contribute back. More collaboration benefits both of us. And there are plenty of Intel folks involved with audio, should not be rocket science to figure this out. Another, but much bigger, thing is to start gating drm-tip branch updates. Instead of pulling in everything at every drm-tip build, figure out a way to ask for CI runs with good baseline + updated audio tree with specified sha1. If CI says good, update, otherwise escalate with audio.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>