From: Nhat Pham <nphamcs@gmail.com>
To: Pedro Falcato <pedro.falcato@gmail.com>
Cc: mm <linux-mm@kvack.org>,
Linux Regressions <regressions@lists.linux.dev>,
Johannes Weiner <hannes@cmpxchg.org>,
Yosry Ahmed <yosryahmed@google.com>,
Chengming Zhou <chengming.zhou@linux.dev>,
Christian Heusel <christian@heusel.eu>,
yshuiv7@gmail.com
Subject: Re: zswap_writeback_entry crashes in 6.9.5
Date: Fri, 19 Jul 2024 13:47:23 -0700 [thread overview]
Message-ID: <CAKEwX=OOCc0nxheE3yTJgTR0K7XXL2_TcKp7jt_zt4NbDLv8Dg@mail.gmail.com> (raw)
In-Reply-To: <CAKbZUD3yM0kjbeqdscG3gVhoMz5hNZjCxV9xSQepCEpL=qGa5w@mail.gmail.com>
On Fri, Jul 19, 2024 at 11:57 AM Pedro Falcato <pedro.falcato@gmail.com> wrote:
>
> On Mon, Jul 1, 2024 at 2:07 AM Nhat Pham <nphamcs@gmail.com> wrote:
> >
> > On Sun, Jun 30, 2024 at 10:58 AM Pedro Falcato <pedro.falcato@gmail.com> wrote:
> > >
> > > Hi everyone,
> >
> > Hi Pedro,
> >
>
> I have a separate theory. I also run the NVIDIA proprietary drivers.
> slabinfo -a shows us:
> [...]
> :0000080 <- zswap_entry Acpi-Parse kernfs_iattrs_cache
> uvm_tools_replay_data_t Acpi-State audit_tree_mark
> [...]
>
> See the uvm_tools_replay_data_t there? Yeah, it's entirely possible
> some random nvidia.ko bug has been corrupting zswap_entry from time to
> time (which explains why e.g the big server people have not seen
> this).
Oh this is fascinating. I would never have guessed this. Thanks for
doing the investigation!
> I'm not sure if Yuxuan is running the same driver, but their kernel is
> also proprietary-tainted.
>
> As such I'll refrain from posting more about this or similar bugs
> until I can get a guarantee it happens with a non-tainted kernel
> (fwiw, I have not seen crashes for 2 weeks or so, hopefully this issue
> is fixed).
Crossing my fingers :)
>
> Again, sorry for not checking the taint before posting this, and thank
> you for your time :)
No worries at all :) Let me know if there are new developments
regarding this issue, or if you are able to confirm one way or another
:)
next prev parent reply other threads:[~2024-07-19 20:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 17:58 Pedro Falcato
2024-07-01 1:07 ` Nhat Pham
2024-07-19 18:57 ` Pedro Falcato
2024-07-19 20:47 ` Nhat Pham [this message]
2024-07-01 3:44 ` Chengming Zhou
2024-07-02 0:33 ` Builder
2024-07-02 15:28 ` Nhat Pham
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='CAKEwX=OOCc0nxheE3yTJgTR0K7XXL2_TcKp7jt_zt4NbDLv8Dg@mail.gmail.com' \
--to=nphamcs@gmail.com \
--cc=chengming.zhou@linux.dev \
--cc=christian@heusel.eu \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=pedro.falcato@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=yosryahmed@google.com \
--cc=yshuiv7@gmail.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