<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#c10">Comment # 10</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:txtoxtox285@googlemail.com" title="txtoxtox285@googlemail.com">txtoxtox285@googlemail.com</a> <pre>> I'm not quite following what you mean by booting vs. resuming kernel. I resume by echoing into /sys/power/resume from an initramfs. The kernel which is in charge before I called the “booting” kernel. When I echo into /sys/power/resume, my naive understanding is that the old kernel (the one which save a memory image to swap) is taking over control again (the “resuming” kernel). 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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>