From: Liam Howlett <liam.howlett@oracle.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Heiko Carstens <hca@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mapletree-vs-khugepaged
Date: Thu, 19 May 2022 22:38:56 +0000 [thread overview]
Message-ID: <20220519223848.wp77de6ohc744hek@revolver> (raw)
In-Reply-To: <28f3958f-dd25-cb1a-0a4c-040e7706ffc7@roeck-us.net>
* Guenter Roeck <linux@roeck-us.net> [220519 17:42]:
> On 5/19/22 07:35, Liam Howlett wrote:
> > * Guenter Roeck <linux@roeck-us.net> [220517 10:32]:
> >
> > ...
> > >
> > > Another bisect result, boot failures with nommu targets (arm:mps2-an385,
> > > m68k:mcf5208evb). Bisect log is the same for both.
> > ...
> > > # first bad commit: [bd773a78705fb58eeadd80e5b31739df4c83c559] nommu: remove uses of VMA linked list
> >
> > I cannot reproduce this on my side, even with that specific commit. Can
> > you point me to the failure log, config file, etc? Do you still see
> > this with the fixes I've sent recently?
> >
>
> This was in linux-next; most recently with next-20220517.
> I don't know if that was up-to-date with your patches.
> The problem seems to be memory allocation failures.
> A sample log is at
> https://kerneltests.org/builders/qemu-m68k-next/builds/1065/steps/qemubuildcommand/logs/stdio
> The log history at
> https://kerneltests.org/builders/qemu-m68k-next?numbuilds=30
> will give you a variety of logs.
I did hunt that down. It looks like it's allocating 512kb and failing.
I tried the commit you see the failures on and my qemu boots fine.
>
> The configuration is derived from m5208evb_defconfig, with initrd
> and command line embedded in the image. You can see the detailed
> configuration updates at
> https://github.com/groeck/linux-build-test/blob/master/rootfs/m68k/run-qemu-m68k.sh
>
> Qemu command line is
>
> qemu-system-m68k -M mcf5208evb -kernel vmlinux \
> -cpu m5208 -no-reboot -nographic -monitor none
> -append "rdinit=/sbin/init console=ttyS0,115200"
>
> with initrd from
> https://github.com/groeck/linux-build-test/blob/master/rootfs/m68k/rootfs-5208.cpio.gz
I'm using buildroot-2022.02.1, so maybe that's the difference?
Buildroot has the following qemu line:
qemu-system-m68k -M mcf5208evb -cpu m5208 -kernel vmlinux -nographic
>
> I use qemu v6.2, but any recent qemu version should work.
>
> Hope this helps,
> Guenter
Thanks for the information. I will keep digging into it.
Liam
next prev parent reply other threads:[~2022-05-19 22:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 17:20 [PATCH] mapletree-vs-khugepaged Guenter Roeck
2022-04-28 19:27 ` Liam Howlett
2022-04-29 12:09 ` Heiko Carstens
2022-04-29 13:01 ` Liam Howlett
2022-04-29 13:10 ` Heiko Carstens
2022-04-29 16:18 ` Liam Howlett
2022-05-02 9:10 ` Geert Uytterhoeven
2022-05-13 14:46 ` Sven Schnelle
2022-05-13 14:51 ` Sven Schnelle
2022-05-13 16:49 ` Andrew Morton
2022-05-13 17:00 ` Liam Howlett
2022-05-15 20:02 ` Sven Schnelle
2022-05-16 14:02 ` Liam Howlett
2022-05-16 15:37 ` Sven Schnelle
2022-05-16 15:50 ` Liam Howlett
2022-05-16 17:10 ` Sven Schnelle
2022-05-17 14:52 ` Liam Howlett
2022-05-17 11:53 ` Heiko Carstens
2022-05-17 12:26 ` Heiko Carstens
2022-05-17 13:23 ` Guenter Roeck
2022-05-17 15:03 ` Liam Howlett
2022-05-17 16:28 ` Guenter Roeck
2022-05-17 20:38 ` Liam Howlett
2022-05-17 14:32 ` Guenter Roeck
2022-05-19 14:35 ` Liam Howlett
2022-05-19 21:41 ` Guenter Roeck
2022-05-19 22:38 ` Liam Howlett [this message]
2022-05-30 17:38 ` Liam Howlett
2022-05-31 18:56 ` Liam Howlett
2022-06-01 19:06 ` Liam Howlett
2022-05-13 17:28 ` Guenter Roeck
2022-05-13 20:12 ` Yang Shi
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=20220519223848.wp77de6ohc744hek@revolver \
--to=liam.howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@roeck-us.net \
--cc=svens@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).