Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
Subject: RE: 2.6.9-rc2-mm4 - Getting dev->irq equals 0
Date: Mon, 4 Oct 2004 12:16:18 -0700
Message-ID: <468F3FDA28AA87429AD807992E22D07E02C29ABE@orsmsx408>
Thread-Topic: 2.6.9-rc2-mm4 - Getting dev->irq equals 0
Thread-Index: AcSoB7y0FgfNoMZiTNunqxaSAETYnQCK4ulA
From: "Sy, Dely L" <dely.l.sy@intel.com>
To: "Bjorn Helgaas" <bjorn.helgaas@hp.com>
Cc: <linux-kernel@vger.kernel.org>, "Greg KH" <greg@kroah.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1395
Lines: 34

On Friday, October 01, 2004 3:41 PM, Bjorn Helgaas wrote:
> > I encountered a problem in running shpchp & pciehp drivers on
> > 2.6.9-rc2-mm4 kernel.  With ACPI & MSI enabled in the kernel, I 
> > got dev->irq properly for the hot-plug controllers.  With ACPI 
> > enabled and MSI not-enabled in this kernel, I got dev->irq 
> > equal 0 for the controllers. With the same options set in 
> > 2.6.8.1 & 2.6.9-rc2, things worked fine on the same system.

> Does it make any difference if you boot with "pci=routeirq"?
> I haven't looked at MSI recently, but it's possible that's
> sensitive to have all the IRQs programmed at boot-time.

Basically, the problem found was when I tried to use INTx mode 
for hot-plug controllers in ACPI enabled kernel.  I don't think 
this is related to MSI; the way I stated in the original email 
was not clear.  

I tried to boot with "pci=routeirq" and I got proper dev->irq for 
the hot-plug controllers. This tells me that my hot-plug drivers 
need to call pci_enable_device(), correct?
  
> If that does make a difference, please send me the output
> of lspci and a dmesg.

I will send them to you.

Thanks,
Dely

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/