All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Nikolai Kondrashov <spbnick@gmail.com>, 688964@bugs.debian.org
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] Bug#688964: qemu-kvm: Fedora 17 guest hangs on boot with soft lockup in udevd
Date: Thu, 27 Sep 2012 21:39:29 +0400	[thread overview]
Message-ID: <50648F51.3050805@msgid.tls.msk.ru> (raw)
In-Reply-To: <506489CD.8080605@msgid.tls.msk.ru>

To clarify:

 1. this only affects 1.1.x tree (which is a
    history for most developers already)
 2. the same guest boots okay with 1.2 (with
    kvm and irqchip enabled).

BTW, what is this hda-duplex device anyway?  I never heard of it
before now :).  And I guess using QEMU_AUDIO_DRV=none with a guest
sound device isn't very smart move ;)  (But setting it to something
else does not change things).

Also note that 1.1.1 contained one more patch which added msi
reset, this time for ahci.

Thanks,

/mjt

>   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]
> [   36.055026] Modules linked in: snd_hda_intel(+) snd_hda_codec snd_hwdep i2c_piix4 snd_pcm i2c_core snd_page_alloc snd_timer snd soundcore uinput squashfs

> commit 0ec39075710ae15acc2a5825cd21e0c229fa04af
> (8e729e3b521d9fcd87fc2e40b6322e684f58bb2e upstream)
> Author: Jan Kiszka <jan.kiszka@siemens.com>
> Date:   Fri May 11 11:42:35 2012 -0300
> 
>     intel-hda: Fix reset of MSI function

  reply	other threads:[~2012-09-27 17:39 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 [this message]
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
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=50648F51.3050805@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=688964@bugs.debian.org \
    --cc=jan.kiszka@siemens.com \
    --cc=kraxel@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=spbnick@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.