From: Paul Hubbard <phubbard@fnal.gov>
To: unlisted-recipients:; (no To-header on input)@pop.zip.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: 4G SGI quad Xeon -memory-related slowdowns
Date: Wed, 17 Jan 2001 12:19:16 -0600 [thread overview]
Message-ID: <3A65E224.72826E01@fnal.gov> (raw)
In-Reply-To: <ut24rz074jw.fsf@lydia.adaptive.net>
> Sounds like a true-to-God bug. Possibly in the form of incorrect MTRR
> settings. Make sure you enable MTRR support.
MTRR is enabled - here's the dump from /proc/mtrr:
reg00: base=0xc0000000 (3072MB), size=1024MB: uncachable, count=1
reg01: base=0x00000000 ( 0MB), size=4096MB: write-back, count=1
reg02: base=0x100000000 (4096MB), size=1024MB: write-back, count=1
Note that the sizes sum to six gigabytes, and we only have four in the
box.
We've discovered that if we turn off PCI hotplug support and resource
remapping in the BIOS, then /proc/mtrr looks more sensible:
reg00: base=0xfc000000 (4032MB), size= 64MB: uncachable, count=1
reg01: base=0x00000000 ( 0MB), size=4096MB: write-back, count=1
However, the 64G-compiled kernel still hangs.
The complete task dump is at http://quirk.fnal.gov/xeon/
It looks like everything is blocked on lock_get_status.
> I do need more information on what seems to hang, and how it hangs. One
> of the pre-kernels will give you a nice stack backtrace for each process
> if you press control-scrolllock, and that might be useful.
Sysreq dump, plus meminfo and MTRR are at the above URL. Please let me
know if you need any other information.
FYI, with the revised BIOS settings, even the 4G-compiled kernel sees
and uses the full 4G. So if this problem turns out to take time to fix,
we can still get full use from the machine in the interim.
Many thanks for the help!
-Paul
--
Paul Hubbard phubbard@fnal.gov
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
parent reply other threads:[~2001-01-17 18:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <ut24rz074jw.fsf@lydia.adaptive.net>]
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=3A65E224.72826E01@fnal.gov \
--to=phubbard@fnal.gov \
--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®