From: dianlujitao@gmail.com
To: Matthew Wilcox <willy@infradead.org>
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: Sun, 8 Oct 2023 21:35:58 +0800 [thread overview]
Message-ID: <162d90ab-e538-402e-90f1-304183bf6e76@gmail.com> (raw)
In-Reply-To: <ZRPXlfGFWiCNZ6sh@casper.infradead.org>
The problem does not occur with 6.1.56 lts kernel, not that old as you
expected.
在 2023/9/27 15:19, Matthew Wilcox 写道:
> 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-10-08 13:36 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
2023-10-08 13:35 ` dianlujitao [this message]
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=162d90ab-e538-402e-90f1-304183bf6e76@gmail.com \
--to=dianlujitao@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=clm@fb.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 \
--cc=willy@infradead.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).