<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [NV4C] GPU lock-up after booting to desktop in Fedora 20 & 21 (Nvidia Geforce 6100 IGP)" href="https://bugs.freedesktop.org/show_bug.cgi?id=87361#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [NV4C] GPU lock-up after booting to desktop in Fedora 20 & 21 (Nvidia Geforce 6100 IGP)" href="https://bugs.freedesktop.org/show_bug.cgi?id=87361">bug 87361</a> from <a class="email" href="mailto:jajadekroon@gmail.com" title="Jan Jasper de Kroon <jajadekroon@gmail.com>"> Jan Jasper de Kroon</a> <pre>A quick search around the freedesktop.org bugzilla with search criteria NV4C revealed some similar bugs like: <a class="bz_bug_link bz_status_NEW " title="NEW - [regression][NV4c] System hang while loading gdm on 3.7 kernel (works on 3.6)" href="show_bug.cgi?id=61321">https://bugs.freedesktop.org/show_bug.cgi?id=61321</a> When I did a quick search on nv4c_mc_oclass I found on the website: <a href="http://lxr.free-electrons.com/ident?v=3.14;i=nv4c_mc_oclass">http://lxr.free-electrons.com/ident?v=3.14;i=nv4c_mc_oclass</a> that this nv4c_mc_oclass is first mentioned in kernel 3.14. But if you look at the bug report I linked in this comment I found out that this person also experienced the same problem with the transition of kernel 3.6 to 3.7. While browsing the kernel source from 3.7 I found out that the value for device->oclass[NVDEV_SUBDEV_MC still was nv44_mc_oclass. When you enter this search value 'nv44_mc_oclass' in the free-electrons.com website and you look at kernel version 3.6 and 3.7 you'll find the nv44_mc_oclass was first introduced in kernel version 3.7 (where the above mentioned bug report applies to). So indeed I think you're thought to disable the MSI in the kernel source will be the correct decision. But of course that's just my humble opinion. As said earlier I will report this evening about the change from nv4c_mc_oclass to nv44_mc_oclass, but given the above bug report I suppose this will eventually lead to the same result. Hope I have given you a lot of usefull information about this problem.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>