You are not logged in.
Pages: 1
Recently my i86_64 system has been hanging on shutdown, the boot partition needing checking on restart (no errors reported). After waiting over ten minutes for shutdown to complete, it's still hung. CTL·ALT·DEL has no effect.
Running a debug shell (F9) also hangs when console (F1) freezes during shutdown.
"sync && poweroff -f " avoids the hang but the boot partitions still requires checking.
If I run "sudo umount /dev/sdf1 " (/boot) then "sudo sync && sudo reboot -f " the system shuts down and reboots without requiring file-system check.
"lsof " shows no open files on /boot/…
No serial console available.
What could be causing this..? & are they separate issues..?
This system boots with grub, has been around a long time, survived the switch to systemd and survived a major hardware upgrade.
Ref: freedesktop.org/systemd/debugging
Ref: Full System Spec
Edit: corrected the Sysinfo link.
-------
Edit:
After upgrading to systemd-208, the debug console(F9) now works. Shutdown hangs running vclock. The error message from journalctl -f is
vlock[528]: pam_unix(vclock:auth): auth could not identify password for [..user..]
which continues until system is killed by hardware reboot.
I have compared /etc/pam.d/ to one from a properly behaving i686 laptop, and could see no differences, but my knowledge of PAM in very limited.
I'm running XFCE4 and run Xfce automatically using the xorg-xinit method at Start X at Login combining with Automatic login to virtual console
Last edited by keepitsimpleengineer (2013-10-07 21:05:01)
Al Einstein: "Man soll die Dinge so einfach machen wie möglich ~ aber nicht einfacher." (Things should be as simple as possible ~ but not too simple.) ~ Al (Einstein) war ein Cousin von Albert, "Al" ist die Abkürzung für Aloysius
Offline
I reverted to systemd systemd-204-3-x86_64 and the problem ceased.
Hopefull that systemd-208-1-x86_64 would solve the problem, I upgraded to that.
The same problem exists excpt the debug shell (F9) is not frozen.
Last edited by keepitsimpleengineer (2013-10-03 21:49:52)
Al Einstein: "Man soll die Dinge so einfach machen wie möglich ~ aber nicht einfacher." (Things should be as simple as possible ~ but not too simple.) ~ Al (Einstein) war ein Cousin von Albert, "Al" ist die Abkürzung für Aloysius
Offline
There are several threads about this. Please search before posting.
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
There are several threads about this. Please search before posting.
I have searched the forums, bugs, upstream... and found several similar but not the same occurance that I am experiencing.
If you are aware of some search result I have missed, could you please post them?
Thanx...
Al Einstein: "Man soll die Dinge so einfach machen wie möglich ~ aber nicht einfacher." (Things should be as simple as possible ~ but not too simple.) ~ Al (Einstein) war ein Cousin von Albert, "Al" ist die Abkürzung für Aloysius
Offline
I was thinking of e.g. https://bbs.archlinux.org/viewtopic.php?id=170756
What is vclock for? Seems to be connected with vdso? Is that right? Which is some sort of virtualised something? (That is, I didn't understand the explanation I found.)
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
I was thinking of e.g. https://bbs.archlinux.org/viewtopic.php?id=170756
What is vclock for? Seems to be connected with vdso? Is that right? Which is some sort of virtualised something? (That is, I didn't understand the explanation I found.)
vlock (recently moved into kbd) locks virtual consoles. I presume opening XFCE at boot without password uses it.
I'm running XFCE4 and run Xfce automatically using the xorg-xinit method at Start X at Login combining with Automatic login to virtual console
I believe this locks virtual console/terminal #1 (Alt-F1) in which to run X.
I presume systemd tries to unlock this locked virtual console as a part of shutdown, and stumbles in authorization, then continues ad infinitum. If so, two failures indicated; authorization (PAM), and systemd allowing the unlimited loop with failure.
After upgrading to systemd-208, the debug console(Alt-F9) now works. Shutdown hangs running vclock. The error message from journalctl -f is
vclock[528]: pam_unix(vclock:auth): auth could not identify password for [..user..]
which continues until system is killed by hardware reboot.
In any case, I'm working struggling with that theory. Curious as to why systemd-204-3-x86_64 had no problem with this while systemd-207-3-x86_64, systemd-207-5-x86_64, and systemd-208-1-x86_64 do.
Al Einstein: "Man soll die Dinge so einfach machen wie möglich ~ aber nicht einfacher." (Things should be as simple as possible ~ but not too simple.) ~ Al (Einstein) war ein Cousin von Albert, "Al" ist die Abkürzung für Aloysius
Offline
Wait. vclock or vlock? Your original post says vclock but now you are talking about vlock.
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
Wait. vclock or vlock? Your original post says vclock but now you are talking about vlock.
***vclock***
I apologize, fat finger effect...
Last edited by keepitsimpleengineer (2013-10-07 21:05:53)
Al Einstein: "Man soll die Dinge so einfach machen wie möglich ~ aber nicht einfacher." (Things should be as simple as possible ~ but not too simple.) ~ Al (Einstein) war ein Cousin von Albert, "Al" ist die Abkürzung für Aloysius
Offline
Which is not the same as vlock and is not in kbd, right?
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
Temporary but treacherous work around found.
Modifying PAM bypassing authentication for vclock by adding this to /etc/pam.d/
[--ljohnson{14:39:08}~]$ cat /etc/pam.d/vclock
#%PAM-1.0
auth include system-auth
account required pam_permit.so
which passes all authentication requests by vclock, AFAIK
Al Einstein: "Man soll die Dinge so einfach machen wie möglich ~ aber nicht einfacher." (Things should be as simple as possible ~ but not too simple.) ~ Al (Einstein) war ein Cousin von Albert, "Al" ist die Abkürzung für Aloysius
Offline
Which is not the same as vlock and is not in kbd, right?
You are correct, I was confused.
Now I have no idea of the source of vclock. but perhaps it is associated with linux-vdso which is outside my ken.
Al Einstein: "Man soll die Dinge so einfach machen wie möglich ~ aber nicht einfacher." (Things should be as simple as possible ~ but not too simple.) ~ Al (Einstein) war ein Cousin von Albert, "Al" ist die Abkürzung für Aloysius
Offline
Apparently, I am still confused.
It is vlock, not vclock.
vlock is invoked in .bash_profile when starting xfce4.
The error message from jorunalctl -f in debug console ...
reads:
vclock[528]: pam_unix(vlock:auth): auth could not identify password for [ljohnson]
Todays large update has broken xfce4 so I am going to fix that, apparently some changes are required after switching to systemd which I did not make.
Al Einstein: "Man soll die Dinge so einfach machen wie möglich ~ aber nicht einfacher." (Things should be as simple as possible ~ but not too simple.) ~ Al (Einstein) war ein Cousin von Albert, "Al" ist die Abkürzung für Aloysius
Offline
Removed the call to vlock in ~/.bash_profile used to auto-start xfce4 at login. Resolved the problem.
Al Einstein: "Man soll die Dinge so einfach machen wie möglich ~ aber nicht einfacher." (Things should be as simple as possible ~ but not too simple.) ~ Al (Einstein) war ein Cousin von Albert, "Al" ist die Abkürzung für Aloysius
Offline
Pages: 1