From: Ronald G Minnich <rminnich@lanl.gov>
To: "Eric W. Biederman" <ebiederman@lnxi.com>
Cc: Andrew Stanley-Jones <asj@amphus.com>,
linux-mm@kvack.org, LinuxBIOS <linuxbios@lanl.gov>,
Jim Bailey <jbailey@amphus.com>
Subject: Re: 2.4.2 kernel weirdness
Date: Mon, 19 Mar 2001 20:42:45 -0700 (MST) [thread overview]
Message-ID: <Pine.LNX.4.30.0103192040380.666-100000@white.acl.lanl.gov> (raw)
In-Reply-To: <m3d7bdmkp7.fsf@DLT.linuxnetworx.com>
On 19 Mar 2001, Eric W. Biederman wrote:
> Andrew Stanley-Jones <asj@amphus.com> writes:
>
> > I wasn't confident of the SDRAM setup on an embedded 486 machine, so I
> > wrote a user space program to write and read mem to make sure everything
> > was ok. Well when the program runs almost instantly it generates a oops
> > (with eip in schedual). Assuming SDRAM setup was bad I added various
> > checks in boot up to read and write mem. They didn't show any problems,
> > I can read and write all I like, the mem works.
I think your memory is misconfigured. This problem looks suspiciously like
you only really have about 8M actually working, i.e. you're saying you
have 64m but you're getting address line wrap such that you're trashing
low kernel memory. This can happen with a misconfigured north bridge. That
might explain why falling over the 4M boundary is killing you. Not sure
though.
ron
--
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.eu.org/Linux-MM/
prev parent reply other threads:[~2001-03-20 3:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-19 17:25 Andrew Stanley-Jones
2001-03-19 22:56 ` Eric W. Biederman
2001-03-20 3:42 ` Ronald G Minnich [this message]
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.30.0103192040380.666-100000@white.acl.lanl.gov \
--to=rminnich@lanl.gov \
--cc=asj@amphus.com \
--cc=ebiederman@lnxi.com \
--cc=jbailey@amphus.com \
--cc=linux-mm@kvack.org \
--cc=linuxbios@lanl.gov \
/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