From: Jonathan Nieder <jrnieder@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, Michael Tokarev <mjt@tls.msk.ru>,
Guillem Jover <guillem@debian.org>
Subject: [regression] KVM: hangs and "irq timeout" booting HURD unless -no-kvm-irqchip passed
Date: Mon, 7 Feb 2011 00:00:30 -0600 [thread overview]
Message-ID: <20110207060030.GA1896@elie> (raw)
In-Reply-To: <1283171743-10766-2-git-send-email-avi@redhat.com>
Hi kvm-ers,
When I boot the HURD with
kvm -m 768 -net nic,model=ne2k_pci -net user hurd-installed.qemu
it hangs and eventually produces two messages:
hd0: unexpected_intr: status=0x58 { DriveReady SeekComplete DataRequest }
hd0: irq timeout: status=0x58 { DriveReady Seek Complete DataRequest }
More details below[1].
Adding -no-kvm-irqchip to the kvm command line fixes it --- no
more hangs or confusing messages (thanks, Guillem!).
Bisects (thanks to Michael for the idea) to
v2.6.37-rc1~142^2~39 (KVM: Check for pending events before
attempting injection, 2010-07-27).
Bisection log and kernel configuration available upon request (but
probably not too relevant --- the 2.6.37 distro kernel from Debian
exhibits the same problem). Reproducible with kvm/master (2d4b4d26,
2011-02-01).
CPU is a dual-core AMD Athlon II P360, family 16, model 6.
Any hints for tracking this down? For those wanting to follow along
at home, you can find a HURD cd to try at [2].
Thanks for kvm --- now that I have hardware that can handle it, it's
become a favorite toy. :)
Jonathan
[1] Background: http://bugs.debian.org/612105
Result:
1. Normal boot procedure. Eventually the following message from HURD
is on the console:
start ext2fs: Hurd server bootstrap: ext2fs[device:hd0s1] exec
2. Hang. I hit ctrl+alt, "info registers", and so on in the hope of
waking it up. Eventually...
3. A flood of repeated
kb_setleds1: unexpected state (1)
messages.
4. Another message and another hang:
hd0: unexpected_intr: status=0x58 { DriveReady SeekComplete DataRequest }
hd0: irq timeout: status=0x58 { DriveReady Seek Complete DataRequest }
(the two messages overlap sometimes).
[2] http://people.debian.org/~sthibault/hurd-i386/installer/cdimage/
next prev parent reply other threads:[~2011-02-07 6:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 12:35 [PATCH v5 0/5] Nonatomic interrupt injection Avi Kivity
2010-08-30 12:35 ` [PATCH v5 1/5] KVM: Check for pending events before attempting injection Avi Kivity
2011-02-07 6:00 ` Jonathan Nieder [this message]
2011-02-07 12:39 ` [regression] KVM: hangs and "irq timeout" booting HURD unless -no-kvm-irqchip passed Avi Kivity
2011-02-07 12:45 ` Gleb Natapov
2011-02-07 13:27 ` Gleb Natapov
2011-02-08 1:40 ` Jonathan Nieder
2011-02-08 7:40 ` Michael Tokarev
2011-02-08 12:00 ` Gleb Natapov
2011-02-08 14:22 ` Marcelo Tosatti
2011-02-08 14:41 ` Gleb Natapov
2011-02-08 14:43 ` Avi Kivity
2011-02-08 14:47 ` Gleb Natapov
2011-02-08 14:57 ` Avi Kivity
2011-02-08 17:44 ` Marcelo Tosatti
2011-02-08 20:40 ` Jonathan Nieder
2010-08-30 12:35 ` [PATCH v5 2/5] KVM: VMX: Split up vmx_complete_interrupts() Avi Kivity
2010-08-30 12:35 ` [PATCH v5 3/5] KVM: VMX: Move real-mode interrupt injection fixup to vmx_complete_interrupts() Avi Kivity
2010-08-30 12:35 ` [PATCH v5 4/5] KVM: VMX: Parameterize vmx_complete_interrupts() for both exit and entry Avi Kivity
2010-08-30 12:35 ` [PATCH v5 5/5] KVM: Non-atomic interrupt injection Avi Kivity
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=20110207060030.GA1896@elie \
--to=jrnieder@gmail.com \
--cc=avi@redhat.com \
--cc=guillem@debian.org \
--cc=kvm@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=mtosatti@redhat.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).