From: Linus Torvalds <torvalds@osdl.org>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Intel Alder IOAPIC fix
Date: Mon, 12 Jan 2004 13:24:29 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0401121152070.1901@evo.osdl.org> (raw)
In-Reply-To: <1073876117.2549.65.camel@mulgrave>
On Sun, 11 Jan 2004, James Bottomley wrote:
>
> The intel alder motherboard really dislikes the way the current kernel
> reassigns all PCI resources. It exports 6 memory bars from its Extended
> Express System Support Controller, but if the system touches any of
> them, it disables the secondary IO-APIC.
>
> The system is bootable if you disable all IO-APICs apart from the
> primary, but it does become a bit crowded in interrupt space. The patch
> fixes the problem by adding a quirk to clear the first six memory bars.
What are the BAR contents? In particular, maybe the right fix is to add a
flag to say "don't touch" - but leave the BAR contents there, so that
the resource manager can actually see what the resources actually are..
Linus
next prev parent reply other threads:[~2004-01-12 21:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 2:55 James Bottomley
2004-01-12 21:24 ` Linus Torvalds [this message]
2004-01-12 22:13 ` James Bottomley
2004-01-12 23:04 ` James Bottomley
2004-01-12 23:04 ` Linus Torvalds
2004-01-13 0:25 ` James Bottomley
2004-01-13 0:45 ` James Bottomley
2004-01-13 0:25 ` Linus Torvalds
2004-01-13 16:52 ` James Bottomley
2004-01-15 5:18 ` Eric W. Biederman
2004-01-15 16:58 ` James Bottomley
2004-01-15 19:26 ` Eric W. Biederman
2004-01-15 19:54 ` James Bottomley
2004-01-16 5:32 ` Eric W. Biederman
2004-01-17 15:18 ` James Bottomley
2004-01-17 19:43 ` Eric W. Biederman
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=Pine.LNX.4.58.0401121152070.1901@evo.osdl.org \
--to=torvalds@osdl.org \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--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®