Bug#877672: [systemd] System Stalled at Pam-nologon

[Michael Biebl]

Control: tags -1 moreinfo unreproducible

Am 04.10.2017 um 08:21 schrieb David Baron:
> Package: systemd
> Version: 234-3
> Severity: critical
> 
> --- Please enter the report below this line. ---
> This touches systemd because of concurrent boot threads but actual bug may be 
> elsewhere!
> 
> Sporadically get, instead of the usual bootup and kdm start, a console logon. 
> It is not possible to log on, getting the pam-nologon error, system booting.
> Actually had kdm start up in this state, though impossible to log on 
> (concurrent boot).

Please provide exact error messages. To get a more verbose boot you can
change the options in the grub boot loader and append
"systemd.log_level=debug".
If everything else fails, take a screenshot and attach the image.

Is this problem reproducible? Does it happen on every boot?


> MAY be related to:
> 1. CPU too hot. In this case, retries will simple abort early on. Can do 
> nothing but spray cool and wait.
> 2. Network unavailable. Had this happen as well. When finally succeeded to 
> normal boot, I had to restart network-services.
> 3. Zram. Error seems more frequent after this was activated.

And how would this be related to systemd?


> --- System information. ---
> Architecture: 
> Kernel:       Linux 4.11.0-1-amd64
> 
> Debian Release: buster/sid
>   500 yakkety         ppa.launchpad.net 
>   500 unstable        ftp.us.debian.org 
>   500 testing         ftp.us.debian.org 
>   500 sid             linux.dropbox.com 
>   500 lucid           ppa.launchpad.net 
>   100 jessie-backports ftp.us.debian.org 
>     1 experimental    ftp.us.debian.org 

What kind of frankendebian is that system, mixing all those different
distros/release...

> --- Package information. ---
> Depends                              (Version) | Installed
> ==============================================-+-============================
> libacl1                          (>= 2.2.51-8) | 2.2.52-3+b1
> libapparmor1                 (>= 2.9.0-3+exp2) | 2.11.0-11
> libaudit1                         (>= 1:2.2.1) | 1:2.7.7-1+b2
> libblkid1                          (>= 2.19.1) | 
> libc6                                (>= 2.17) | 
> libcap2                            (>= 1:2.10) | 
> libcryptsetup4                    (>= 2:1.4.3) | 
> libgcrypt20                         (>= 1.7.0) | 
> libgpg-error0                        (>= 1.14) | 
> libidn11                             (>= 1.13) | 
> libip4tc0          (>= 1.6.0+snapshot20161117) | 
> libkmod2                               (>= 5~) | 
> liblz4-1                         (>= 0.0~r130) | 
> liblzma5              (>= 5.1.1alpha+20120614) | 
> libmount1                          (>= 2.26.2) | 
> libpam0g                         (>= 0.99.7.1) | 
> libseccomp2                         (>= 2.3.1) | 
> libselinux1                         (>= 2.1.9) | 
> libsystemd0                          (= 234-3) | 
> util-linux                         (>= 2.27.1) | 
> mount                                (>= 2.26) | 
> adduser                                        | 
> procps                                         | 

Are those packages really not installed or why is the version
information missing?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20171010/14ea572e/attachment.sig>