[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#989020: marked as done (linux-image-5.9.0-5-sh7751r entirely fails to boot in qemu-system-sh4)

Your message dated Thu, 20 Feb 2025 13:39:19 +0100 (CET)
with message-id <20250220123919.2A586BE2EE7@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #989020,
regarding linux-image-5.9.0-5-sh7751r entirely fails to boot in qemu-system-sh4
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
989020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989020
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:linux
Version: 5.9.15-1
Severity: normal
X-Debbugs-Cc: rincebrain@gmail.com

Dear Maintainer,

On a lark, I decided to try and get a sh4 boot environment running. So I
tried downloading the oldest (2019-11-21, with vmlinuz-4.19.0-5-sh7751r) 
and newest (2021-04-17, with vmlinuz-5.9.0-5-sh7751r) debian-installer 
tarballs, and they both did the same thing in qemu - no serial output, no 
graphical output.

So I found https://people.debian.org/~aurel32/qemu/sh4/, and tried booting
that kernel and initrd with my qemu command, and that worked fine.

So next I tried a debootstrap --arch=sh4 sh4_chroot, chrooted in, installed
the kernel (linux-image-5.9.0-5-sh7751r), generated an initrd, partitioned
the disk image file I made before, mkfs.ext4, rsync -avx everything over,
try booting with the kernel+initrd from the chroot...same result.

The qemu line I used is:
qemu-system-sh4 -M r2d -serial null -serial mon:stdio -m 1024 -usb -usbdevice keyboard -kernel sh4_chroot/boot/vmlinuz-5.9.0-5-sh7751r -initrd sh4_chroot/boot/initrd.img-5.9.0-5-sh7751r -drive file=sh4_disk,format=raw -append "root=/dev/sda1 console=tty0 noiotrap" -vnc :30

The qemu version is 5.2+dfsg-9~bpo10+1.

It's certainly possible that I could be holding it wrong, and something has
changed between 2.6.32 and 4.19.0 that means I need a different command line,
but I'm kind of surprised if the same command doesn't at least produce
_some_ output, and unsurprisingly it's quite difficult to find documentation
on how to do this properly.

- Rich

-- Package-specific info:
** Kernel log: boot messages should be attached


-- System Information:
Debian Release: 11.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: sh4

Kernel: Linux 4.19.0-16-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=C.UTF-8 (charmap=/usr/bin/locale: Cannot set LC_MESSAGES to default locale: No such file or directory
/usr/bin/locale: Cannot set LC_ALL to default locale: No such file or directory
UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages linux-image-5.9.0-5-sh7751r depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.140
ii  kmod                                    28-1
ii  linux-base                              4.6

Versions of packages linux-image-5.9.0-5-sh7751r recommends:
ii  apparmor             2.13.6-10
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-5.9.0-5-sh7751r suggests:
pn  debian-kernel-handbook  <none>
pn  linux-doc-5.9           <none>

Versions of packages linux-image-5.9.0-5-sh7751r is related to:
pn  firmware-amd-graphics     <none>
pn  firmware-atheros          <none>
pn  firmware-bnx2             <none>
pn  firmware-bnx2x            <none>
pn  firmware-brcm80211        <none>
pn  firmware-cavium           <none>
pn  firmware-intel-sound      <none>
pn  firmware-intelwimax       <none>
pn  firmware-ipw2x00          <none>
pn  firmware-ivtv             <none>
pn  firmware-iwlwifi          <none>
pn  firmware-libertas         <none>
pn  firmware-linux-nonfree    <none>
pn  firmware-misc-nonfree     <none>
pn  firmware-myricom          <none>
pn  firmware-netxen           <none>
pn  firmware-qlogic           <none>
pn  firmware-realtek          <none>
pn  firmware-samsung          <none>
pn  firmware-siano            <none>
pn  firmware-ti-connectivity  <none>
pn  xen-hypervisor            <none>

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: