linux-kernel - Re: mainline: qemu_arm64 boot failed - Failed to start Hostname Service

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <292d7225-5ac2-71f0-08bc-8c33217fb93f@kernel.org>
Date:   Wed, 30 Mar 2022 10:02:16 +0200
From:   Jiri Slaby <jirislaby@...nel.org>
To:     Naresh Kamboju <naresh.kamboju@...aro.org>,
        open list <linux-kernel@...r.kernel.org>,
        lkft-triage@...ts.linaro.org, regressions@...ts.linux.dev,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>,
        Vincent Whitchurch <vincent.whitchurch@...s.com>
Subject: Re: mainline: qemu_arm64 boot failed - Failed to start Hostname
 Service - Stopped Serial Getty on ttyAMA0

Hi,

I am not sure what this report is good for. See below.

On 30. 03. 22, 9:16, Naresh Kamboju wrote:
> Linux mainline kernel booting qemu_arm64 and Raspberry Pi 4 boot
> failed [1] and [2].
> 
> Boot log:
> [    0.000000] Booting Linux on physical CPU 0x0000000000 [0x413fd0c1]
> [    0.000000] Linux version 5.17.0 (tuxmake@...make)
> (aarch64-linux-gnu-gcc (Debian 11.2.0-18) 11.2.0, GNU ld (GNU Binutils
> for Debian) 2.38) #1 SMP PREEMPT @1648607824
> [    0.000000] Machine model: linux,dummy-virt
> 
> <trim>
> 
>           Starting Hostname Service...
> [FAILED] Failed to start Hostname Service.
> See 'systemctl status systemd-hostnamed.service' for details.

One failure here.

> [    2.453172] random: crng init done
> [    2.453522] random: 7 urandom warning(s) missed due to ratelimiting
> [    2.483013] audit: type=1334 audit(1648621045.348:8): prog-id=0 op=UNLOAD
> [    2.483953] audit: type=1334 audit(1648621045.348:9): prog-id=0 op=UNLOAD
> [    2.609230] audit: type=1334 audit(1648621045.476:10): prog-id=10 op=LOAD
> [  OK  ] Started Resize root filesystem to fit available disk space.
> [     ] A start job is running for Network Manager (6s / 1min 30s)
> ] A start job is running for Network Manager (7s / 1min 30s)[   ] A
> start job is running for Network Manager (7s / 1min 30s)[   ] A start
> job is running for Network Manager (8s / 1min 30s)[   ] A start job is

So NM is unable to start -- another networking failure.

> ...
> running for Network Manager (25s / 1min 30s)[  OK  ] Started Network
> Manager.
> [  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
>           Starting Network Manager Script Dispatcher Service...
> [   27.359980] kauditd_printk_skb: 11 callbacks suppressed
> [   27.359988] audit: type=1701 audit(1648621070.228:22):
> auid=4294967295 uid=0 gid=0 ses=4294967295 pid=313 comm=\"(spatcher)\"
> exe=\"/lib/systemd/systemd\" sig=6 res=1
> [  OK  ] Reached target Network.
>           Starting DNS forwarder and DHCP server...
> [   27.367248] audit: type=1701 audit(1648621070.232:23):
> auid=4294967295 uid=0 gid=0 ses=4294967295 pid=315 comm=\"(dnsmasq)\"
> exe=\"/lib/systemd/systemd\" sig=6 res=1
>           Starting Permit User Sessions...
> [   27.371110] audit: type=1701 audit(1648621070.240:24):
> auid=4294967295 uid=0 gid=0 ses=4294967295 pid=317 comm=\"(sessions)\"
> exe=\"/lib/systemd/systemd\" sig=6 res=1
> [FAILED] Failed to start Network Manager Script Dispatcher Service.
> See 'systemctl status NetworkManager-dispatcher.service' for details.

And finally NM failed here. And it also tells you what to do for further 
investigation.

> [FAILED] Failed to start DNS forwarder and DHCP server.
> See 'systemctl status dnsmasq.service' for details.

Again, a network service.

> [FAILED] Failed to start Permit User Sessions.
> See 'systemctl status systemd-user-sessions.service' for details.
> [  OK  ] Started Getty on tty1.
> [  OK  ] Started Serial Getty on ttyAMA0.
> [  OK  ] Reached target Login Prompts.
> [  OK  ] Reached target Multi-User System.
>           Starting Update UTMP about System Runlevel Changes...
> [   27.402975] audit: type=1701 audit(1648621070.268:25):
> auid=4294967295 uid=0 gid=0 ses=4294967295 pid=322 comm=\"(ate-utmp)\"
> exe=\"/lib/systemd/systemd\" sig=6 res=1
> [FAILED] Failed to start Update UTMP about System Runlevel Changes.
> See 'systemctl status systemd-update-utmp-runlevel.service' for details.
> [   32.398140] audit: type=1701 audit(1648621075.264:26):
> auid=4294967295 uid=0 gid=0 ses=4294967295 pid=320 comm=\"(agetty)\"
> exe=\"/lib/systemd/systemd\" sig=6 res=1
> [   32.399187] audit: type=1701 audit(1648621075.264:27):
> auid=4294967295 uid=0 gid=0 ses=4294967295 pid=321 comm=\"(agetty)\"
> exe=\"/lib/systemd/systemd\" sig=6 res=1
> [  OK  ] Stopped Serial Getty on ttyAMA0.
> [  OK  ] Started Serial Getty on ttyAMA0.

      ^^ This one is "OK", so I see no connection to serial layer at all 
as the Subject and CCed people list suggest. Am I missing something?

regards,
-- 
js
suse labs