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>
Subject: RE: 2.6.9-rc2-mm4 - Getting dev->irq equals 0
Date: Mon, 4 Oct 2004 12:16:18 -0700 [thread overview]
Message-ID: <468F3FDA28AA87429AD807992E22D07E02C29ABE@orsmsx408> (raw)
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
next reply other threads:[~2004-10-04 19:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 19:16 Sy, Dely L [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-01 22:40 Bjorn Helgaas
2004-10-01 17:10 Sy, Dely L
2004-10-01 19:14 ` Andrew Morton
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=468F3FDA28AA87429AD807992E22D07E02C29ABE@orsmsx408 \
--to=dely.l.sy@intel.com \
--cc=bjorn.helgaas@hp.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®