From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: MSI error when reloading iwlagn module
Date: Tue, 27 Sep 2011 12:57:26 -0700 [thread overview]
Message-ID: <4E822AA6.4010605@goop.org> (raw)
Hi,
With a fairly current kernel + xen, I'm seeing this if I rmmod iwlagn
and try to reload it:
[51230.646678] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
[51230.646685] Copyright(c) 2003-2011 Intel Corporation
[51230.646760] xen: registering gsi 17 triggering 0 polarity 1
[51230.646773] xen_map_pirq_gsi: returning irq 17 for gsi 17
[51230.646777] xen: --> pirq=17 -> irq=17 (gsi=17)
[51230.646781] Already setup the GSI :17
[51230.646789] iwlagn 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[51230.646814] iwlagn 0000:03:00.0: setting latency timer to 64
[51230.646935] iwlagn 0000:03:00.0: pci_resource_len = 0x00002000
[51230.646941] iwlagn 0000:03:00.0: pci_resource_base = ffffc9000671c000
[51230.646945] iwlagn 0000:03:00.0: HW Revision ID = 0x35
[51230.647075] iwlagn 0000:03:00.0: xen map irq failed -22 for 32752 domain
[51230.647081] iwlagn 0000:03:00.0: pci_enable_msi failed
[51230.647113] iwlagn 0000:03:00.0: PCI INT A disabled
[51230.647126] iwlagn: probe of 0000:03:00.0 failed with error -22
with this on the Xen console
(XEN) physdev.c:139: dom0: can't create irq for msi!
I'm running Xen as of a422e2a4451e, which your MSI changes in them,
which I suspect of having caused a regression (since I don't remember
having problems reloading msi-using drivers before).
Thanks,
J
next reply other threads:[~2011-09-27 19:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 19:57 Jeremy Fitzhardinge [this message]
2011-09-28 8:33 ` MSI error when reloading iwlagn module Jan Beulich
2011-09-28 10:17 ` George Dunlap
2011-11-07 10:08 ` Jan Beulich
2011-11-09 19:09 ` Jeremy Fitzhardinge
2011-09-28 10:27 ` Jan Beulich
2011-09-28 11:07 ` George Dunlap
2011-09-28 16:50 ` Jeremy Fitzhardinge
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=4E822AA6.4010605@goop.org \
--to=jeremy@goop.org \
--cc=JBeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.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.