From: Matthew Wilcox <willy@infradead.org>
To: dianlujitao@gmail.com
Cc: Bagas Sanjaya <bagasdotme@gmail.com>, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux btrfs <linux-btrfs@vger.kernel.org>,
Linux Filesystem Development <linux-fsdevel@vger.kernel.org>
Subject: Re: Fwd: kernel bug when performing heavy IO operations
Date: Wed, 27 Sep 2023 08:19:49 +0100 [thread overview]
Message-ID: <ZRPXlfGFWiCNZ6sh@casper.infradead.org> (raw)
In-Reply-To: <b290c417-de1b-4af8-9f5e-133abb79580d@gmail.com>
On Wed, Sep 27, 2023 at 01:36:52PM +0800, dianlujitao@gmail.com wrote:
> Hello, I got some logs with 6.5.4 kernel from the official linux package of
> Arch, no zen patches this time. Full dmesg is uploaded to
> https://fars.ee/F1yM and below is a small snippet for your convenience, from
> which PG_offline is no longer set:
>
> [177850.039441] BUG: Bad page map in process ld.lld pte:8000000edacc4025
> pmd:147f96067
> [177850.039454] page:000000007415dd6c refcount:22 mapcount:-237
> mapping:00000000b0c37ca6 index:0x1075 pfn:0xedacc4
It still looks like memory corruption to me. If you go back to an older
kernel (say 5.10 or 5.15) does the problem go away? It's not really
dispositive either way, since a newer kernel might drive the hardware
closer to the edge, but it might give some clue.
next prev parent reply other threads:[~2023-09-27 7:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 3:20 Fwd: kernel bug when performing heavy IO operations Bagas Sanjaya
2023-08-27 3:45 ` Matthew Wilcox
[not found] ` <7d8b4679-5cd5-4ba1-9996-1a239f7cb1c5@gmail.com>
2023-08-27 11:54 ` Matthew Wilcox
2023-09-27 5:36 ` dianlujitao
2023-09-27 7:19 ` Matthew Wilcox [this message]
2023-10-08 13:35 ` dianlujitao
2023-10-08 14:07 ` Bagas Sanjaya
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=ZRPXlfGFWiCNZ6sh@casper.infradead.org \
--to=willy@infradead.org \
--cc=bagasdotme@gmail.com \
--cc=clm@fb.com \
--cc=dianlujitao@gmail.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).