qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: Looking for advise on debugging a non-boot kernel on qemu-system-sh4
Date: Thu, 21 Oct 2021 15:10:40 +0200	[thread overview]
Message-ID: <541c421b-d4a0-be8c-7d5e-ec204c7dba9f@redhat.com> (raw)
In-Reply-To: <4882e4cc-6754-1c8a-a8ae-a2ceeca115fb@physik.fu-berlin.de>

On 21/10/2021 11.49, John Paul Adrian Glaubitz wrote:
> Hello!
> 
> I'm regularly building debian-installer packages for Debian's unofficial ports
> which includes sh4 among others. The kernel package and therefore the installer
> package contains a kernel for the SH7751R machine which is emulated by QEMU when
> choosing the "r2d" type.
> 
> Unfortunately, I have not yet been able to boot a current kernel on qemu-system-sh4,
> the screen remains blank and there are no error messages. Booting an older 2.6 kernel
> works just fine.
> 
> I'm using qemu-system-sh4 as follows:
> 
> $ qemu-system-sh4 -M r2d -kernel vmlinuz-2.6.32-5-sh7751r -initrd initrd.gz -hda debian.img \
>    -append "root=/dev/sda1 console=tty0 noiotrap"
> 
> The old 2.6 kernel from [1] boots fine while the current 5.14.x kernel from [2] does
> not produce any output.
> 
> Can anyone enlighten me what I might be missing?

I can't say much about very recent kernels, but FWIW, it was still working 
fine with kernel 4.9 in 2018, see:

  https://www.qemu-advent-calendar.org/2018/#day-9

In case it's just the video driver that is not working anymore, try:

  -append "console=ttySC1" -serial null -serial stdio

... that should hopefully redirect the kernel output to the serial console 
on stdio of the host terminal (at least it does so with the advent calendar 
image that I mentioned above).

  HTH,
   Thomas



      parent reply	other threads:[~2021-10-21 13:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-21  9:49 Looking for advise on debugging a non-boot kernel on qemu-system-sh4 John Paul Adrian Glaubitz
2021-10-21 12:12 ` BALATON Zoltan
2021-10-21 12:40   ` John Paul Adrian Glaubitz
2021-10-21 13:49     ` BALATON Zoltan
2021-10-21 15:07       ` John Paul Adrian Glaubitz
2021-10-22 21:06         ` BALATON Zoltan
2021-10-22 21:49           ` John Paul Adrian Glaubitz
2021-10-22 23:08             ` John Paul Adrian Glaubitz
2021-10-23  1:07               ` BALATON Zoltan
2021-10-23  1:12                 ` John Paul Adrian Glaubitz
2021-10-23 13:22                   ` BALATON Zoltan
2021-10-25 22:10                     ` John Paul Adrian Glaubitz
2021-10-25 22:40                       ` BALATON Zoltan
2022-01-12 11:27                         ` John Paul Adrian Glaubitz
2022-01-12 14:44                           ` BALATON Zoltan
2021-10-21 13:10 ` Thomas Huth [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=541c421b-d4a0-be8c-7d5e-ec204c7dba9f@redhat.com \
    --to=thuth@redhat.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).