From: "Jan Beulich" <JBeulich@suse.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Xen-unstable: pci-passthrough "irq 16: nobody cared" on HVM guest shutdown on irq of device not passed through.
Date: Fri, 26 Sep 2014 07:59:22 +0100 [thread overview]
Message-ID: <54252AEA02000078000396CD@mail.emea.novell.com> (raw)
In-Reply-To: <1028558175.20140926000905@eikelenboom.it>
>>> On 26.09.14 at 00:09, <linux@eikelenboom.it> wrote:
> - Tried booting dom0 with pci=nosmi, but that didn't make a difference, still
> "irq16 nobody cared".
> - Tried booting dom0 with pci=nomsi and irqpoll, that prevented the "irq16
> nobody cared" from appearing, i could see around 600000 interrupts for
> irq16,
> however the machine now freezes shortly afterward without any error (on
> serial
> console with sync-console on, triple ctrl-a also doesn't work anymore)
Again please don't mix up host and guest MSI. Host IRQ 16 can't
possibly be an MSI one.
> - Tried switching off the onboard soundcard in the bios. Now irq16 is not
> bound
> to any device, but the machine still freezes without any error (on serial
> console with sync-console on, triple ctrl-a also doesn't work anymore)
I suppose that hang is with irqpoll still in use? Ctrl-a not working anymore
makes me wonder whether you use a PCI serial card sitting on that same
IRQ for the Xen console... Furthermore in that mode (with supposedly no
handler set up for IRQ 16) monitoring (with a little bit of debugging code)
how/when IRQ 16 gets setup and unmasked may provide further hints.
Jan
next prev parent reply other threads:[~2014-09-26 6:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 14:36 Xen-unstable: pci-passthrough "irq 16: nobody cared" on HVM guest shutdown on irq of device not passed through Sander Eikelenboom
2014-09-25 14:42 ` Andrew Cooper
2014-09-25 14:47 ` Sander Eikelenboom
2014-09-25 15:11 ` Jan Beulich
2014-09-25 15:49 ` Sander Eikelenboom
2014-09-25 16:14 ` Jan Beulich
2014-09-25 17:02 ` Sander Eikelenboom
2014-09-25 18:45 ` Sander Eikelenboom
2014-09-25 22:09 ` Sander Eikelenboom
2014-09-26 6:59 ` Jan Beulich [this message]
2014-09-26 9:18 ` Sander Eikelenboom
2014-09-26 9:43 ` Jan Beulich
2014-09-26 10:02 ` Sander Eikelenboom
2014-09-26 10:08 ` Jan Beulich
2014-09-27 14:00 ` Sander Eikelenboom
2014-09-27 18:02 ` Konrad Rzeszutek Wilk
2014-09-27 18:23 ` Sander Eikelenboom
2014-10-01 13:52 ` Sander Eikelenboom
2014-10-01 14:19 ` Jan Beulich
2014-10-07 13:41 ` Konrad Rzeszutek Wilk
2014-10-07 14:50 ` Jan Beulich
2014-10-08 12:56 ` Konrad Rzeszutek Wilk
2014-10-08 20:33 ` Sander Eikelenboom
2014-10-21 13:43 ` Sander Eikelenboom
2014-10-21 14:52 ` Jan Beulich
2014-09-26 6:54 ` Jan Beulich
2014-09-26 9:06 ` Sander Eikelenboom
2014-09-26 6:50 ` Jan Beulich
2014-09-26 9:00 ` Sander Eikelenboom
2014-09-26 9:09 ` Jan Beulich
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=54252AEA02000078000396CD@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xenproject.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).