From: Nikolai Kondrashov <spbnick@gmail.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
688964@bugs.debian.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Bug#688964: qemu-kvm: Fedora 17 guest hangs on boot with soft lockup in udevd
Date: Thu, 27 Sep 2012 22:40:34 +0300 [thread overview]
Message-ID: <5064ABB2.2000503@gmail.com> (raw)
In-Reply-To: <506489CD.8080605@msgid.tls.msk.ru>
On 09/27/2012 08:15 PM, Michael Tokarev wrote:
> Ok. I reproduced this, I _think_, and now I want some confirmation
> from you. This is my command line:
>
> QEMU_AUDIO_DRV=none qemu-kvm -nodefconfig -nodefaults -enable-kvm \
> -monitor stdio -rtc base=utc \
> -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \
> -m 512 -vga cirrus -cdrom Fedora-17-x86_64-Live-Desktop.iso \
> -device intel-hda,id=sound0,bus=pci.0,addr=0x4 \
> -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0
>
> leads to this in guest:
>
> ...
> Starting udev Wait for Complete Device Initialization...
> [ 4.123978] piix4_smbus 0000:00:01.3: SMBus Host Controller at 0xb100, revision 0
> [ 4.311473] microcode: AMD CPU family 0x6 not supported
> [ 4.355429] microcode: AMD CPU family 0x6 not supported
> [ 7.323032] ALSA sound/pci/hda/hda_intel.c:823 azx_get_response timeout, switching to polling mode: last cmd=0x000f0000
> [ 8.325018] ALSA sound/pci/hda/hda_intel.c:831 No response from codec, disabling MSI: last cmd=0x000f0000
> [ 36.055021] BUG: soft lockup - CPU#0 stuck for 22s! [udevd:385]
>
> Is it the issue you're seeing?
>
> Removing hda-duplex device lets it to work. Removing piix3-usb-uhci
> allows it to boot too. Even removing the explicit bus address from
> piix3-usb-uhci allow it to boot.
>
> Nikolai, please verify if this is the issue you're seeing, and
> please try without sound device. If this is the case, let's
> downgrade this bug from important to normal, since emulated sound
> devices aren't really of high priority in this context, and there
> should be easy workaround (to disable sound).
I wasn't able to get a backtrace, unfortunately. It just isn't printed.
Could
I be missing some trick? However, removing the sound device did help.
I'll try the patch you sent in another message next.
Thank you.
next prev parent reply other threads:[~2012-09-27 19:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120927142751.28864.67471.reportbug@gimli.ponomarevs.fi>
[not found] ` <50646F5F.7080703@msgid.tls.msk.ru>
[not found] ` <50647E08.7050606@gmail.com>
2012-09-27 17:15 ` [Qemu-devel] Bug#688964: qemu-kvm: Fedora 17 guest hangs on boot with soft lockup in udevd Michael Tokarev
2012-09-27 17:39 ` Michael Tokarev
2012-09-27 18:28 ` Jan Kiszka
2012-09-27 18:43 ` Michael Tokarev
2012-09-27 19:03 ` Jan Kiszka
2012-09-27 19:32 ` Michael S. Tsirkin
2012-09-27 19:34 ` Michael Tokarev
2012-09-27 19:40 ` Nikolai Kondrashov [this message]
2012-09-27 19:57 ` Nikolai Kondrashov
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=5064ABB2.2000503@gmail.com \
--to=spbnick@gmail.com \
--cc=688964@bugs.debian.org \
--cc=jan.kiszka@siemens.com \
--cc=kraxel@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=mst@redhat.com \
--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).