From: Petr Vorel <pvorel@suse.cz>
To: Minchan Kim <minchan@kernel.org>
Cc: ltp@lists.linux.it, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Nitin Gupta <ngupta@vflare.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Jens Axboe <axboe@kernel.dk>,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
Martin Doucha <mdoucha@suse.cz>,
Yang Xu <xuyang2018.jy@fujitsu.com>
Subject: Re: [PATCH 0/1] Possible bug in zram on ppc64le on vfat
Date: Fri, 11 Nov 2022 10:29:28 +0100 [thread overview]
Message-ID: <Y24V+AUuivt1F/Kw@pevik> (raw)
In-Reply-To: <Y22DiF5Q5EDUIrZE@google.com>
> 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.
I suppose you don't have ppc64le bare metal machine, thus you run on x86_64.
One way would be to install on host qemu-system-ppc64, download iso image of any
distro which supports ppc64le and install it with virt-manager (which would fill
necessary qemu params).
Other way, which I often use is to compile system with Buildroot distribution.
You can clone my Buildroot distro fork, branch debug/zram [1].
I put there in 3 commits my configuration.
I added 0001-zram-Debug-mm_stat_show.patch [2] on the top of 6.0.7 with little debugging.
What is now only needed is to 1) install on host qemu-system-ppc64
(speedup build + Buildroot is configured not to compile qemu-system-ppc64),
then:
$ make # takes time
$ ./output/images/start-qemu.sh serial-only
When I have ppc64le host with enough space, I often use rapido [3],
but that crashed stable kernel (another story which I'll report soon).
Hope that helps.
Kind regards,
Petr
[1] https://github.com/pevik/buildroot/commits/debug/zram
[2] https://github.com/pevik/buildroot/blob/debug/zram/0001-zram-Debug-mm_stat_show.patch
[3] https://github.com/rapido-linux/rapido
WARNING: multiple messages have this Message-ID (diff)
From: Petr Vorel <pvorel@suse.cz>
To: Minchan Kim <minchan@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Sergey Senozhatsky <senozhatsky@chromium.org>,
ltp@lists.linux.it, linux-kselftest@vger.kernel.org,
Nitin Gupta <ngupta@vflare.org>
Subject: Re: [LTP] [PATCH 0/1] Possible bug in zram on ppc64le on vfat
Date: Fri, 11 Nov 2022 10:29:28 +0100 [thread overview]
Message-ID: <Y24V+AUuivt1F/Kw@pevik> (raw)
In-Reply-To: <Y22DiF5Q5EDUIrZE@google.com>
> 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.
I suppose you don't have ppc64le bare metal machine, thus you run on x86_64.
One way would be to install on host qemu-system-ppc64, download iso image of any
distro which supports ppc64le and install it with virt-manager (which would fill
necessary qemu params).
Other way, which I often use is to compile system with Buildroot distribution.
You can clone my Buildroot distro fork, branch debug/zram [1].
I put there in 3 commits my configuration.
I added 0001-zram-Debug-mm_stat_show.patch [2] on the top of 6.0.7 with little debugging.
What is now only needed is to 1) install on host qemu-system-ppc64
(speedup build + Buildroot is configured not to compile qemu-system-ppc64),
then:
$ make # takes time
$ ./output/images/start-qemu.sh serial-only
When I have ppc64le host with enough space, I often use rapido [3],
but that crashed stable kernel (another story which I'll report soon).
Hope that helps.
Kind regards,
Petr
[1] https://github.com/pevik/buildroot/commits/debug/zram
[2] https://github.com/pevik/buildroot/blob/debug/zram/0001-zram-Debug-mm_stat_show.patch
[3] https://github.com/rapido-linux/rapido
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-11-11 9:29 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 19:11 [PATCH 0/1] Possible bug in zram on ppc64le on vfat Petr Vorel
2022-11-07 19:11 ` [LTP] " Petr Vorel
2022-11-07 19:11 ` [PATCH 1/1] zram01.sh: Workaround division by 0 on vfat on ppc64le Petr Vorel
2022-11-07 19:11 ` [LTP] " Petr Vorel
2022-11-21 7:14 ` Li Wang
2022-11-21 8:59 ` Petr Vorel
2022-11-21 8:59 ` Petr Vorel
2023-09-18 9:38 ` Richard Palethorpe
2022-11-07 21:25 ` [PATCH 0/1] Possible bug in zram on ppc64le on vfat Minchan Kim
2022-11-07 21:25 ` [LTP] " Minchan Kim
2022-11-07 21:47 ` Petr Vorel
2022-11-07 21:47 ` [LTP] " Petr Vorel
2022-11-07 22:42 ` Petr Vorel
2022-11-07 22:42 ` [LTP] " Petr Vorel
2022-11-08 1:05 ` Sergey Senozhatsky
2022-11-08 1:05 ` [LTP] " Sergey Senozhatsky
2022-11-09 22:08 ` Petr Vorel
2022-11-09 22:08 ` [LTP] " Petr Vorel
2022-11-10 23:04 ` Minchan Kim
2022-11-10 23:04 ` [LTP] " Minchan Kim
2022-11-11 9:29 ` Petr Vorel [this message]
2022-11-11 9:29 ` Petr Vorel
2022-11-10 14:29 ` Martin Doucha
2022-11-10 14:29 ` [LTP] " Martin Doucha
2022-11-11 0:48 ` Sergey Senozhatsky
2022-11-11 0:48 ` [LTP] " Sergey Senozhatsky
2022-11-21 9:41 ` Petr Vorel
2022-11-21 9:41 ` [LTP] " Petr Vorel
2022-11-22 14:56 ` Martin Doucha
2022-11-22 14:56 ` [LTP] " Martin Doucha
2022-11-22 15:07 ` Petr Vorel
2022-11-22 15:07 ` [LTP] " Petr Vorel
2022-11-29 4:38 ` Sergey Senozhatsky
2022-11-29 4:38 ` [LTP] " Sergey Senozhatsky
2023-05-02 15:23 ` Martin Doucha
2023-05-02 15:23 ` [LTP] " Martin Doucha
2022-11-11 9:18 ` Petr Vorel
2022-11-11 9:18 ` [LTP] " Petr Vorel
2023-08-04 6:37 ` Ian Wienand
2023-08-04 6:37 ` [LTP] " Ian Wienand
2023-08-07 4:44 ` Ian Wienand
2023-08-07 4:44 ` [LTP] " Ian Wienand
2023-08-07 5:19 ` Sergey Senozhatsky
2023-08-07 5:19 ` [LTP] " Sergey Senozhatsky
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=Y24V+AUuivt1F/Kw@pevik \
--to=pvorel@suse.cz \
--cc=axboe@kernel.dk \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=mdoucha@suse.cz \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=senozhatsky@chromium.org \
--cc=xuyang2018.jy@fujitsu.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.