I am running openSUSE 12.1 64 bit with KDE (regular repos) on a Lenovo X201i laptop. (Intel Corei5 and intel graphics).
Previously I had no problems but after the latest kernel update (3.1.10-1.13-desktop 64 ) the system goes to shutdown but blocks with running ventilator at “detaching dm-device”. I went through the kernel logs but I do not see anything that is different from the usual. Does anyone have some advice on how to track down what blocks the process to eventually be able to post a valuable bug report? Currently I could just report that shutdown problem, and for me this a bit too meager to be useful.
Thanks for all suggestions.
My main box was updated this AM, but I’ll not be shutting it down until tonight… so I’ll report on that tomorrow.
Did you try more than once?
All my other machines are Tumbleweed.
I can confirm that there is a major regression with this update: my laptop (HP Elitebook 8440p) won’t suspend (to ram or to disk). Both suspend modes were working perfectly fine with the previous kernel version. So far shutdown goes fine though (goes past “detaching DM device” and actually shuts down). Advice to all laptop (and possibly desktop) users: don’t install this update until this issue clears up.
BTW: Anybody knows how to cancel the update and revert to the previous kernel??
In reply to my own post: I reverted to kernel 3.1.10-1.9 (forced the version in software management).
Suspend to ram (sleep) and to disk (hibernate) are working again.
I have briefly looked at the kernel messages but didn’t see any difference between a working suspend with 3.1.10-1.9 and a failed one with 3.1.10-1.13.
I confirm that suspend to ram seems broken (system freeze and stays black, hardware reboot needed). If you have a wireless connection running and do the reboot it stops at “removing dm devices”. If you manually interrupt wlan it will go down (apparently) normally.
I had similar problem after last update, but on my desktop machine. Solution is to change default init program in grub config files. I added init=/bin/systemd in kernel line.
Hello dragonmj, and welcome to openSUSE. I appreciate you took the time to share your solution. I will try it out and then report back. Hope to see you here also in future. Cheers.
I had to go out - so shutdown my machine. It was fine.
You guys should report your issue
https://bugzilla.novell.com/index.cgi
OK checked that, but it has already been reported several times.
For example : #764864, #768560, #768553, #768483.
Hope it will be fixed soon.
I have the same problem with kernel-default 3.1.10-1.13.1 on my Dell Precision M6300 laptop running OpenSUSE 12.1. Sleep/suspend-to-RAM does not work. The computer freezes and I have to do a hard power off and reboot to get it back. I reverted to kernel-default 3.1.10-1.9.1 which works fine.
I added comments on bugzilla as well.
FYI,
Gordon
Same happened to me after updating to 3.1.10-1.13 kernel on my U460 Lenovo.
Bugzilla 764864, comment 32, https://bugzilla.novell.com/show_bug.cgi?id=764864#c32, states that this is fixed with a kernel update at Index of /repositories/Kernel:/openSUSE-12.1/standard
It seems to have fixed the kernel-desktop 3.1.10-1.13.1 suspend-to-RAM problem on my 32-bit HP desktop.
Howard
I have Thinkpad too. my situation is I can suspend to ram, but can’t resume.
caplock flashing light keeps blinking and screen turns black.
power button sometimes will boot me into emergency mode in the next manual boot.
I’ve opened a bug report:
On 07/23/2012 10:06 AM, MargueriteSu wrote:
>
> I have Thinkpad too. my situation is I can suspend to ram, but can’t
> resume.
>
> caplock flashing light keeps blinking and screen turns black.
Having the capslock flashing means a kernel panic. Those are really hard to
diagnose as the critical information only comes out on virtual terminal 10. I’m
not sure if you can switch to it during either suspend or resume.