<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [all bisected]system hang and BUG: unable to handle kernel NULL pointer dereference at 0000000000000084 when kill X" href="https://bugs.freedesktop.org/show_bug.cgi?id=89388#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [all bisected]system hang and BUG: unable to handle kernel NULL pointer dereference at 0000000000000084 when kill X" href="https://bugs.freedesktop.org/show_bug.cgi?id=89388">bug 89388</a> from <a class="email" href="mailto:michael@slashhome.org" title="Michael Leuchtenburg <michael@slashhome.org>"> Michael Leuchtenburg</a> <pre>I get a very similar crash to this on BDW hardware when modeswitching; changing to console results in an oops in the same function. gdb claims the IP was in the line changed in fd2d613, p->pri.bytes_per_pixel = crtc->primary->state->fb->bits_per_pixel / 8; so I suspect it's the same bug with a different trigger. If I revert the patch, I am able to change to console without a crash, though the mode in the console is not correct and causes the text to flicker in three locations.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>