From: "Martin J. Bligh" <mbligh@aracnet.com>
To: William Lee Irwin III <wli@holomorphy.com>, linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org
Subject: Re: 48GB NUMA-Q boots, with major IO-APIC hassles
Date: Wed, 15 Jan 2003 07:24:40 -0800 [thread overview]
Message-ID: <840980000.1042644279@titus> (raw)
In-Reply-To: <20030115105802.GQ940@holomorphy.com>
> (2) MAX_IO_APIC's got clobbered in the subarch cleanups.
> -- CONFIG_X86_NUMA was removed, use CONFIG_X86_NUMAQ
> -- this is greppable, folks...
That wasn't the subarch cleanups that removed it, please be careful
what you're saying. I plead not guilty to that one.
> (4) PCI bridges get misnumbered children.
> -- Brew up a PCI hook for giving child buses their bus numbers.
> -- Basically, fwd port mbligh's fix for 2.4.x more cleanly.
> -- Okay, not IO-APIC-related, but it annoys me greatly.
> -- ink is at least trying to steer me in the right direction here.
Additional PCI-PCI bridges (eg starfire cards) have never been supported
in non-boot quads. It's not impossible, but don't be suprised if it
doesn't work.
> (5) Booting with notsc panic()'s.
> -- Remove tsc_disable assignment in the __setup() call.
> -- I'd be much obliged if the SMP TSC issues were at long
> -- last conclusively dealt with. Not IO-APIC-related either,
> -- but also very annoying.
You don't have PIT support compiled in, and you turned off TSC support,
leaving yourself with no timer. There's a patch in my tree to force on
PIT support for NUMA-Q.
M.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2003-01-15 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 10:58 William Lee Irwin III
2003-01-15 15:24 ` Martin J. Bligh [this message]
2003-01-15 15:34 ` William Lee Irwin III
2003-03-28 5:08 ` William Lee Irwin III
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=840980000.1042644279@titus \
--to=mbligh@aracnet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=wli@holomorphy.com \
/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