From: Conor Dooley <conor@kernel.org>
To: Song Shuai <songshuaishuai@tinylab.org>
Cc: alexghiti <alexghiti@rivosinc.com>, robh <robh@kernel.org>,
ajones <ajones@ventanamicro.com>, anup <anup@brainfault.org>,
palmer <palmer@rivosinc.com>,
"jeeheng.sia" <jeeheng.sia@starfivetech.com>,
"leyfoon.tan" <leyfoon.tan@starfivetech.com>,
"mason.huo" <mason.huo@starfivetech.com>,
"paul.walmsley" <paul.walmsley@sifive.com>,
"conor.dooley" <conor.dooley@microchip.com>,
guoren <guoren@kernel.org>,
linux-riscv <linux-riscv@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Bug report: kernel paniced while booting
Date: Mon, 5 Jun 2023 11:58:57 +0100 [thread overview]
Message-ID: <20230605-catnip-gallery-c20cc203b186@spud> (raw)
In-Reply-To: <tencent_7C3B580B47C1B17C16488EC1@qq.com>
[-- Attachment #1.1: Type: text/plain, Size: 1040 bytes --]
On Mon, Jun 05, 2023 at 10:52:14AM +0000, Song Shuai wrote:
> This report is not identical to my prior report -- "kernel paniced when system hibernates" [1], but both of them
> are closely related with the commit (3335068f8721 "riscv: Use PUD/P4D/PGD pages for the linear mapping").
>
> With this commit, hibernation is trapped with "access fault" while accessing the PMP-protected regions (mmode_resv0@80000000)
> from OpenSbi (BTW, hibernation is marked as nonportable by Conor[2]).
Just to be clear, you enabled NONPORTABLE & hibernation, and then
hibernating panicked for you on a system that uses standard OpenSBI?
This is the existing, known, issue and not something you are trying to
report as a new problem here, right?
(Sorry, I am a bit slow today)
Cheers,
Conor.
> In this report, efi_init handoffs the memory mapping from Boot Services to memblock where reserves mmode_resv0@80000000,
> so there is no "access fault" but "page fault".
>
> And reverting commit 3335068f8721 indeed fixed this panic.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-06-05 10:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 10:52 Bug report: kernel paniced while booting Song Shuai
2023-06-05 10:58 ` Conor Dooley [this message]
2023-06-05 14:25 ` Alexandre Ghiti
2023-06-05 15:12 ` Sunil V L
2023-06-05 20:55 ` Atish Patra
2023-06-06 0:48 ` Icenowy Zheng
2023-06-06 2:29 ` Jessica Clarke
2023-06-06 7:20 ` Alexandre Ghiti
2023-06-06 9:01 ` Sunil V L
2023-06-06 11:50 ` Alexandre Ghiti
2023-06-05 21:42 ` Jessica Clarke
2023-06-06 6:40 ` Sunil V L
2023-06-06 7:25 ` Alexandre Ghiti
2023-06-06 18:21 ` Atish Patra
2023-06-06 10:04 ` Song Shuai
2023-06-06 11:46 ` Alexandre Ghiti
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=20230605-catnip-gallery-c20cc203b186@spud \
--to=conor@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=alexghiti@rivosinc.com \
--cc=anup@brainfault.org \
--cc=conor.dooley@microchip.com \
--cc=guoren@kernel.org \
--cc=jeeheng.sia@starfivetech.com \
--cc=leyfoon.tan@starfivetech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mason.huo@starfivetech.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=songshuaishuai@tinylab.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