qemu-devel
[Top][All Lists]
Advanced

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

[Qemu-devel] [Bug 1278977] Re: qemu-system-sparc64 crash when initializi


From: wbx
Subject: [Qemu-devel] [Bug 1278977] Re: qemu-system-sparc64 crash when initializing disk
Date: Sat, 23 Aug 2014 22:53:17 -0000

Hi Mark,

I tried the cmd646 driver again and it works fine now. I can even extract the 
perl code without problems.
No deadlock, even with a high load of the host system.

When switching back to virtio using following command:
qemu-system-sparc64 -M sun4u -nographic -net nic,model=virtio -net user -drive 
file=qemu-sparc64.img,if=virtio,index=0 -kernel 
/home/wbx/sparc64/firmware/qemu-sparc64_glibc/qemu-sparc64-archive-kernel 
qemu-sparc64.img
The deadlock can be reproduced again using Qemu 2.1.
Interesting is that I can not reproduce the deadlock using 
qemu-system--aarch64, which uses virtio, too.
But for qemu-system-aarch64 I need following command:
qemu-system-aarch64 -nographic -M virt -cpu cortex-a57 -smp 1 -netdev 
user,id=eth0 -device virtio-net-device,netdev=eth0 -device 
virtio-blk-device,drive=vda -drive file=qemu-aarch64.img,if=none,id=vda -kernel 
/home/wbx/aarch64/firmware/qemu-aarch64_glibc/qemu-aarch64-archive-kernel 
qemu-aarch64.img

The sparc64 system emulator does not work with this syntax and I get following 
warning with the other one:
qemu-system-sparc64: unable to init msix vectors to 3
qemu-system-sparc64: -drive file=qemu-sparc64.img,if=virtio,index=0: unable to 
init msix vectors to 2

Hmm, I think I haven't seen this messages with older Qemu versions. Both
are using virtio, why the deadlock only occurs with sparc64?

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1278977

Title:
  qemu-system-sparc64 crash when initializing disk

Status in QEMU:
  New

Bug description:
  Hi,

  I try to boot up Linux for SPARC64 in qemu-system-sparc64 (qemu 1.7.0). A 
