![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.novell.com/show_bug.cgi?id=619754
http://bugzilla.novell.com/show_bug.cgi?id=619754#c29
Thomas Renninger
The funny thing is that happened with kernel 2.6.34-9-desktop which I had rebooted. Russ also tested a MS6 kernel which should have been affected, but could not reproduce this with when trying to by testing a MS6 kernel on a 11.3 RCx dist. Hmm, possibly the power has to be cut off completely (until all board LEDs switch off). Hmm, I can darkly remember a bug where you had to boot a non affected kernel (Linux or Windows) and then reboot again to get the issue fixed. But it could take hours to find it again... If we had a machine that can reproduce this every time, I could bisect it down... Ruediger, can I get fatou for some days? Can you remember whether you hit the reset button or did you completely power the machine off? (the next two days I am rather busy, though). Arian told me about reboot after suspend to ram, "might" be related. Please check dmesg for any ACPI warnings/errors everybody.
-- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.