From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.kernel.org ([198.145.29.136]:33779 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756865AbcCaPOF (ORCPT ); Thu, 31 Mar 2016 11:14:05 -0400 Date: Thu, 31 Mar 2016 10:14:01 -0500 From: Bjorn Helgaas To: Rob Groner Cc: "linux-pci@vger.kernel.org" , "jiang.liu@linux.intel.com" , "bhelgaas@google.com" , "tglx@linutronix.de" Subject: Re: PCI IRQ issue since 4.2 kernel Message-ID: <20160331151401.GA15801@localhost> References: <1459430795.1998.11.camel@rtd-VirtualBox> <20160331134000.GA31995@localhost> <1459436757.1998.14.camel@rtd-VirtualBox> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <1459436757.1998.14.camel@rtd-VirtualBox> Sender: linux-pci-owner@vger.kernel.org List-ID: On Thu, Mar 31, 2016 at 11:05:57AM -0400, Rob Groner wrote: > On Thu, 2016-03-31 at 09:40 -0400, Bjorn Helgaas wrote: > > Hi Rob, > > > > On Thu, Mar 31, 2016 at 09:26:35AM -0400, Rob Groner wrote: > > > We became aware of an issue with our Linux drivers when used with a 4.4 > > > kernel. These drivers had worked previously from 2.6.35 to 4.2 kernels. > > > The symptoms were that, even though the request_irq() call was > > > successful, we did not receive any IRQs. IRQs did arrive on a different > > > IRQ line, however, and the kernel disabled that line because there was > > > no handler. > > > > Others have seen similar issues, so we reverted 991de2e59090 ("PCI, x86: > > Implement pcibios_alloc_irq() and pcibios_free_irq()"). > > > > The revert, 6c777e8799a9 ("Revert "PCI, x86: Implement pcibios_alloc_irq() > > and pcibios_free_irq()""), appeared in v4.5-rc6, so if you try that or a > > later kernel (including v4.5), it should work. > > > > Let us know if you still see problems. > > > > Bjorn > > I installed the 4.5 kernel from kernel.org and my issue has been > resolved. Thank you very much! > > Will this revert possibly make it into 4.3 and 4.4, or will I have to > tell people to avoid those versions? Shoot, I forgot to mark that revert for stable. I'll see if I can figure out how to do that after the fact. Of course, you'll still have to tell people to use the latest 4.3.x or 4.4.x stable kernels, not the original 4.3 and 4.5. Bjorn