From: Conor Dooley <conor.dooley@microchip.com>
To: Song Shuai <suagrfillet@gmail.com>
Cc: <alexghiti@rivosinc.com>, <robh@kernel.org>,
Andrew Jones <ajones@ventanamicro.com>, <anup@brainfault.org>,
<palmer@rivosinc.com>, <jeeheng.sia@starfivetech.com>,
<leyfoon.tan@starfivetech.com>, <mason.huo@starfivetech.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Guo Ren <guoren@kernel.org>, <linux-riscv@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <regressions@lists.linux.dev>
Subject: Re: Bug report: kernel paniced when system hibernates
Date: Tue, 16 May 2023 12:35:55 +0100 [thread overview]
Message-ID: <20230516-figure-vanity-d8b671ca1aa0@wendy> (raw)
In-Reply-To: <CAAYs2=gQvkhTeioMmqRDVGjdtNF_vhB+vm_1dHJxPNi75YDQ_Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 416 bytes --]
On Tue, May 16, 2023 at 09:24:07AM +0000, Song Shuai wrote:
> Description of problem:
>
> The latest hibernation support[1] of RISC-V Linux produced a kernel panic.
> The entire log has been posted at this link: https://termbin.com/sphl .
Since the reporting is a bit scattered between here and the sw-dev list:
#regzbot introduced: v6.4-rc1.. ^
#regzbot title: kernel accessing opensbi reserved memory
[-- 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
prev parent reply other threads:[~2023-05-16 11:36 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 9:24 Bug report: kernel paniced when system hibernates Song Shuai
2023-05-16 9:55 ` JeeHeng Sia
2023-05-16 11:14 ` Alexandre Ghiti
2023-05-16 11:27 ` JeeHeng Sia
2023-05-17 8:33 ` Alexandre Ghiti
2023-05-18 4:06 ` JeeHeng Sia
2023-05-16 11:12 ` Alexandre Ghiti
2023-05-17 8:58 ` Alexandre Ghiti
2023-05-17 11:05 ` Song Shuai
[not found] ` <CAHVXubgjgMvFV0MOABbtKr+2TH85+0kow7wOrjxFCP5iXt1saQ@mail.gmail.com>
2023-05-17 14:42 ` Fwd: " Alexandre Ghiti
2023-05-18 1:29 ` JeeHeng Sia
2023-05-18 9:13 ` Alexandre Ghiti
2023-05-18 3:29 ` Song Shuai
2023-05-18 11:54 ` Alexandre Ghiti
2023-05-17 11:27 ` Conor Dooley
2023-05-17 14:55 ` Alexandre Ghiti
2023-05-18 6:53 ` Anup Patel
2023-05-18 7:59 ` Conor Dooley
2023-05-18 8:41 ` Alexandre Ghiti
2023-05-18 10:35 ` Conor Dooley
2023-05-18 11:58 ` Alexandre Ghiti
2023-05-24 23:53 ` Atish Patra
2023-05-25 12:55 ` Conor Dooley
2023-05-18 12:21 ` JeeHeng Sia
2023-05-18 12:09 ` Alexandre Ghiti
2023-05-18 14:04 ` Anup Patel
2023-05-24 13:49 ` Conor Dooley
2023-05-24 13:57 ` Alexandre Ghiti
2023-05-24 15:59 ` Conor Dooley
2023-05-24 23:45 ` Atish Patra
2023-05-25 13:08 ` Conor Dooley
2023-05-25 13:21 ` Anup Patel
2023-05-25 13:37 ` Conor Dooley
2023-05-25 13:43 ` Anup Patel
2023-05-25 13:55 ` Conor Dooley
2023-05-25 13:59 ` Anup Patel
2023-05-25 14:20 ` Conor Dooley
2023-05-25 17:39 ` Atish Patra
2023-05-25 18:22 ` Conor Dooley
2023-05-25 18:37 ` Atish Patra
2023-05-25 18:39 ` Conor Dooley
2023-05-25 20:06 ` Atish Patra
2023-05-25 21:24 ` Conor Dooley
2023-05-26 13:14 ` Alexandre Ghiti
2023-05-26 14:59 ` Conor Dooley
2023-05-26 15:12 ` Alexandre Ghiti
2023-05-26 15:17 ` Anup Patel
2023-05-26 15:22 ` Alexandre Ghiti
2023-05-26 18:48 ` Atish Patra
2023-05-16 11:35 ` Conor Dooley [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=20230516-figure-vanity-d8b671ca1aa0@wendy \
--to=conor.dooley@microchip.com \
--cc=ajones@ventanamicro.com \
--cc=alexghiti@rivosinc.com \
--cc=anup@brainfault.org \
--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=regressions@lists.linux.dev \
--cc=robh@kernel.org \
--cc=suagrfillet@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