From: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
To: ncunningham-3EexvZdKGZRWk0Htik3J/w@public.gmane.org
Cc: ACPI List <acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Help wanted with IRQ routing.
Date: Wed, 16 Feb 2005 09:14:53 -0700 [thread overview]
Message-ID: <1108570493.20278.9.camel@eeyore> (raw)
In-Reply-To: <1108419552.12611.98.camel-r49W/1Cwd2ff0s6lnCXPX/uOuaPYTxhvJwvTLr3MMZM@public.gmane.org>
On Tue, 2005-02-15 at 09:19 +1100, Nigel Cunningham wrote:
> > Did you try booting with "pci=routeirq" or turning off PNPACPI?
> > I've seen a few reports of IRQ problems with PCMCIA devices that
> > seemed to be related to one or both of these.
>
> I tried pci=routeirq and it didn't make a difference. I assume PNPACPI
> is the ACPI Hotplug driver? If so, it didn't help either. It if helps at
> all, this is an Omnibook XE3-GF (4304 flavour).
Actually, PNPACPI is a build-time config option. If your kernel
is new enough, you can also turn it off at boot-time with
"pnpacpi=off".
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-16 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-14 8:59 Help wanted with IRQ routing Nigel Cunningham
[not found] ` <1108371574.12611.61.camel-r49W/1Cwd2ff0s6lnCXPX/uOuaPYTxhvJwvTLr3MMZM@public.gmane.org>
2005-02-14 16:24 ` Bjorn Helgaas
2005-02-14 22:19 ` Nigel Cunningham
[not found] ` <1108419552.12611.98.camel-r49W/1Cwd2ff0s6lnCXPX/uOuaPYTxhvJwvTLr3MMZM@public.gmane.org>
2005-02-16 16:14 ` Bjorn Helgaas [this message]
2005-02-17 22:10 ` Nigel Cunningham
2005-02-18 16:23 ` Bjorn Helgaas
2005-02-21 1:32 ` Nigel Cunningham
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=1108570493.20278.9.camel@eeyore \
--to=bjorn.helgaas-vxdhtt5mjny@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ncunningham-3EexvZdKGZRWk0Htik3J/w@public.gmane.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