From: Charles Duffy <Charles_Duffy@messageone.com>
To: kvm@vger.kernel.org
Subject: Re: kvm-78 - kernel panic after using system_reset except when using -no-kvm-irqchip
Date: Wed, 12 Nov 2008 12:10:36 -0600 [thread overview]
Message-ID: <gff66t$hle$1@ger.gmane.org> (raw)
In-Reply-To: <491A807F.20403@web.de>
Jan Kiszka wrote:
> Charles Duffy wrote:
>> irq 25, desc: ffffffff803afc80, depth: 1, count: 0, unhandled: 0
>> ->handle_irq(): ffffffff800b54e3, handle_bad_irq+0x0/0x1f6
>> ->chip(): ffffffff802ea700, 0xffffffff802ea700
>> ->action(): 0000000000000000
>> IRQ_DISABLED set
>> unexpected IRQ trap at vector 19
>> ..MP-BIOS bug: 8254 timer not connected to IO-APIC
>> timer doesn't work through the IO-APIC - disabling NMI Watchdog!
>> Kernel panic - not syncing: IO-APIC + timer doesn't work! Try using the
>> 'noapic' kernel parameter
>
> Still too early for me, so I didn't get yet if you can trigger this
> guest panic reliably or only sporadically (like I can). In the former
> case I would be very interested in the how!
Reproduced 100% of the time when using system_reset at the qemu monitor
console coming from a non-panic'd state. (Thus, it happens only every
other time doing a series of boots and system_reset monitor commands).
> So far my theory on this is that the guest happens to loose too many PIC
> timer ticks during the test window where it checks the PIC IRQ routing
> (it does so with 10 ticks, out of which at least 4 must be delivered).
> The theory also says that this is hard to avoid, maybe just less likely
> with Gleb's timer drift compensation patches.
>
> Jan
>
> PS: Booting with noapic leaves many real boxes useless as well.
>
next prev parent reply other threads:[~2008-11-12 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 2:29 kvm-78 - kernel panic after using system_reset except when using -no-kvm-irqchip Charles Duffy
2008-11-12 7:06 ` Jan Kiszka
2008-11-12 18:10 ` Charles Duffy [this message]
2008-11-12 21:03 ` Jan Kiszka
2008-11-14 18:50 ` Jan Kiszka
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='gff66t$hle$1@ger.gmane.org' \
--to=charles_duffy@messageone.com \
--cc=kvm@vger.kernel.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