You are not logged in.
Pages: 1
Disclaimer
I've sporadically experienced this issue on two Dell laptops, however it doesn't seem to be laptop specific.
I'm unable to reliably reproduce it as it only happens sporadically.
Issue
No matter what kernel I run (be it lts, hardened or standard), on some reboots I experience a system hang for
about 90 seconds witch black screen and an underscore cursor blinking in top left corner. After that, system
reboots.
Additional Info
UEFI install
Laptop Dell Latitude 5501, i7 9th gen, no nvidia graphics, only Intel UHD 630.
At first I thought this has to do with PCI, that's why I added this to mi grub conf (and updated grub of course):
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet reboot=pci acpi=force"That didn't help though.
Logs
Here's journal log from the last reboot during which this issue occurred.
journalctl -r
-- Reboot --
Jul 17 14:08:48 arch systemd[566]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[patres] ruser=[<unknown>] rhost=[<unkno>
Jul 17 14:08:48 arch systemd[565]: Reached target Exit the Session.
Jul 17 14:08:48 arch systemd[565]: Finished Exit the Session.
Jul 17 14:08:48 arch systemd[565]: systemd-exit.service: Succeeded.
Jul 17 14:08:48 arch systemd[565]: Reached target Shutdown.
Jul 17 14:08:48 arch systemd[565]: Closed Sound System.
Jul 17 14:08:48 arch systemd[565]: pulseaudio.socket: Succeeded.
Jul 17 14:08:48 arch systemd[565]: Closed p11-kit server.
Jul 17 14:08:48 arch systemd[565]: p11-kit-server.socket: Succeeded.
Jul 17 14:08:48 arch systemd[565]: Closed GnuPG cryptographic agent and passphrase cache.
Jul 17 14:08:48 arch systemd[565]: gpg-agent.socket: Succeeded.
Jul 17 14:08:48 arch systemd[565]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Jul 17 14:08:48 arch systemd[565]: gpg-agent-ssh.socket: Succeeded.
Jul 17 14:08:48 arch systemd[565]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Jul 17 14:08:48 arch systemd[565]: gpg-agent-extra.socket: Succeeded.
Jul 17 14:08:48 arch systemd[565]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jul 17 14:08:48 arch systemd[565]: gpg-agent-browser.socket: Succeeded.
Jul 17 14:08:48 arch systemd[565]: Closed GnuPG network certificate management daemon.
Jul 17 14:08:48 arch systemd[565]: dirmngr.socket: Succeeded.
Jul 17 14:08:48 arch systemd[565]: Closed D-Bus User Message Bus Socket.
Jul 17 14:08:48 arch systemd[565]: dbus.socket: Succeeded.
Jul 17 14:08:48 arch systemd[565]: Stopped target Timers.
Jul 17 14:08:48 arch systemd[565]: Stopped target Sockets.
Jul 17 14:08:48 arch systemd[565]: Stopped target Paths.
Jul 17 14:08:48 arch systemd[565]: Stopped target Basic System.
Jul 17 14:08:48 arch systemd[565]: Stopped Accessibility services bus.
Jul 17 14:08:48 arch systemd[565]: at-spi-dbus-bus.service: Succeeded.
Jul 17 14:08:48 arch systemd[565]: Stopped D-Bus User Message Bus.
Jul 17 14:08:48 arch systemd[565]: dbus.service: Succeeded.
Jul 17 14:08:48 arch systemd[565]: Stopping D-Bus User Message Bus...
Jul 17 14:08:48 arch systemd[565]: Stopping Accessibility services bus...
Jul 17 14:08:48 arch systemd[565]: Stopped target Sound Card.
Jul 17 14:08:48 arch systemd[565]: Stopped target Main User Target.
Jul 17 14:07:20 arch systemd[565]: pulseaudio.service: Succeeded.
Jul 17 14:02:35 arch systemd[565]: var-lib-docker-overlay2-opaque\x2dbug\x2dcheck383479491-merged.mount: Succeeded.
Jul 17 14:02:05 arch gpasswd[372517]: patres failed to add user patres to group docker: Permission deniedThere's approximately 90 second delay between these two entries:
Jul 17 14:08:48 arch systemd[565]: Stopped target Main User Target.
Jul 17 14:07:20 arch systemd[565]: pulseaudio.service: Succeeded.Could this be caused by pulseaudio?
Last edited by patresko (2020-07-17 12:44:29)
Offline
Looks like a shutdown issue. The 90 seconds is the default timeout for services that don't respond.
Jul 17 14:08:48 arch systemd[566]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[patres] ruser=[<unknown>] rhost=[<unkno>
<snip>
Jul 17 14:02:35 arch systemd[565]: var-lib-docker-overlay2-opaque\x2dbug\x2dcheck383479491-merged.mount: Succeeded.
Jul 17 14:02:05 arch gpasswd[372517]: patres failed to add user patres to group docker: Permission deniedThat's a strong indication towards a docker /systemd-user issue, maybe the truncated line has more useful info then is visible.
check https://wiki.archlinux.org/index.php/Sy … ing_output for ways to wrap instead of truncate journalctl output .
Last edited by Lone_Wolf (2020-07-17 12:51:42)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I would suspect systemd-user, since I've only installed docker today and this issue was prevalent before.
Untruncated journal doesn't seem to offer much help.
Jul 17 14:08:48 arch systemd[566]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[patres] ruser=[<unknown>] rhost=[<unknown>]Edit
I've just experienced the same issue on shutdown with hang taking place between the same two entries:
Jul 18 09:49:27 arch systemd[573]: Stopped target Main User Target.
Jul 18 09:47:59 arch systemd[573]: pulseaudio.service: Succeeded.And this is how journal looks upon rebooting without delay/hang:
Jul 18 10:13:18 arch systemd[557]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[patres] ruser=[<unknown>] rhost=[<unknown>]
Jul 18 10:13:18 arch systemd[556]: Reached target Exit the Session.
Jul 18 10:13:18 arch systemd[556]: Finished Exit the Session.
Jul 18 10:13:18 arch systemd[556]: systemd-exit.service: Succeeded.
Jul 18 10:13:18 arch systemd[556]: Reached target Shutdown.
Jul 18 10:13:18 arch systemd[556]: Closed Sound System.
Jul 18 10:13:18 arch systemd[556]: pulseaudio.socket: Succeeded.
Jul 18 10:13:18 arch systemd[556]: Closed p11-kit server.
Jul 18 10:13:18 arch systemd[556]: p11-kit-server.socket: Succeeded.
Jul 18 10:13:18 arch systemd[556]: Closed GnuPG cryptographic agent and passphrase cache.
Jul 18 10:13:18 arch systemd[556]: gpg-agent.socket: Succeeded.
Jul 18 10:13:18 arch systemd[556]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Jul 18 10:13:18 arch systemd[556]: gpg-agent-ssh.socket: Succeeded.
Jul 18 10:13:18 arch systemd[556]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Jul 18 10:13:18 arch systemd[556]: gpg-agent-extra.socket: Succeeded.
Jul 18 10:13:18 arch systemd[556]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jul 18 10:13:18 arch systemd[556]: gpg-agent-browser.socket: Succeeded.
Jul 18 10:13:18 arch systemd[556]: Closed GnuPG network certificate management daemon.
Jul 18 10:13:18 arch systemd[556]: dirmngr.socket: Succeeded.
Jul 18 10:13:18 arch systemd[556]: Closed D-Bus User Message Bus Socket.
Jul 18 10:13:18 arch systemd[556]: dbus.socket: Succeeded.
Jul 18 10:13:18 arch systemd[556]: Stopped target Timers.
Jul 18 10:13:18 arch systemd[556]: Stopped target Sockets.
Jul 18 10:13:18 arch systemd[556]: Stopped target Paths.
Jul 18 10:13:18 arch systemd[556]: Stopped target Basic System.
Jul 18 10:13:18 arch systemd[556]: Stopped Accessibility services bus.
Jul 18 10:13:18 arch systemd[556]: at-spi-dbus-bus.service: Succeeded.
Jul 18 10:13:18 arch systemd[556]: Stopped D-Bus User Message Bus.
Jul 18 10:13:18 arch systemd[556]: dbus.service: Succeeded.
Jul 18 10:13:17 arch systemd[556]: Stopping D-Bus User Message Bus...
Jul 18 10:13:17 arch systemd[556]: Stopping Accessibility services bus...
Jul 18 10:13:17 arch systemd[556]: Stopped target Main User Target.Last edited by patresko (2020-07-18 08:17:03)
Offline
Did you solve this issue?, I am also experiencing it for a while now.
Last edited by zwa (2021-03-24 17:13:08)
Offline
It would be better to find out why it is happening, but temporary you could change that 90s timeout to something lower in /etc/systemd/system.conf uncomment and change value DefaultTimeoutStopSec=90s . Details in 'man system.conf.d'. Also see:
https://bbs.archlinux.org/viewtopic.php?id=243206
https://bbs.archlinux.org/viewtopic.php?id=244508.
Last edited by xerxes_ (2021-03-24 18:45:25)
Offline
Pages: 1