linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Yu Zhao" <yuzhao@google.com>,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Cc: Linux-MM <linux-mm@kvack.org>
Subject: Re: MCEs on MIPS: multiple matching TLB entries
Date: Sun, 30 Jun 2024 03:22:05 +0100	[thread overview]
Message-ID: <b8abe9ab-9fc9-4117-b4c4-728c99f46d88@app.fastmail.com> (raw)
In-Reply-To: <CAOUHufac==iT7BD9_eWERNcpazV6KEaR3qupR9v5SrzC4GXYcg@mail.gmail.com>



在2024年6月28日六月 下午6:57,Yu Zhao写道:
> Hi,
>
> OpenWrt folks ran into MCEs caused by multiple matching TLB entries
> [1], after they updated their kernel from v6.1 to v6.6.
>
> I reported similar crashes previously [2], on v6.4. So they asked me
> whether I'm aware of a fix from the mainline, which I am not.
> on
> I took a quick look from the MM's POV and found nothing obviously
> wrong. I'm hoping they have better luck with the MIPS experts.

Hi Yu,

I never hit such problem on my (non-bcm) 74Kc systems.

However a quick glance suggested it may be related to Wired TLB entries
on your platform.

Both duplicated TLB entries, Index 2 and 3, are all below "Wired" setting,
which means they are not managed by mm, but platform code.

Thanks
- Jiaxun

>
> Thanks!
>
> [1] https://github.com/openwrt/openwrt/pull/15635
> [2] 
> https://lore.kernel.org/linux-mm/CAOUHufbAjZd4Mxkio9OGct-TZ=L0QRG+_6Xa7atQVFN_4ez86w@mail.gmail.com/
>
-- 
- Jiaxun


  reply	other threads:[~2024-06-30  2:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28 17:57 Yu Zhao
2024-06-30  2:22 ` Jiaxun Yang [this message]
2024-06-30  3:01   ` Jiaxun Yang
2024-06-30 17:25     ` Jiaxun Yang
2024-06-30 18:23       ` Yu Zhao
2024-07-03  5:13         ` Jiaxun Yang

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=b8abe9ab-9fc9-4117-b4c4-728c99f46d88@app.fastmail.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=yuzhao@google.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