From: "Marco d'Itri" <md@Linux.IT>
To: Andi Kleen <ak@colin2.muc.de>
Cc: Linus Torvalds <torvalds@osdl.org>, Andi Kleen <ak@muc.de>,
linux-kernel@vger.kernel.org, len.brown@intel.com
Subject: Re: irq 15: nobody cared! with KT600 chipset and 2.6.0-test9
Date: Sun, 23 Nov 2003 11:29:53 +0100 [thread overview]
Message-ID: <20031123102953.GA1852@wonderland.linux.it> (raw)
In-Reply-To: <20031123051011.GA92830@colin2.muc.de>
On Nov 23, Andi Kleen <ak@colin2.muc.de> wrote:
>On Sat, Nov 22, 2003 at 08:23:16PM -0800, Linus Torvalds wrote:
>>
>> On Sun, 23 Nov 2003, Andi Kleen wrote:
>> >
>> > It's a long standing bug in how we handle VIA on board devices in ACPI.
>> > It was a big problem on x86-64 too until I cheated and used only
>> > PIC mode when there is a VIA southbridge.
>>
>> That doesn't explain the lack of autodetection, and the early irq15
>> registration.
>>
>> That would explain why no interrupts make it at all, but why do we not
>> even probe for irq15 here?
>
>It's easy to test. does it work when booted with "noapic" ?
Yes, I checked again.
--
ciao, |
Marco | [3232 ma6tjQg3wBT1w]
next prev parent reply other threads:[~2003-11-23 10:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <UPPL.70W.11@gated-at.bofh.it>
[not found] ` <UReK.uF.5@gated-at.bofh.it>
2003-11-23 3:39 ` irq 15: nobody cared! with KT600 chipset and 2.6.0-test9 Andi Kleen
2003-11-23 4:23 ` Linus Torvalds
2003-11-23 5:10 ` Andi Kleen
2003-11-23 10:29 ` Marco d'Itri [this message]
2003-11-23 19:16 Brown, Len
-- strict thread matches above, loose matches on Subject: below --
2003-11-22 23:55 Marco d'Itri
2003-11-23 1:21 ` Linus Torvalds
2003-11-23 1:59 ` Linus Torvalds
2003-11-23 2:15 ` Marco d'Itri
2003-11-23 3:24 ` Linus Torvalds
2003-11-23 5:49 ` Len Brown
2003-11-23 11:40 ` Marco d'Itri
2003-11-23 16:40 ` Linus Torvalds
2003-11-23 18:52 ` Marco d'Itri
2003-11-23 19:12 ` Linus Torvalds
2003-11-23 19:41 ` Marco d'Itri
2003-11-15 10:43 Marco d'Itri
2003-11-16 11:13 ` Marco d'Itri
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=20031123102953.GA1852@wonderland.linux.it \
--to=md@linux.it \
--cc=ak@colin2.muc.de \
--cc=ak@muc.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.