<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [NV98] hangs in nvbios_init on probe (worked in 3.2)" href="https://bugs.freedesktop.org/show_bug.cgi?id=72943#c15">Comment # 15</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [NV98] hangs in nvbios_init on probe (worked in 3.2)" href="https://bugs.freedesktop.org/show_bug.cgi?id=72943">bug 72943</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>Well, I downloaded <a href="https://www.dropbox.com/sh/e77p700zr8g1v4z/kb_av1ZSS6/127.0.0.1-2014.01.07-20%3A43%3A35">https://www.dropbox.com/sh/e77p700zr8g1v4z/kb_av1ZSS6/127.0.0.1-2014.01.07-20%3A43%3A35</a> Which includes kernel-debuginfo-common-x86_64-3.13.0-0.rc6.git0.1.fc20.x86_64.rpm Which contains the source. I can only assume that this is the source that you built from. And the drivers/gpu/drm/nouveau/core/subdev/bios/init.c in there does not appear to have the patch applied to init_jump. So I'd like to ask again... can you check that the kernel you're booting is the kernel that has the patch applied to it? Am I misunderstanding the situation? You could prove it to yourself by modifying some common print, for example, that you would be able to identify from kernel messages. Or you could just build the kernel directly without fancy tools that obscure these things. (I did try loading the nouveau.ko.debug in gdb, but I think it _only_ contains the debug symbols, since the init_jump function was full of add %al,(%rax) instructions which I think is just opcode 0.)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>