[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9e2214b1-999d-90cf-a5c2-2dbb5a2eadd4@canonical.com>
Date: Tue, 29 Jun 2021 20:28:02 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
To: Josef Bacik <josef@...icpanda.com>, Chris Mason <clm@...com>,
David Sterba <dsterba@...e.com>, linux-btrfs@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"kernel-team@...ts.ubuntu.com" <kernel-team@...ts.ubuntu.com>,
"ltp@...ts.linux.it" <ltp@...ts.linux.it>,
Qu Wenruo <wqu@...e.com>, Filipe Manana <fdmanana@...e.com>
Subject: Re: [BUG] btrfs potential failure on 32 core LTP test (fallocate05)
On 29/06/2021 20:06, Krzysztof Kozlowski wrote:
> Minor update - it's not only Azure's. AWS m5.8xlarge and m5.16xlarge (32
> and 64 cores) fail similarly. I'll try later also QEMU machines with
> different amount of CPUs.
>
Test on QEMU machine with 31 CPUs passes. With 32 CPUs - failure as
reported.
dmesg is empty - no error around this.
Maybe something with per-cpu variables?
Best regards,
Krzysztof
Powered by blists - more mailing lists