From: Len Brown <lenb@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Tear <tarrqt@yahoo.com>,
mingo@redhat.com, akpm@linux-foundation.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andi Kleen <ak@suse.de>
Subject: Re: [RFC][PATCH] IO-APIC blacklist
Date: Sat, 2 Jun 2007 19:33:40 -0400 [thread overview]
Message-ID: <200706021933.40583.lenb@kernel.org> (raw)
In-Reply-To: <alpine.LFD.0.98.0706021400330.23741@woody.linux-foundation.org>
> -uhci_hcd 0000:00:1f.2: irq 19, io base 0x0000ff80 # slow
> +uhci_hcd 0000:00:1f.2: irq 17, io base 0x0000ff80 # fine
nope, this function is on on hardware IRQ 19 in both cases.
it just looks like IRQ 17 in the ACPI case due to this:
ACPI: PCI Interrupt 0000:00:1f.2[D] -> GSI 19 (level, low) -> IRQ 17
Totally bogus? Yes.
google "Kill IRQ compression"
But while I truly hate this particular hack and I've wanted it gone for a long time,
it doesn't appear to be related to the failure at hand -- it just makes
it more irritating to debug.
-Len
next prev parent reply other threads:[~2007-06-02 23:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 14:10 [RFC][PATCH] IO-APIC blacklist Tear
2007-06-02 14:39 ` Heikki Orsila
2007-06-02 16:39 ` Linus Torvalds
2007-06-02 20:32 ` Tear
2007-06-02 21:28 ` Linus Torvalds
2007-06-02 22:54 ` Andrew Morton
2007-06-02 23:13 ` Len Brown
2007-06-02 23:33 ` Len Brown [this message]
2007-06-02 23:53 ` Tear
2007-06-03 4:16 ` Len Brown
2007-06-03 10:24 ` Tear
2007-06-03 11:25 ` Tear
2007-06-02 17:46 ` Len Brown
2007-06-02 20:39 ` Tear
2007-06-02 20:55 ` Linus Torvalds
2007-06-02 23:48 ` Tear
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=200706021933.40583.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tarrqt@yahoo.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.