From: "Luck, Tony" <tony.luck@intel.com>
To: linux-mm@kvack.org
Cc: shy828301@gmail.com, naoya.horiguchi@nec.com,
mike.kravetz@oracle.com, bp@alien8.de, linmiaohe@huawei.com,
akpm@linux-foundation.org
Subject: unhandlable pages
Date: Mon, 21 Mar 2022 10:17:29 -0700 [thread overview]
Message-ID: <YjizKd4scejFi6fl@agluck-desk3.sc.intel.com> (raw)
Validation folks are seeing this on a v5.16 kernel. I don't
see any changes in v5.17 that look like they address it.
Mar 04 14:05:05 JF5300-07B181T kernel: page:00000000696b0b6a refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x195cda44
Mar 04 14:05:05 JF5300-07B181T kernel: flags: 0x57ffffc0801000(reserved|hwpoison|node=1|zone=2|lastcpupid=0x1fffff)
Mar 04 14:05:05 JF5300-07B181T kernel: raw: 0057ffffc0801000 ffff6ea817369108 ffff6ea817369108 0000000000000000
Mar 04 14:05:05 JF5300-07B181T kernel: raw: 0000000000000000 0000000000000000 00000001ffffffff 0000000000000000
Mar 04 14:05:05 JF5300-07B181T kernel: page dumped because: hwpoison: unhandlable page
Mar 04 14:05:05 JF5300-07B181T kernel: Memory failure: 0x195cda44: recovery action for unknown page: Ignored
Som debugging shows this is an anon page (expected ... that's the
type of page where the error was injected. They see shake_page()
called three times, but it doesn't change anything, so the page
is reported as unhandlable.
-Tony
next reply other threads:[~2022-03-21 17:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 17:17 Luck, Tony [this message]
2022-03-21 17:21 ` Matthew Wilcox
2022-03-21 17:28 ` Luck, Tony
2022-03-21 17:32 ` Matthew Wilcox
2022-03-21 21:07 ` Yang Shi
2022-03-21 21:19 ` Luck, Tony
2022-03-22 0:10 ` Jane Chu
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=YjizKd4scejFi6fl@agluck-desk3.sc.intel.com \
--to=tony.luck@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=linmiaohe@huawei.com \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=naoya.horiguchi@nec.com \
--cc=shy828301@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