I installed Opensuse in a Acer Aspire V5-473 and I can’t shutdown properly the system. When I press the shutdown button in KDE (or doing # shutdown -h now) all the system freezes and I can’t access any tty or reboot with the REISUB trick. The only solution is doing a hard shutdown (pressing the ac/power button for a couple of seconds, not the best idea IMHO)
I read this thread about a similar problem but it seems that affects only 32 bits machines.
My situation:
Fully updated with ‘zypper up’
$ uname -a
Linux linux-zo89.site 3.11.10-7-desktop #1 SMP PREEMPT Mon Feb 3 09:41:24 UTC 2014 (750023e) x86_64 x86_64 x86_64 GNU/Linux
Hm. A few thoughts:
Try to disable plymouth (by adding “plymouth.enable=0” to the boot options). You should see the messages during shutdown then. Maybe there’s something obvious there?
Or maybe /var/log/messages shows something?
Do you have any nfs shares mounted?
Maybe the network gets shut down before the shares are unmounted, causing a hang.
Do you have acpid installed? Try to remove it, I have heard this could cause hangs on shutdown. But it should not be installed by default on 13.1 anyway.
Try to disable plymouth (by adding “plymouth.enable=0” to the boot options). You should see the messages during shutdown then. Maybe there’s something obvious there?
Or maybe /var/log/messages shows something?
The only message that I got was ‘‘Reboot: power down’’. I post my message log file from my last shutdown: /var/log/messages
Do you have any nfs shares mounted?
Maybe the network gets shut down before the shares are unmounted, causing a hang.
No I don’t have any. It’s a single personal machine.
Do you have acpid installed? Try to remove it, I have heard this could cause hangs on shutdown. But it should not be installed by default on 13.1 anyway.
I installed, but read this in another place and remove it immediately.
> The only message that I got was ‘‘Reboot: power down’’. I post my
> message log file from my last shutdown: '/var/log/messages
> ’ (http://pastebin.com/Ek1UKAbV)
Nothing there. A normal shutdown, then it starts again.
> 2014-02-22T10:54:26.712581+01:00 linux-zo89 polkitd[2152]: Unregistered Authentication Agent for unix-session:1 (system bus name :1.36, object path /org/kde/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
> 2014-02-22T10:54:27.203567+01:00 linux-zo89 bluetoothd[2071]: Failed to remove UUID: Invalid Parameters (0x0d)
> 2014-02-22T10:54:27.301433+01:00 linux-zo89 kdm: :0[2203]: pam_unix(xdm:session): session closed for user myusername
> 2014-02-22T10:54:27.450476+01:00 linux-zo89 systemd[1]: Stopping Session 1 of user myusername.
> 2014-02-22T10:54:27.450823+01:00 linux-zo89 systemd[1]: Stopped Session 1 of user myusername.
> 2014-02-22T10:54:27.451043+01:00 linux-zo89 systemd[1]: Stopping Bluetooth.
> 2014-02-22T10:54:27.451281+01:00 linux-zo89 systemd[1]: Stopped target Bluetooth.
> 2014-02-22T10:54:27.451864+01:00 linux-zo89 systemd[1]: Stopping Sound Card.
> 2014-02-22T10:54:27.452154+01:00 linux-zo89 systemd[1]: Stopped target Sound Card.
> 2014-02-22T10:54:27.452396+01:00 linux-zo89 systemd[1]: Stopping Stop Read-Ahead Data Collection 10s After Completed Startup.
> 2014-02-22T10:54:27.452560+01:00 linux-zo89 systemd[1]: Stopped Stop Read-Ahead Data Collection 10s After Completed Startup.
> 2014-02-22T10:54:27.452728+01:00 linux-zo89 systemd[1]: Stopping User Manager for 0...
> 2014-02-22T10:54:27.452996+01:00 linux-zo89 systemd[1]: Stopping User Manager for 1000...
> 2014-02-22T10:54:27.453293+01:00 linux-zo89 systemd[1]: Stopping Graphical Interface.
> 2014-02-22T10:54:27.453580+01:00 linux-zo89 systemd[1]: Stopped target Graphical Interface.
> 2014-02-22T10:54:27.453841+01:00 linux-zo89 systemd[1]: Stopping LSB: X Display Manager...
> 2014-02-22T10:54:27.454144+01:00 linux-zo89 systemd[1]: Stopping Multi-User System.
> 2014-02-22T10:54:27.454865+01:00 linux-zo89 systemd[1]: Stopped target Multi-User System.
> 2014-02-22T10:54:27.455587+01:00 linux-zo89 systemd[1]: Stopping Command Scheduler...
> 2014-02-22T10:54:27.456509+01:00 linux-zo89 systemd[1]: Stopping OpenSSH Daemon...
> 2014-02-22T10:54:27.458857+01:00 linux-zo89 rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="2124" x-info="http://www.rsyslog.com"] exiting on signal 15.
> 2014-02-22T10:55:17.451601+01:00 linux-zo89 rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="1505" x-info="http://www.rsyslog.com"] start
If something happens, it does after the syslog daemon is stopped, thus
nothing can be recorded on log.
On 2014-02-22 12:26, mikesol wrote:
>
> robin_listas;2626457 Wrote:
>>
>>
>> Try disable Plymouth, as wolfi323 said.
>>
>
> Yes I did it, and the only message that I see is “Reboot: Power down”.
>
> [image:
> https://dl.dropboxusercontent.com/u/70467261/IMG_20140222_121322.jpg]
Ok, try something else (with plymouth disabled).
Log out from KDE or whatever you use.
Switch to a text console: type ctrl-alt-f1.
Log in there as root.
Enter “halt -p”.
And watch what happens…
If it gets stuck, make a photo of the messages. Sometimes you still can
press ctrl-alt-f10 and see some messages in there.
OK, so the system does in fact shut down successfully. What doesn’t work is turning off power, which is most likely ACPI related I’d guess.
Just to reassure you: a hard shutdown (by pressing the power button for a few seconds) doesn’t cause any harm in that state, as the system is already shut down.
Maybe some playing with the BIOS’s ACPI settings might help?
Or specifying some ACPI boot options?
Ok this a start, but it’s a kind weird, isn’t it? Anyway, I discovered that if I restart, go to the grub console (F2 in the grub screen) and type “halt”, it shutdowns and poweroffs completely the laptop.
Maybe some playing with the BIOS’s ACPI settings might help?
Or specifying some ACPI boot options?
I’d wish! I installed Opensuse using UEFI with secure boot (The only way to make all work). In fact my first option with this new machine was to use Tumbleweed, but I failed miserably because the newer kernels aren’t signed and I can’t boot with them.
Maybe in another related issue. If I suspend my machine, it keeps freeze when I try to start it back.
Is it the same issue or I have to report it in another thread?
F2 in grub? That’s the language setting, isn’t it?
Are you using grub legacy or grub2?
I tried these options but nothing “reboot=kbd”, or =pci, efi, triple, bios. Could you please suggest me something else to try?
I thought about “acpi_osi=Windows” or something like that. But I’m not really experienced with those either.
I’d wish! I installed Opensuse using UEFI with secure boot (The only way to make all work). In fact my first option with this new machine was to use Tumbleweed, but I failed miserably because the newer kernels aren’t signed and I can’t boot with them.
Well, you should be able to turn off secure boot in the BIOS settings (with UEFI turned ON of course).
But I have absolutely no expierence with that UEFI/secure boot stuff, as all of my systems still have a legacy BIOS.
Maybe in another related issue. If I suspend my machine, it keeps freeze when I try to start it back.
Is it the same issue or I have to report it in another thread?
No idea, could be the same issue, could be not.
Does it really freeze? There is an issue in KDE in which the screen locker would not show a password dialog even when a password is required to unlock after resume. So, do you have a black screen or something, or is there a wallpaper and the mouse cursor?
Thanks Wolfi! To deactivate the secure boot It was only necessary set a supervisor password. I installed the Kernel 3.13 and I can shutdown without problems. Maybe this bug has to be backported to 3.11 or something. In any case, thanks again!
Does it really freeze? There is an issue in KDE in which the screen locker would not show a password dialog even when a password is required to unlock after resume. So, do you have a black screen or something, or is there a wallpaper and the mouse cursor?
In fact there are two different behaviors. If I explicitly click the button “Suspend to Ram” and then tried to recover the session, I get only a black screen.
But, if I leave it for 10 minutes unplugged, the machine get sleep and when i tried to recover the session I see only the wallpaper and the mouse cursor.
There won’t be any 3.11 kernels any more, as 3.11 has been EOLed in November.
But you might want to file a bug report at http://bugzilla.novell.com (don’t forget to link to that upstream bug report and mention that kernel 3.13 works for you).
Maybe they would backport the patch and include it in an update. I have no idea though, if it would be even possible to backport it.
In fact there are two different behaviors. If I explicitly click the button “Suspend to Ram” and then tried to recover the session, I get only a black screen.
Have you tried with kernel 3.13 already?
I find that strange since suspend/resume does apparently seem to work:
But, if I leave it for 10 minutes unplugged, the machine get sleep and when i tried to recover the session I see only the wallpaper and the mouse cursor.
You can also change the power management settings to not require a password after resume (in the “Advanced” tab), or to not suspend at all automatically.
Enabling “Require Passwort after” in the screen locker/screen saver settings should fix this also, but you would need the password everytime the screen locker kicks in then of course.
Anyway, no need to open a new thread for this problem, there are quite few recent ones already (and the bug report)…
I find that strange since suspend/resume does apparently seem to work:
I’m using the kernel 3.13 and that happens. I workaround this changing all the instances of suspension by hibernation in the power manager settings. It isn’t very elegant but works for me (while I remember don’t click to the “Suspend to Ram” button)
