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

Bug#826173: Debian Testing/Unstable MIPS Installer Kernel Panic



Good call on the CPU. Here's what I was using to run it:

qemu-system-mips64 -M malta -kernel vmlinux-4.5.0-2-4kc-malta -initrd initrd.gz -hda hda.img -append root=/dev/ram console=ttyS0 -m 1G -nographic

After adding the -cpu option you mentioned it started up without issue.

Thanks!

Mike


On Sat, Jun 4, 2016 at 5:26 AM, Aurelien Jarno <aurelien@aurel32.net> wrote:
On 2016-06-03 19:03, Ben Hutchings wrote:
> Control: reassign -1 debian-installer 20160516+b1
>
> On Fri, 2016-06-03 at 08:48 +0000, Mattia Rizzolo wrote:
> > control: reassign -1 src:linux  4.5.4-1
> >
> > On Thu, Jun 02, 2016 at 07:13:04PM -0400, Mike wrote:
> > > Package: kernel
> >
> > this is not a valid package name.
> >
> > > Version: Testing
> >
> > and this is not a valid version....
> >
> > >
> > > I am working on installing Debian under a QEMU MIPS emulator. I was able to
> > > get the Debian Stable branch to install and run properly using this:
> > >
> > > http://ftp.de.debian.org/debian/dists/stable/main/installer-mips/current/images/malta/netboot/
> > >
> > > However, when I attempt to use unstable or testing, I receive a kernel
> > > panic immediately on boot for install. I cannot really give a package name
> > > because it appears there's a problem in the kernel or init somewhere.
> > >
> > > http://ftp.de.debian.org/debian/dists/unstable/main/installer-mips/current/images/malta/netboot/
> > >
> > > The error I get it as follows:
> > > [    2.463767] Kernel panic - not syncing: Attempted to kill init!
> > > exitcode=0x00000004
> > > [    2.463767]
> > > [    2.464725] ---[ end Kernel panic - not syncing: Attempted to kill init!
> > > exitcode=0x00000004
>
> That usually means something is wrong with the initrd.  So reassigning
> to the installer.

It would be interested to know which QEMU command you used to start this
image. Since the switch to GCC 5, the mips architecture requires a R2
CPU.

QEMU defaults emulating a R2 CPU in 32-bit mode, but a R1 CPU in 64-bit
mode. In the later case try to pass "-cpu 5KEf" to QEMU.

Aurelien

--
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net


Reply to: