<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - intel driver on Dell Latitude 5285: Segmentation fault after resume" href="https://bugs.freedesktop.org/show_bug.cgi?id=101986#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - intel driver on Dell Latitude 5285: Segmentation fault after resume" href="https://bugs.freedesktop.org/show_bug.cgi?id=101986">bug 101986</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>It's going to be loss of a DP after resume, I guess? What else will make the previously working mode now invalid. The crash is going to be some mistake in error handling, but we're not going to get much without debug symbols. Is there any chance you can compile with --enable-debug=full? That should have the added benefit of capturing why the kernel rejected the mode as well. (In reply to nico-freedesktop.org from <a href="show_bug.cgi?id=101986#c4">comment #4</a>) > Plus the actual driver (why do we still have xf86 in the name? ...) History + inertia.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>