From: Robin Lee Powell <rlpowell@digitalkingdom.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Same MCE on 4 working machines (was Re: Early boot hang on recent 2.6 kernels (> 2.6.3), on x86-64 with 16gb of RAM)
Date: Fri, 15 Sep 2006 16:18:52 -0700 [thread overview]
Message-ID: <20060915231852.GV4610@chain.digitalkingdom.org> (raw)
In-Reply-To: <20060915203159.GS4610@chain.digitalkingdom.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 3215 bytes --]
Found away to get around the large RAM issue; see below.
On Fri, Sep 15, 2006 at 01:31:59PM -0700, wrote:
> On Fri, Sep 15, 2006 at 09:50:39PM +0100, Alan Cox wrote:
> >
> > You also have a lot of RAM, that shouldn't matter but it means
> > you hit code paths most users don't. If you boot with mem
> > limited to 1GB I assume it still blows up ?
>
> I've tried mem=1023M, yes, and it still blows up. Just did
> acpi=off mem=1023M to check.
I've found a server with the same hardware except only 2GiB of RAM.
The behaviour is slightly different. It restarts instead of
hanging, and the last bit is:
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
Disabling vsyscall due to use of PM timer
time.c: Using 3.579545 MHz WALL PM GTOD PM timer.
time.c: Detected 1804.115 MHz processor.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
Memory: 2059540k/2096576k available (2584k kernel code, 36348k reserved, 1198k data, 220k init)
Calibrating delay using timer specific routine.. 3611.41 BogoMIPS (lpj=18057088)
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
í
Not the wierd character at the end; there's always one or two of
them, but that could just be our Cyclades console servers doing
something odd.
At that point, the machine reboots.
I have found no way yet to get any other behaviour; acpi=off, in
particular, doesn't give me the MCE on this box.
I've tried all your pci= options, too, with no effect.
I tried "nosmp noapic mem=512M ide=nodma apm=off acpi=off desktop
showopts".
I tried iommu=off.
I tried Debian's 2.6.8-11-amd64-generic, which on the 16GiB boxes
went straight to the MCE; it stopped at the same place, but seems to
have hung instead of rebooting. Still didn't get as far as the MCE.
Nothing seems to make a difference.
But 2.6.2 boots right up, no troubles.
Just to make sure that the machines really were the same, I pulled
lspci -v from this smaller-RAM one. They are *exactly the same*.
Right down to the IRQs. You can see them at:
16gb: http://teddyb.org/~rlpowell/media/regular/lkml/lspci_v.txt
2gb: http://teddyb.org/~rlpowell/media/regular/lkml/devnutch1-lspci_v.txt
(you can see they're not the same file, because the whitespace came
out differently :-)
Here's some BIOS options that look maybe relevant, just in case:
4GB Memory Hole Adjust [Auto]
4GB Memory Hole Size [128 MB]
IOMMU: [Enable]
Size: [64 MB]
Multiprocessor Specification: [1.4]
Use PCI Interrupt Entries in MP Table: [Yes]
ACPI Enabled: [Yes]
ACPI SRAT Table [Enabled]
Spread spectrum modulation [No]
Suppress Unused PCI Slot Clocks [No]
-Robin
--
http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/
Reason #237 To Learn Lojban: "Homonyms: Their Grate!"
Proud Supporter of the Singularity Institute - http://singinst.org/
next prev parent reply other threads:[~2006-09-15 23:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-12 22:32 Early boot hang on recent 2.6 kernels (> 2.6.3), on x86-64 with 16gb of RAM Robin Lee Powell
2006-09-14 19:05 ` Same MCE on 4 working machines (was Re: Early boot hang on recent 2.6 kernels (> 2.6.3), on x86-64 with 16gb of RAM) Robin Lee Powell
2006-09-14 19:14 ` Lee Revell
2006-09-14 19:15 ` Robin Lee Powell
2006-09-15 5:42 ` Bharath Ramesh
2006-09-15 17:47 ` Robin Lee Powell
2006-09-15 18:07 ` Robin Lee Powell
2006-09-15 18:22 ` Alan Cox
2006-09-15 18:12 ` Robin Lee Powell
2006-09-18 7:52 ` Andi Kleen
2006-09-18 18:59 ` Robin Lee Powell
2006-09-15 11:45 ` Alan Cox
2006-09-15 18:29 ` Robin Lee Powell
2006-09-15 20:50 ` Alan Cox
2006-09-15 20:31 ` Robin Lee Powell
2006-09-15 23:18 ` Robin Lee Powell [this message]
2006-09-18 7:50 ` Early boot hang on recent 2.6 kernels (> 2.6.3), on x86-64 with 16gb of RAM Andi Kleen
2006-09-18 19:06 ` Robin Lee Powell
2006-09-18 23:58 ` Robin Lee Powell
2006-09-19 6:04 ` Andi Kleen
2006-09-19 6:28 ` Robin Lee Powell
2006-09-19 6:39 ` Andi Kleen
2006-09-19 17:46 ` Robin Lee Powell
2006-09-19 21:07 ` Robin Lee Powell
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=20060915231852.GV4610@chain.digitalkingdom.org \
--to=rlpowell@digitalkingdom.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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®