From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: "open list:MIPS" <linux-mips@vger.kernel.org>
Subject: Re: Loongson64 and huge pages
Date: Wed, 8 Dec 2021 12:50:30 +0100 [thread overview]
Message-ID: <20211208115030.GA9868@alpha.franken.de> (raw)
In-Reply-To: <CAAhV-H6tWyiZCtZXf_57-va9J8C+Roy5bgKJVc0=ATRrHV9Mtw@mail.gmail.com>
On Wed, Dec 08, 2021 at 09:56:50AM +0800, Huacai Chen wrote:
> Hi, Thomas,
>
> On Wed, Dec 8, 2021 at 8:59 AM Thomas Bogendoerfer
> <tsbogend@alpha.franken.de> wrote:
> >
> > Hi,
> >
> > [ 11.647401] CPU 3 Unable to handle kernel paging request at virtual address 0000000558005801, epc == ffffffff80232838, ra == ffffffff802327ac
> > [ 11.660049] Oops[#1]:
> > [ 11.662303] CPU: 3 PID: 348 Comm: libvirtd Not tainted 5.16.0-rc3+ #140
> > [ 11.668877] Hardware name: Lemote LEMOTE-LS3A4000-7A1000-1w-V0.1-pc/LEMOTE-LS3A4000-7A1000-1w-V01-pc, BIOS Kunlun-A1901-V4.1.4 04/20/2020
> > [ 11.929428] note: libvirtd[348] exited with preempt_count 1
> [..]
> >
> > is this a known issue ? If I disabled TRANSPARENT_HUGE_PAGE system
> > works.
> Have you tried some older kernels, such as 5.10/5.15? I have seen that
> some MM-related patches be merged in MIPS tree in recent releases, and
> maybe this bug is caused by them.
not yet, as it has worked, I'm going to bisect it.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2021-12-08 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 16:26 Loongson64 and huge pages Thomas Bogendoerfer
2021-12-08 1:56 ` Huacai Chen
2021-12-08 11:50 ` Thomas Bogendoerfer [this message]
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=20211208115030.GA9868@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=chenhuacai@kernel.org \
--cc=linux-mips@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