self compiled kernel with initramfs as piggyback boots up fine.
  (http://www.openadk.org/qemu-sparc64-initramfs-piggyback-kernel)
  When trying to use a disk image I get following trace:
  qemu-system-sparc64 -nographic -kernel 
/home/wbx/openadk/bin/qemu_sparc64_eglibc/qemu-sparc64-archive-kernel 
qemu-sparc64.img -append "root=/dev/sda1" 
  [   43.520705] ata1.00: ATA-7: QEMU HARDDISK, 1.7.0, max UDMA/100
  [   43.792734] ata1.00: 1048576 sectors, multi 16: LBA48 
  [   44.100768] ata1.00: configured for UDMA/33
  [   44.316791] scsi 0:0:0:0: Direct-Access     ATA      QEMU HARDDISK    1.7. 
PQ: 0 ANSI: 5
  [   44.724835] sd 0:0:0:0: [sda] 1048576 512-byte logical blocks: (536 MB/512 
MiB)
  [   45.172883] ata2.00: ATAPI: QEMU DVD-ROM, 1.7.0, max UDMA/100
  [   45.508920] ata2.00: configured for UDMA/33
  [   45.752946] scsi 1:0:0:0: CD-ROM            QEMU     QEMU DVD-ROM     1.7. 
PQ: 0 ANSI: 5
  [   46.309006] sd 0:0:0:0: [sda] Write Protect is off
  [   46.737053] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
  qemu: fatal: Trap 0x0032 while trap level (5) >= MAXTL (5), Error state
  pc: 00000000004055dc  npc: 00000000004055e0
  %g0-3: 0000000000000000 0000000000000200 fffff80006a3f170 0000000000000200
  %g4-7: f500046400000000 0000000000000000 fffff80006a3c000 f500000000000000
  %o0-3: fffff80006a10140 fffff80006a10160 fffff80006900010 0000000006a6c000 
  %o4-7: 0000000000000002 00000000000003e7 fffff80006a3e1c1 0000000000593988 
  %l0-3: 000000000000ffff 0000000000ff0000 0000000000002000 0000000000000001 
  %l4-7: 0000000000000000 fffff80006a0d980 0000000000000001 00000000c0004000 
  %i0-3: 0000000000000000 000000000000ff00 0000000000010000 0000000000000001 
  %i4-7: fffff80006a11d50 fffff80006a10000 fffff80006a3e271 0000000000582444 
  %f00:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
  %f08:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
  %f16:  076e072707740720 0773077507700770 076f077207740720 07440750074f0720
  %f24:  076f077207200746 0755074107200720 0720072007200720 0720072007200720
  %f32:  0720072007200720 0720072007200720 0720072007200720 0720072007200720
  %f40:  0720072007200720 0720072007200720 0720072007200720 0720072007200720
  %f48:  0720072007200720 0755074107200720 0720072007200720 0720072007200720
  %f56:  0720072007200720 0720072007200720 0720072007200720 0720072007200720
  pstate: 00000015 ccr: 00 (icc: ---- xcc: ----) asi: 80 tl: 5 pil: e
  cansave: 4 canrestore: 2 otherwin: 0 wstate: 0 cleanwin: 7 cwp: 4
  fsr: 0000000000000000 y: 0000000000000000 fprs: 0000000000000000

  Aborted

  Same happens when starting up Debian/wheezy 7.4 for sparc64:
  qemu-system-sparc64 -nographic -kernel vmlinuz -initrd initrd.gz qemu.img
  [  102.943129] eth0: RealTek RTL-8029 found at 0x1fe02000400, IRQ 6, 
52:54:00:12:34:56.
  [  105.143367] scsi0 : pata_cmd64x
  [  105.667424] scsi1 : pata_cmd64x
  [  106.003460] ata1: PATA max UDMA/33 cmd 0x1fe02000500 ctl 0x1fe02000580 
bmdma 0x1fe02000700 irq 7
  [  106.871554] ata2: PATA max UDMA/33 cmd 0x1fe02000600 ctl 0x1fe02000680 
bmdma 0x1fe02000708 irq 7
  [  108.247703] ata1.00: ATA-7: QEMU HARDDISK, 1.7.0, max UDMA/100
  [  108.775760] ata1.00: 1048576 sectors, multi 16: LBA48 
  [  109.399827] ata1.00: configured for UDMA/33
  [  109.815872] scsi 0:0:0:0: Direct-Access     ATA      QEMU HARDDISK    1.7. 
PQ: 0 ANSI: 5
  [  111.004001] ata2.00: ATAPI: QEMU DVD-ROM, 1.7.0, max UDMA/100
  [  111.608066] ata2.00: configured for UDMA/33
  [  112.040113] scsi 1:0:0:0: CD-ROM            QEMU     QEMU DVD-ROM     1.7. 
PQ: 0 ANSI: 5
  [  114.344362] sd 0:0:0:0: [sda] 1048576 512-byte logical blocks: (536 MB/512 
MiB)
  qemu: fatal: Trap 0x0032 while trap level (5) >= MAXTL (5), Error state
  pc: 00000000004055bc  npc: 00000000004055c0
  %g0-3: 0000000000000000 0000000000000200 fffff80007e6bd10 0000000000000200
  %g4-7: f500046400000000 0000000000000000 fffff80005d34000 f500000000000000
  %o0-3: fffff80005f68148 fffff80005f68180 000000000000000c 0000000000000001 
  %o4-7: fffff80005d4b889 000001fe02000600 fffff8000705b391 0000000010064474 
  %l0-3: 0000000000000000 00000000007f6330 0000000000200200 fffff80007e6be60 
  %l4-7: 0000000000000000 0000000000945bd8 0000000000945fd8 00000000009463d8 
  %i0-3: fffff80005f68000 fffff80005f68148 0000000000000058 0000000000000001 
  %i4-7: fffff80005f69ce8 0000000000000000 fffff8000705b451 0000000010064ab8 
  %f00:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
  %f08:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
  %f16:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
  %f24:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
  %f32:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
  %f40:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
  %f48:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
  %f56:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
  pstate: 00000015 ccr: 00 (icc: ---- xcc: ----) asi: 80 tl: 5 pil: e
  cansave: 3 canrestore: 3 otherwin: 0 wstate: 0 cleanwin: 7 cwp: 7
  fsr: 0000000000000000 y: 000000000003e810 fprs: 0000000000000000

  Aborted

  Anything I can do to get it boot from disk?

  thanks in advance.
   Waldemar

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1278977/+subscriptions



reply via email to

[Prev in Thread] Current Thread [Next in Thread]