From: Jan Kiszka <jan.kiszka@web.de>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: qemu crashes since today
Date: Wed, 16 Feb 2011 23:45:04 +0100 [thread overview]
Message-ID: <4D5C5370.6090908@web.de> (raw)
In-Reply-To: <4D5C4D4D.1020701@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
On 2011-02-16 23:18, Stefan Berger wrote:
> Qemu is crashing for me. Bisecting the code I found this here as the
> reason. Stepping one commit further into the past does not cause the crash.
>
> 6792a57bf19ab37f61f5acf0f8e3003cf08814af is the first bad commit
> commit 6792a57bf19ab37f61f5acf0f8e3003cf08814af
> Author: Jan Kiszka <jan.kiszka@siemens.com>
> Date: Mon Feb 7 12:19:18 2011 +0100
>
>
> I get crashes while booting FC14 on a FC14 host, both 64bit. Host
> running 2.6.35.11-83.fc14 . Crashes typically happen when udev has
> stared in the guest.
>
> This is the command line I was using:
>
> ./x86_64-softmmu/qemu-system-x86_64 \
> -hda ~images/fc14-x86_64.img \
> -m 2048 \
> -enable-kvm \
> -boot menu=on \
> -chardev stdio,id=seabios \
> -device isa-debugcon,iobase=0x402,chardev=seabios
>
With our without --enable-io-thread? How does the crash look like,
specifically when caught by gdb (backtrace, variable states)?
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2011-02-16 22:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 22:18 [Qemu-devel] qemu crashes since today Stefan Berger
2011-02-16 22:45 ` Jan Kiszka [this message]
2011-02-17 1:35 ` [Qemu-devel] " Stefan Berger
2011-02-17 3:09 ` Anthony Liguori
2011-02-17 8:22 ` Jan Kiszka
2011-02-17 9:21 ` Gerd Hoffmann
2011-02-17 11:36 ` Stefan Berger
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=4D5C5370.6090908@web.de \
--to=jan.kiszka@web.de \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.vnet.ibm.com \
/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).