From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Tommi Airikka <tommi@airikka.net>
Cc: Ian Campbell <ian.campbell@citrix.com>,
810379@bugs.debian.org, xen-devel@lists.xen.org
Subject: Re: [BUG] pci-passthrough generates "xen:events: Failed to obtain physical IRQ" for some devices
Date: Fri, 12 Feb 2016 16:36:02 -0500 [thread overview]
Message-ID: <20160212213602.GE21514@char.us.oracle.com> (raw)
In-Reply-To: <CANQMFx7LTVotNXkcVMeJcqMOhg0aKoD5x++Zfqv1-7gmeEHnUA@mail.gmail.com>
On Fri, Feb 05, 2016 at 12:35:10AM +0100, Tommi Airikka wrote:
> Hi,
>
> I patched the deb8u2 source with all four patches and built a new deb.
.. snip..
>
> Next, I upgraded dom0 with the new linux-image deb and rebooted the machine.
>
> dom0 "uname -a":
> Linux dom0 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u2a~test
> (2016-02-04) x86_64 GNU/Linux
>
> domU 'bug' "uname -a":
> Linux bug 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u2a~test
> (2016-02-04) x86_64 GNU/Linux
>
> And now everything seems to work. No more "Failed to obtain physical IRQ",
> I can mount my usb flash stick using the passthroughed usb controller. No
> call traces in dmesg.
Awesome!
Are you OK if I put 'Tested-by' on the patches from you?
next prev parent reply other threads:[~2016-02-12 21:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANQMFx4YULqKctKZqeESesTQjLQun7rQ0ZjGzq96TXTtUw6VWA@mail.gmail.com>
2016-01-27 18:30 ` [BUG] pci-passthrough generates "xen:events: Failed to obtain physical IRQ" for some devices Konrad Rzeszutek Wilk
2016-01-30 2:13 ` Marek Marczykowski-Górecki
2016-01-30 13:18 ` Tommi Airikka
2016-02-01 10:43 ` Ian Campbell
2016-02-01 14:50 ` Konrad Rzeszutek Wilk
2016-02-03 14:22 ` Marek Marczykowski-Górecki
2016-02-03 15:26 ` Konrad Rzeszutek Wilk
2016-02-08 17:39 ` Marek Marczykowski-Górecki
2016-02-09 4:59 ` Konrad Rzeszutek Wilk
2016-02-03 20:28 ` Konrad Rzeszutek Wilk
2016-02-04 9:37 ` Ian Campbell
2016-02-04 23:35 ` Tommi Airikka
2016-02-12 21:36 ` Konrad Rzeszutek Wilk [this message]
2016-02-12 21:53 ` Tommi Airikka
2016-01-23 16:12 Tommi Airikka
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=20160212213602.GE21514@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=810379@bugs.debian.org \
--cc=ian.campbell@citrix.com \
--cc=tommi@airikka.net \
--cc=xen-devel@lists.xen.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 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.