[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y/wo7H+ZZzFoEqvk@casper.infradead.org>
Date: Mon, 27 Feb 2023 03:52:12 +0000
From: Matthew Wilcox <willy@...radead.org>
To: "Liam R. Howlett" <Liam.Howlett@...cle.com>,
kernel test robot <oliver.sang@...el.com>,
oe-lkp@...ts.linux.dev, lkp@...el.com,
linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
linux-perf-users@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [linus:master] [mm/mmap] 0503ea8f5b: kernel_BUG_at_mm/filemap.c
On Sun, Feb 26, 2023 at 10:17:56PM -0500, Liam R. Howlett wrote:
> Are you sure about this bisection? I'm not saying it isn't my fault or
> looking to blame others, but I suspect we are indeed looking at the
> wrong commit here.
I concur. Looking at the backtrace, I think it's more likely to be
a pagecache, swapcache or shmfs issue. I'll look more in the morning.
> > bin/lkp qemu -k <bzImage> -m modules.cgz job-script # job-script is attached in this email
> >
> > # if come across any failure that blocks the test,
> > # please remove ~/.lkp and /lkp dir to run from a clean state.
> >
>
> This does not work for me. Since my last use of lkp it seems something
> was changed and now -watchdog is not recognized by my qemu and so my
> attempts to reproduce this are failing. Is there a way to avoid using
> the -watchdog flag? Running the command by hand fails as it seems some
> files are removed on exit?
https://www.qemu.org/docs/master/about/removed-features.html
-watchdog (since 7.2)
Use -device instead.
(I have no idea what this means, but maybe it's a clue?)
Powered by blists - more mailing lists