[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y22DiF5Q5EDUIrZE@google.com>
Date: Thu, 10 Nov 2022 15:04:40 -0800
From: Minchan Kim <minchan@...nel.org>
To: Petr Vorel <pvorel@...e.cz>
Cc: ltp@...ts.linux.it, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
Nitin Gupta <ngupta@...are.org>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Jens Axboe <axboe@...nel.dk>,
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>,
Martin Doucha <mdoucha@...e.cz>,
Yang Xu <xuyang2018.jy@...itsu.com>
Subject: Re: [PATCH 0/1] Possible bug in zram on ppc64le on vfat
On Mon, Nov 07, 2022 at 10:47:33PM +0100, Petr Vorel wrote:
> Hi Minchan,
>
> > On Mon, Nov 07, 2022 at 08:11:35PM +0100, Petr Vorel wrote:
> > > Hi all,
>
> > > following bug is trying to workaround an error on ppc64le, where
> > > zram01.sh LTP test (there is also kernel selftest
> > > tools/testing/selftests/zram/zram01.sh, but LTP test got further
> > > updates) has often mem_used_total 0 although zram is already filled.
>
> > Hi, Petr,
>
> > Is it happening on only ppc64le?
> I haven't seen it on other archs (x86_64, aarch64).
>
> > Is it a new regression? What kernel version did you use?
> Found on openSUSE kernel, which uses stable kernel releases 6.0.x.
> It's probably much older, first I've seen it some years ago (I'm not able to find kernel version), but it was random. Now it's much more common.
>
> Test runs on VM (I can give qemu command or whatever you need to know about it)
> I'll try to verify it on some bare metal ppc64le.
Hi Petr and Martin,
Thanks for testing and meaning information.
Could you tell how I could create VM to run ppc64le and run the test?
I'd like to reproduce in my local to debug it.
Thanks!
Powered by blists - more mailing lists