<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [KVM][GVT-d] [BDW & SKL ]Ubuntu 16.04 guest boot up with kernel panic with the newest 4.9.0+ drm-intel kernel" href="https://bugs.freedesktop.org/show_bug.cgi?id=99025#c15">Comment # 15</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [KVM][GVT-d] [BDW & SKL ]Ubuntu 16.04 guest boot up with kernel panic with the newest 4.9.0+ drm-intel kernel" href="https://bugs.freedesktop.org/show_bug.cgi?id=99025">bug 99025</a> from <a class="email" href="mailto:tomeu@tomeuvizoso.net" title="Tomeu Vizoso <tomeu@tomeuvizoso.net>"> Tomeu Vizoso</a> <pre>(In reply to Terrence Xu from <a href="show_bug.cgi?id=99025#c14">comment #14</a>) > Created <a href="attachment.cgi?id=129481" name="attach_129481" title="dmesg-guest-slubdebug-20170203-drm-tip: 2017y-02m-02d-19h-49m-15s">attachment 129481</a> <a href="attachment.cgi?id=129481&action=edit" title="dmesg-guest-slubdebug-20170203-drm-tip: 2017y-02m-02d-19h-49m-15s">[details]</a> > dmesg-guest-slubdebug-20170203-drm-tip: 2017y-02m-02d-19h-49m-15s > > Here is the guest dmesg log for "Boot up guest with > slub_debug=FPZU,kmalloc-1024”. Sorry, but that log isn't really that useful. It's not complete, please attach the *whole* kernel output (first line should start with "Linux version"). Please make sure the cmd line args include drm.debug=0xe. Please use slub_debug without any further options, or if you have a good reason to think those should be enough, please explain. Also, I think it would be good if this bug contained more detailed instructions on how to reproduce the problem.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>