From: Piotr Oniszczuk <piotr.oniszczuk@gmail.com>
To: Nhat Pham <nphamcs@gmail.com>
Cc: Matthew Wilcox <willy@infradead.org>,
Linux regressions mailing list <regressions@lists.linux.dev>,
LKML <linux-kernel@vger.kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Yosry Ahmed <yosryahmed@google.com>,
Linux-MM <linux-mm@kvack.org>
Subject: Re: [regression] oops on heavy compilations ("kernel BUG at mm/zswap.c:1005!" and "Oops: invalid opcode: 0000")
Date: Fri, 23 Aug 2024 19:24:27 +0200 [thread overview]
Message-ID: <9793DBCA-13F4-4B47-AD57-12A62F7DD8DD@gmail.com> (raw)
In-Reply-To: <CAKEwX=N-10A=C_Cp_m8yxfeTigvmZp1v7TrphcrHuRkHJ8837g@mail.gmail.com>
> Wiadomość napisana przez Nhat Pham <nphamcs@gmail.com> w dniu 23.08.2024, o godz. 18:16:
>
> Have you tried with 6.9 yet? IIRC, there are two major changes to
> zswap architecture in recent versions.
No. But now building vanilla 6.9.12. Will install and see…
(This will take some time as catching issue needs days of compilation)
>
> 1. In 6.9, we range-partition zswap's rbtrees to reduce lock contention.
>
> 2. In 6.10, we replace zswap's rbtrees with xarrays.
>
> If 6.9 is fine, then the latter is the suspect, and vice versa. Of
> course, the minor changes are still suspect - but you get the idea :)
>
>>
>> btw: we can go with elimination strategy.
>> So what i need to change/disable to be closer to finding root cause?
>
> Could you let me know more about the setup? A couple things come to my mind:
>
> 1. zswap configs (allocator - is it zsmalloc? compressor?)
Well - I’m not using zswap.
[root@minimyth2-aarch64-next piotro]# swapon -s
Filename Type Size Used Priority
/dev/nvme0n1p3 partition 16776188 294164 -2
>
> 2. Is mTHP enabled? mTHP swapout was merged in 6.10, and there seems
I don’t have used config at the moment, but /sys/kernel/mm/transparent_hugepage in I see:
│/hugepages-1024kB
│/hugepages-128kB
│/hugepages-16kB
│/hugepages-2048kB
│/hugepages-256kB
│/hugepages-32kB
│/hugepages-512kB
│/hugepages-64kB
> to be some conflicts with zswap, but Yosry will know more about this
> than me...
>
> 3. Is there any proprietary driver etc.?
>
Only 2, both ryzen9 monitoring related:
https://github.com/leogx9r/ryzen_smu/commits/master
https://github.com/ocerman/zenpower/commits/master
next prev parent reply other threads:[~2024-08-23 17:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BD22A15A-9216-4FA0-82DF-C7BBF8EE642E@gmail.com>
2024-08-23 11:51 ` Linux regression tracking (Thorsten Leemhuis)
2024-08-23 12:12 ` Piotr Oniszczuk
2024-08-23 13:13 ` Matthew Wilcox
2024-08-23 14:35 ` Nhat Pham
2024-08-23 14:47 ` Matthew Wilcox
2024-08-23 16:07 ` Yosry Ahmed
2024-08-23 15:06 ` Piotr Oniszczuk
2024-08-23 16:16 ` Nhat Pham
2024-08-23 17:24 ` Piotr Oniszczuk [this message]
2024-08-23 18:06 ` Nhat Pham
2024-08-24 10:50 ` Piotr Oniszczuk
2024-08-25 5:55 ` Piotr Oniszczuk
2024-08-25 15:05 ` Pedro Falcato
2024-08-25 16:24 ` Piotr Oniszczuk
2024-08-27 18:48 ` Yosry Ahmed
2024-08-29 15:50 ` Piotr Oniszczuk
2024-08-29 21:54 ` Yosry Ahmed
2024-08-29 22:29 ` Matthew Wilcox
2024-08-29 22:53 ` Yosry Ahmed
2024-08-31 9:41 ` Piotr Oniszczuk
2024-08-31 17:23 ` Yosry Ahmed
2024-09-02 8:57 ` Piotr Oniszczuk
2024-09-03 17:49 ` Yosry Ahmed
2024-09-03 22:43 ` Nhat Pham
2024-09-04 23:36 ` Yosry Ahmed
2024-09-13 9:03 ` Tomáš Trnka
2024-09-13 17:39 ` Yosry Ahmed
[not found] ` <27594ee6-41dd-4951-b4cc-31577c9466db@amd.com>
2024-09-03 17:52 ` Yosry Ahmed
2024-08-23 18:42 ` Takero Funaki
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=9793DBCA-13F4-4B47-AD57-12A62F7DD8DD@gmail.com \
--to=piotr.oniszczuk@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=willy@infradead.org \
--cc=yosryahmed@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox