From: Artyom Tarasenko <atar4qemu@gmail.com>
To: Bug 1278977 <1278977@bugs.launchpad.net>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Bug 1278977] Re: qemu-system-sparc64 crash when initializing disk
Date: Tue, 1 Apr 2014 17:06:34 +0200 [thread overview]
Message-ID: <CACXAS8CAoQbSP15Xo_GvkPmb78K+e35Huy6OG_BEXts5oJ__Tg@mail.gmail.com> (raw)
In-Reply-To: <20140401093719.5705.11282.malone@chaenomeles.canonical.com>
Hi Waldemar,
It can be a Linux kernel bug or a QEMU bug. To get the further info,
try -serial telnet::4444,server,wait
and use the telnet as a serial console. When the guest hangs use the
telnet menu to send break, and then type 'T'.
This would produce the same result as magic SysRq+T: the kernel will
list the active threads (the magic SysRq has to be enabled to use this
feature though). Then please post the listing here and on the
sparclinux@ mailing list.
Artyom
On Tue, Apr 1, 2014 at 11:37 AM, wbx <mail@waldemar-brodkorb.de> wrote:
> Hi Artyom,
>
> okay, with 1.7.0 on Maverick I get:
> (qemu) info block
> virtio0: qemu-sparc64.img (raw)
>
> ide0-hd0: qemu-sparc64.img (raw)
>
> ide1-cd0: [not inserted]
> Removable device: not locked, tray closed
>
> floppy0: [not inserted]
> Removable device: not locked, tray closed
>
> sd0: [not inserted]
> Removable device: not locked, tray closed
> (qemu) info blockstats
> virtio0: rd_bytes=42984448 wr_bytes=148874240 rd_operations=6310 wr_operations=16470 flush_operations=0 wr_total_time_ns=450789456000 rd_total_time_ns=23944239000 flush_total_time_ns=0
> ide0-hd0: rd_bytes=0 wr_bytes=0 rd_operations=0 wr_operations=0 flush_operations=0 wr_total_time_ns=0 rd_total_time_ns=0 flush_total_time_ns=0
> ide1-cd0: rd_bytes=0 wr_bytes=0 rd_operations=0 wr_operations=0 flush_operations=0 wr_total_time_ns=0 rd_total_time_ns=0 flush_total_time_ns=0
> floppy0: rd_bytes=0 wr_bytes=0 rd_operations=0 wr_operations=0 flush_operations=0 wr_total_time_ns=0 rd_total_time_ns=0 flush_total_time_ns=0
> sd0: rd_bytes=0 wr_bytes=0 rd_operations=0 wr_operations=0 flush_operations=0 wr_total_time_ns=0 rd_total_time_ns=0 flush_total_time_ns=0
>
> The guest is hanging.
>
> best regards
> Waldemar
>
> --
> 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
>
--
Regards,
Artyom Tarasenko
linux/sparc and solaris/sparc under qemu blog:
http://tyom.blogspot.com/search/label/qemu
next prev parent reply other threads:[~2014-04-01 15:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 17:05 [Qemu-devel] [Bug 1278977] [NEW] qemu-system-sparc64 crash when initializing disk wbx
2014-02-14 18:45 ` [Qemu-devel] [Bug 1278977] " Mark Cave-Ayland
2014-02-16 9:58 ` wbx
2014-02-19 19:10 ` wbx
2014-02-21 23:31 ` Mark Cave-Ayland
2014-02-22 13:57 ` wbx
2014-03-27 0:23 ` Mark Cave-Ayland
2014-03-31 7:27 ` wbx
2014-03-31 21:30 ` Artyom Tarasenko
2014-04-01 9:37 ` wbx
2014-04-01 15:06 ` Artyom Tarasenko [this message]
2014-04-02 5:22 ` wbx
2014-04-02 6:04 ` wbx
2014-04-02 18:45 ` Richard Henderson
2014-08-22 15:46 ` Mark Cave-Ayland
2014-08-23 22:53 ` wbx
2014-08-24 7:49 ` Mark Cave-Ayland
2014-09-02 13:18 ` Mark Cave-Ayland
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=CACXAS8CAoQbSP15Xo_GvkPmb78K+e35Huy6OG_BEXts5oJ__Tg@mail.gmail.com \
--to=atar4qemu@gmail.com \
--cc=1278977@bugs.launchpad.net \
--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).