public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
	lkft-triage@lists.linaro.org, regressions@lists.linux.dev,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Jiri Slaby <jirislaby@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	Vincent Whitchurch <vincent.whitchurch@axis.com>
Subject: Re: mainline: qemu_arm64 boot failed - Failed to start Hostname Service - Stopped Serial Getty on ttyAMA0
Date: Wed, 30 Mar 2022 10:24:49 +0200	[thread overview]
Message-ID: <YkQT0ROhctplAuds@kroah.com> (raw)
In-Reply-To: <CA+G9fYuK2GDqWHuW3oOi2O0h4RWsLLQb9198i-PS=nMf1t0T7w@mail.gmail.com>

On Wed, Mar 30, 2022 at 01:45:14PM +0530, Naresh Kamboju wrote:
> On Wed, 30 Mar 2022 at 13:32, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > On Wed, Mar 30, 2022 at 12:46:40PM +0530, 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@tuxmake)
> > > (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.
> > > [    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
> > > running for Network Manager (9s / 1min 30s)[   ] A start job is
> > > running for Network Manager (9s / 1min 30s)[    [ A start job is
> > > running for Network Manager (10s / 1min 30s)[     ] A start job is
> > > running for Network Manager (10s / 1min 30s)[    [ A start job is
> > > running for Network Manager (11s / 1min 30s)[   ] A start job is
> > > running for Network Manager (12s / 1min 30s)[   ] A start job is
> > > running for Network Manager (12s / 1min 30s)[   ] A start job is
> > > running for Network Manager (13s / 1min 30s)[   ] A start job is
> > > running for Network Manager (13s / 1min 30s)    ] A start job is
> > > running for Network Manager (14s / 1min 30s)[     ] A start job is
> > > running for Network Manager (14s / 1min 30s)    ] A start job is
> > > running for Network Manager (15s / 1min 30s)[   ] A start job is
> > > running for Network Manager (16s / 1min 30s)[   ] A start job is
> > > running for Network Manager (16s / 1min 30s)[   ] A start job is
> > > running for Network Manager (17s / 1min 30s)[   ] A start job is
> > > running for Network Manager (17s / 1min 30s)[    [ A start job is
> > > running for Network Manager (18s / 1min 30s)[     ] A start job is
> > > running for Network Manager (19s / 1min 30s)[    [ A start job is
> > > running for Network Manager (19s / 1min 30s)[   ] A start job is
> > > running for Network Manager (19s / 1min 30s)[   ] A start job is
> > > running for Network Manager (20s / 1min 30s)[   ] A start job is
> > > running for Network Manager (20s / 1min 30s)[   ] A start job is
> > > running for Network Manager (21s / 1min 30s)    ] A start job is
> > > running for Network Manager (21s / 1min 30s)[     ] A start job is
> > > running for Network Manager (22s / 1min 30s)    ] A start job is
> > > running for Network Manager (22s / 1min 30s)[   ] A start job is
> > > running for Network Manager (23s / 1min 30s)[   ] A start job is
> > > running for Network Manager (23s / 1min 30s)[   ] A start job is
> > > running for Network Manager (24s / 1min 30s)[   ] A start job is
> > > running for Network Manager (24s / 1min 30s)[    [ A start job is
> > > running for Network Manager (25s / 1min 30s)[     ] A start job is
> > > 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.
> > > [FAILED] Failed to start DNS forwarder and DHCP server.
> > > See 'systemctl status dnsmasq.service' for details.
> > > [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.
> > > [  OK  ] Stopped Getty on tty1.
> > > [  OK  ] Started Getty on tty1.
> > >
> > > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> > >
> > > --
> > > Linaro LKFT
> > > https://lkft.linaro.org
> > >
> > > [1] https://lkft.validation.linaro.org/scheduler/job/4809453#L252
> > > [2] https://lkft.validation.linaro.org/scheduler/job/4809125#L386
> > >
> >
> > That's a lot of userspace logs, any kernel logs showing that anything
> > failed?
> 
> I do not see kernel logs failures here.

Great, then the kernel is working just fine!  :)

Seriously, without some sort of hint, it's going to be impossible for us
to know what to do here...

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-03-30  8:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30  7:16 mainline: qemu_arm64 boot failed - Failed to start Hostname Service - Stopped Serial Getty on ttyAMA0 Naresh Kamboju
2022-03-30  7:18 ` Naresh Kamboju
2022-03-30  8:02 ` Jiri Slaby
2022-03-30  8:02 ` Greg Kroah-Hartman
2022-03-30  8:15   ` Naresh Kamboju
2022-03-30  8:24     ` Greg Kroah-Hartman [this message]
2022-03-30 13:54       ` Naresh Kamboju

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YkQT0ROhctplAuds@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=regressions@lists.linux.dev \
    --cc=vincent.whitchurch@axis.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox