<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - SIGBUS in EVERGREENUploadToScreen after hibernation (Linux 3.12.4-tuxonice)" href="https://bugs.freedesktop.org/show_bug.cgi?id=72716#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - SIGBUS in EVERGREENUploadToScreen after hibernation (Linux 3.12.4-tuxonice)" href="https://bugs.freedesktop.org/show_bug.cgi?id=72716">bug 72716</a> from <a class="email" href="mailto:agd5f@yahoo.com" title="Alex Deucher <agd5f@yahoo.com>"> Alex Deucher</a> <pre>(In reply to <a href="show_bug.cgi?id=72716#c10">comment #10</a>) > I suppose that’s not exactly what happens (is the kernel which just booted > really kicked out of existence or does it keep on running and take over the > memory image from the kernel which was suspended ?). But my point was that > when radeon.ko is loaded before the initramfs echoes into /sys/power/resume, > the lookup and the SIGBUS happen, whereas if it is not loaded, everything’s > fine. Does the booting kernel unload the radeon driver prior to switching to the resuming kernel? If not, the resuming kernel may take over before the radeon driver has finished loading in the boot kernel, or in the middle of some operation which leaves the GPU in a bad state when the resuming kernel takes over.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>