From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Tong Zhang <ztong0001@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Domenico Andreoli <domenico.andreoli@linux.com>,
Andrew Morton <akpm@linux-foundation.org>,
Luis Chamberlain <mcgrof@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: boottime warning from todays linux-next
Date: Fri, 11 Feb 2022 12:43:02 +1100 [thread overview]
Message-ID: <20220211124302.7b0f0ec0@canb.auug.org.au> (raw)
In-Reply-To: <CAA5qM4BKwS9W5UCbnfo_xSTJKBuUEyNzUrg0UfGhoxWK5WK3RQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 608 bytes --]
Hi Tong,
On Thu, 10 Feb 2022 15:35:30 -0800 Tong Zhang <ztong0001@gmail.com> wrote:
>
> I am trying to see if I can reproduce this.
> Could you share the QEMU command line and pseries_le_defconfig?
> Latest kernel does not have pseries_le_defconfig so I assume you have
> your own version.
This is a ARCH=powerpc build and qemu run.
qemu-system-ppc64 -M pseries -cpu POWER8 -m 2G -vga none -nographic -kernel $vmlinux -initrd $initrd
I have a simple initrd that just boots to a login prompt.
Anyway, it seems that the mystery has been solved (hopefully).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-02-11 1:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 7:43 linux-next: boottime warning from todays linux-next Stephen Rothwell
2022-02-10 8:33 ` Stephen Rothwell
2022-02-10 10:41 ` Stephen Rothwell
2022-02-10 11:29 ` Stephen Rothwell
2022-02-10 23:19 ` Luis Chamberlain
2022-02-11 1:33 ` Stephen Rothwell
2022-02-11 1:38 ` Luis Chamberlain
2022-02-11 7:46 ` Stephen Rothwell
2022-02-11 18:51 ` Luis Chamberlain
2022-02-11 19:12 ` Tong Zhang
2022-02-10 18:06 ` Domenico Andreoli
2022-02-10 23:35 ` Tong Zhang
2022-02-11 1:43 ` Stephen Rothwell [this message]
2022-02-11 17:36 ` Tong Zhang
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=20220211124302.7b0f0ec0@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=domenico.andreoli@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=ztong0001@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.