From: Jacob Martin <martin@cs.uga.edu>
To: Andi Kleen <ak@muc.de>, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: OOPSes in PREEMPT SMP for AMD Opteron Dual-Core with Memhole Mapping (non tainted kernel)
Date: Sat, 11 Jun 2005 14:31:52 +0000 [thread overview]
Message-ID: <200506111431.52944.martin@cs.uga.edu> (raw)
In-Reply-To: <m1wtp1ch07.fsf@muc.de>
> I think it has or the strange software memhole (what is that?)
> From your oopses i more suspect it is hardware actually:
> > Jun 7 14:11:27 optimator Unable to handle kernel paging request at
> > 00000000000025b0 RIP: Jun 7 14:11:27 optimator
> > <ffffffff8016797a>{pte_alloc_map+170}
>
> It crashes on first accessing newly allocated memory for page tables.
> Most likely something is wrong with your memory or memory map.
> Maybe it is related to your "discrete mtrr mapping" or your "software
> memhole" whatever they are? I would suggest to try without these.
There are three options for Memhole mapping in my BIOS: Disabled, Hardware,
and Software. I really don't know why there would be a "software" option, or
what it does. Also, I'm not sure what the difference between continuous and
discrete MTRR mapping is. The BIOS says it has to do with some linux
kernels, but I haven't found any reliable information about it.
I disabled Memhole mapping and PREEMPT entirely. I'll try to stress test out
some more oopses. I'll also memtest86 all of the memory.
Thanks for the help,
Jake Martin
next prev parent reply other threads:[~2005-06-11 18:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 22:36 PROBLEM: OOPSes in PREEMPT SMP for AMD Opteron Dual-Core with Memhole Mapping (non tainted kernel) Jacob Martin
2005-06-11 10:41 ` Andi Kleen
2005-06-11 14:31 ` Jacob Martin [this message]
2005-06-12 19:29 ` Jacob Martin
2005-06-13 10:06 ` Andi Kleen
2005-06-13 19:53 ` Jacob Martin
2005-06-15 19:51 ` Andi Kleen
2005-06-15 20:46 ` Jacob Martin
2005-06-15 22:33 ` Jacob Martin
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=200506111431.52944.martin@cs.uga.edu \
--to=martin@cs.uga.edu \
--cc=ak@muc.de \
--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