From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Greg Kroah-Hartman <greg@kroah.com>
Subject: Re: IRQ routing problem in 2.6.10-rc2
Date: Sun, 24 Jul 2005 23:08:32 +0200 [thread overview]
Message-ID: <42E40350.203@drzeus.cx> (raw)
In-Reply-To: <9a87484905072407164f0e0eb5@mail.gmail.com>
Jesper Juhl wrote:
>
>Have you tried the suggestion given "... As a temporary workaround,
>the "pci=routeirq" argument..." ?
>You could also try the pci=noacpi boot option to see if that changes anything.
>
>
No, I missed that one. The machine works fine with either of those two
options. I sent a comment with lspci to Bjorn Helgaas as suggested.
>Also, that's a fairly old kernel you have there, could you try
>2.6.13-rc3, 2.6.13-rc3-git6 or 2.6.13-rc3-mm1 ?
>
>
>
I discovered the problem running 2.6.12. I only tried these kernels to
pinpoint where the problem began.
Rgds
Pierre
prev parent reply other threads:[~2005-07-24 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-24 13:21 IRQ routing problem in 2.6.10-rc2 Pierre Ossman
2005-07-24 14:03 ` Pierre Ossman
2005-07-24 14:16 ` Jesper Juhl
2005-07-24 15:13 ` Jan Engelhardt
2005-07-24 16:10 ` Jesper Juhl
2005-07-24 21:08 ` Pierre Ossman [this message]
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=42E40350.203@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=greg@kroah.com \
--cc=jesper.juhl@gmail.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