From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Guenter Roeck <linux@roeck-us.net>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>, <linux-sh@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sh: Avoid using IRQ0 on SH3 and SH4
Date: Sat, 8 Jul 2023 23:55:52 +0300 [thread overview]
Message-ID: <941c0ebf-d55a-22f1-72d4-1397f44d3c3a@omp.ru> (raw)
In-Reply-To: <29ad9e3d1a83d03190626ba66b7d71c833776982.camel@physik.fu-berlin.de>
On 7/6/23 8:41 PM, John Paul Adrian Glaubitz wrote:
>> I tried rts7751r2dplus_defconfig with no modifications and the following minimized
>> qemu command line.
>>
>> qemu-system-sh4 -M r2d -kernel arch/sh/boot/zImage -serial null -serial stdio -nographic -monitor null
>>
>> This hangs after "heartbeat: version 0.1.2 loaded", so it doesn't
>> even get to the point where it would try to load a root file system.
>> After reverting this patch, I get
>> ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---
>> as expected.
>>
>> I tried with qemu version 6.2, 7.1, 7.2, and 8.0.
>
> I'm curios to hear what Geert and Sergey have to say.
Sorry for a late reaction, I was busy reviewing some PATA patches and a static analyzer
work here, at OMP...
> I hope we don't have to revert this :-(.
I think we should be able to find the root cause soon.
I prolly should learn Qemu some day... :-)
> Adrian
MBR, Sergey
next prev parent reply other threads:[~2023-07-08 20:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 13:57 [PATCH] sh: Avoid using IRQ0 on SH3 and SH4 Guenter Roeck
2023-07-06 14:01 ` John Paul Adrian Glaubitz
2023-07-06 15:51 ` Guenter Roeck
2023-07-08 20:35 ` Sergey Shtylyov
2023-07-08 20:43 ` Sergey Shtylyov
2023-07-06 15:39 ` Geert Uytterhoeven
2023-07-06 15:51 ` Guenter Roeck
2023-07-06 16:38 ` John Paul Adrian Glaubitz
2023-07-06 17:04 ` Guenter Roeck
2023-07-06 17:41 ` John Paul Adrian Glaubitz
2023-07-08 20:55 ` Sergey Shtylyov [this message]
2023-07-07 7:14 ` Geert Uytterhoeven
2023-07-07 8:48 ` Geert Uytterhoeven
2023-07-07 9:30 ` John Paul Adrian Glaubitz
2023-07-07 9:53 ` John Paul Adrian Glaubitz
2023-07-07 14:34 ` Guenter Roeck
[not found] ` <407492B8-5D9F-41BC-A696-24C421C69F49@physik.fu-berlin.de>
2023-07-07 15:30 ` Guenter Roeck
2023-07-08 20:52 ` Sergey Shtylyov
2023-07-08 22:06 ` Guenter Roeck
2023-07-08 23:13 ` John Paul Adrian Glaubitz
2023-07-09 0:28 ` Guenter Roeck
2023-07-12 8:12 ` David Laight
2023-07-12 8:15 ` John Paul Adrian Glaubitz
2023-07-12 8:20 ` Sergei Shtylyov
2023-07-12 8:24 ` David Laight
2023-07-12 15:38 ` Guenter Roeck
2023-07-12 15:51 ` John Paul Adrian Glaubitz
2023-07-12 16:22 ` Sergey Shtylyov
2023-07-12 16:25 ` Sergey Shtylyov
2023-07-08 13:26 ` Guenter Roeck
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=941c0ebf-d55a-22f1-72d4-1397f44d3c3a@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=ysato@users.sourceforge.jp \
/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