Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #53545 > unrolled thread
| Started by | Christian Schwamborn <cs@imap.architektur.tu-darmstadt.de> |
|---|---|
| First post | 2016-04-11 13:40 +0200 |
| Last post | 2016-04-14 01:10 +0200 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.debian.kernel
Bug#820680: xen dom0 pciback issue - pci passthrough generates "xen:events: Failed to obtain physical IRQ" in domu Christian Schwamborn <cs@imap.architektur.tu-darmstadt.de> - 2016-04-11 13:40 +0200
Processed: Re: xen dom0 pciback issue - pci passthrough generates "xen:events: Failed to obtain physical IRQ" in domu owner@bugs.debian.org (Debian Bug Tracking System) - 2016-04-14 01:10 +0200
Bug#820680: xen dom0 pciback issue - pci passthrough generates "xen:events: Failed to obtain physical IRQ" in domu Ben Hutchings <ben@decadent.org.uk> - 2016-04-14 01:10 +0200
| From | Christian Schwamborn <cs@imap.architektur.tu-darmstadt.de> |
|---|---|
| Date | 2016-04-11 13:40 +0200 |
| Subject | Bug#820680: xen dom0 pciback issue - pci passthrough generates "xen:events: Failed to obtain physical IRQ" in domu |
| Message-ID | <rmIme-57L-21@gated-at.bofh.it> |
Package: linux-image-3.16.0-4-amd64 Version: 3.16.7-ckt25-2 Source: linux Severity: important Since a kernel update in early Januar 2016 xen pci passthrough stopped working. There is already a bug report against the hypervisor in place (#810379) and a upstream report at xenproject.org which provides patches as well as at kernel.org (at least for 4.x kernel, https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.1.20). The patches where created and tested against the current jessie 3.16 kernel and I'm currenly testing those as well - so far it looks good. For further information on how to reproduce this issue and the patches, I refer to the existing reports at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810379 http://lists.xenproject.org/archives/html/xen-devel/2016-02/msg00658.html As those patches are accepted upstream, it should follow the debian rules for beeing fixable in stable. Cheers, Christian Schwamborn
[toc] | [next] | [standalone]
| From | owner@bugs.debian.org (Debian Bug Tracking System) |
|---|---|
| Date | 2016-04-14 01:10 +0200 |
| Subject | Processed: Re: xen dom0 pciback issue - pci passthrough generates "xen:events: Failed to obtain physical IRQ" in domu |
| Message-ID | <rnC54-x7-27@gated-at.bofh.it> |
| In reply to | #53545 |
Processing control commands: > tag -1 upstream fixed-upstream Bug #820680 [src:linux] xen dom0 pciback issue - pci passthrough generates "xen:events: Failed to obtain physical IRQ" in domu Added tag(s) upstream and fixed-upstream. > fixed -1 4.5~rc7-1~exp1 Bug #820680 [src:linux] xen dom0 pciback issue - pci passthrough generates "xen:events: Failed to obtain physical IRQ" in domu Marked as fixed in versions linux/4.5~rc7-1~exp1. -- 820680: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820680 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [next] | [standalone]
| From | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| Date | 2016-04-14 01:10 +0200 |
| Message-ID | <rnC54-x7-19@gated-at.bofh.it> |
| In reply to | #53545 |
[Multipart message — attachments visible in raw view] — view raw
Control: tag -1 upstream fixed-upstream Control: fixed -1 4.5~rc7-1~exp1 On Mon, 11 Apr 2016 13:31:28 +0200 Christian Schwamborn <cs@imap.architektur.tu-darmstadt.de> wrote: > Package: linux-image-3.16.0-4-amd64 > Version: 3.16.7-ckt25-2 > Source: linux > Severity: important > > Since a kernel update in early Januar 2016 xen pci passthrough stopped > working. > There is already a bug report against the hypervisor in place (#810379) > and a upstream report at xenproject.org which provides patches as well > as at kernel.org (at least for 4.x kernel, > https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.1.20). > The patches where created and tested against the current jessie 3.16 > kernel and I'm currenly testing those as well - so far it looks good. > > For further information on how to reproduce this issue and the patches, > I refer to the existing reports at: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810379 > http://lists.xenproject.org/archives/html/xen-devel/2016-02/msg00658.html > > As those patches are accepted upstream, it should follow the debian > rules for beeing fixable in stable. For future references, the patches went into 4.5-rc6 as: commit 8d47065f7d1980dde52abb874b301054f3013602 Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Date: Thu Feb 11 16:10:23 2016 -0500 xen/pciback: Check PF instead of VF for PCI_COMMAND_MEMORY commit d159457b84395927b5a52adb72f748dd089ad5e5 Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Date: Thu Feb 11 16:10:24 2016 -0500 xen/pciback: Save the number of MSI-X entries to be copied later. commit 2cfec6a2f989d5c921ba11a329ff8ea986702b9b Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Date: Thu Feb 11 16:10:25 2016 -0500 xen/pcifront: Report the errors better. commit 4d8c8bd6f2062c9988817183a91fe2e623c8aa5e Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Date: Thu Feb 11 16:10:26 2016 -0500 xen/pcifront: Fix mysterious crashes when NUMA locality information was extracted. -- Ben Hutchings It is easier to change the specification to fit the program than vice versa.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web