[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <277CDE7C-7ED8-4840-9C30-533C9327B028@gmail.com>
Date: Sat, 31 Aug 2024 11:41:05 +0200
From: Piotr Oniszczuk <piotr.oniszczuk@...il.com>
To: Yosry Ahmed <yosryahmed@...gle.com>
Cc: Pedro Falcato <pedro.falcato@...il.com>,
Nhat Pham <nphamcs@...il.com>,
Matthew Wilcox <willy@...radead.org>,
Linux regressions mailing list <regressions@...ts.linux.dev>,
LKML <linux-kernel@...r.kernel.org>,
Johannes Weiner <hannes@...xchg.org>,
Linux-MM <linux-mm@...ck.org>
Subject: Re: [regression] oops on heavy compilations ("kernel BUG at
mm/zswap.c:1005!" and "Oops: invalid opcode: 0000")
> Wiadomość napisana przez Yosry Ahmed <yosryahmed@...gle.com> w dniu 29.08.2024, o godz. 23:54:
>
> I also noticed that you are using z3fold as the zpool. Is the problem
> reproducible with zsmalloc? I wouldn't be surprised if there's a
> z3fold bug somewhere.
>
Hmm - yesterday i recompiled 6.9.12 with zsmalloc and …. after 16h of continuous tests I can’t reproduce issue.
With zsmalloc 6.9.12 looks to me like stable.
With this - what will be your advice to move forward?
Is there any possibility/way to avoid bisecting? (due limited time from my side)
Powered by blists - more mailing lists