From: "Luck, Tony" <tony.luck@intel.com>
To: David Hildenbrand <david@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Yazen Ghannam <yazen.ghannam@amd.com>,
Miaohe Lin <linmiaohe@huawei.com>,
Naoya Horiguchi <naoya.horiguchi@nec.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: Machine check recovery broken in v6.9-rc1
Date: Fri, 5 Apr 2024 15:05:17 +0000 [thread overview]
Message-ID: <SJ1PR11MB6083AB3E55B7DE0D3FBE185EFC032@SJ1PR11MB6083.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1e943439-6044-4aa4-8c41-747e9e4dca27@redhat.com>
>> kernel BUG at include/linux/swapops.h:119
>>
>> 117 static inline unsigned long swp_offset_pfn(swp_entry_t entry)
>> 118 {
>> 119 VM_BUG_ON(!is_pfn_swap_entry(entry));
>> 120 return swp_offset(entry) & SWP_PFN_MASK;
>> 121 }
>>
>
> Do you have the full backtrace?
It's very garbled because multiple CPUs seem to be logging to the console together.
I've also got some more details.
1) Problems with recovery go back further than v6.8. Still looking to pin down where it started.
v6.0 seems good (can run hundreds of injections + consumptions).
2) It's connected to a BIOS setting that enables APEI logging. If I disable that, current
kernels don't have problems. v6.0 runs OK with this setting on or off.
I'm bisecting to find where the APEI issue begins.
-Tony
next prev parent reply other threads:[~2024-04-05 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 22:05 Tony Luck
2024-04-04 23:39 ` Tony Luck
2024-04-05 7:19 ` David Hildenbrand
2024-04-05 15:05 ` Luck, Tony [this message]
2024-04-05 23:58 ` Tony Luck
2024-04-06 2:18 ` Oscar Salvador
2024-04-06 3:54 ` Oscar Salvador
2024-04-06 4:13 ` Oscar Salvador
2024-04-07 0:08 ` Luck, Tony
2024-04-07 3:59 ` Miaohe Lin
2024-04-07 4:51 ` Oscar Salvador
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=SJ1PR11MB6083AB3E55B7DE0D3FBE185EFC032@SJ1PR11MB6083.namprd11.prod.outlook.com \
--to=tony.luck@intel.com \
--cc=bp@alien8.de \
--cc=david@redhat.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=yazen.ghannam@amd.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