From: Stephen Wille Padnos <stephenwp@adelphia.net>
To: Byron Stanoszek <gandalf@winds.org>
Cc: "David D.W. Downey" <pgpkeys@hislinuxbox.com>,
linux-kernel@vger.kernel.org
Subject: Re: VIA VT82C686X
Date: Wed, 31 Jan 2001 12:13:21 -0500 [thread overview]
Message-ID: <3A7847B1.C8ABDDE1@adelphia.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0101311148560.20840-100000@winds.org>
Byron Stanoszek wrote:
> On Tue, 30 Jan 2001, David D.W. Downey wrote:
>
> > I removed the ide and ata setting. System is running stably as in no
> > kernel crashes, but I am getting daemon and shell crashes. With this
> > current kernel I've had 1 kernel crash in about 3 hours as compared to 1
> > every 10 or 15 minutes. Crash, reboot, 10 minutes or so crash, reboot. ect
> > ect.
> >
> > I'm wanting to test something else out. I'm wondering if there isn't some
> > hardware issue with the RAM. This particular board will do 1GB of PC133,
> > or 2.5GB of PC100. I'm wondering if there isn't something wrong with how
> > it reads the speed and the appropriate limitation. It's running stably if
> > I only run 768MB of PC133 RAM. But if I run a solid 1GB of PC133 I get
> > segfaults and sig11 crashes constantly. All the RAM has been
> > professionally tested and certified.
>
> That definitely sounds like a RAM problem. The system should perform the same
> independent of how many RAM chips you put in there (segfault-wise). If you're
> still in doubt, you can try booting up with memtest86 and run it for several
> hours with only the memory chip that you think might be causing the problem.
>
Even though the motherboard *should* perform the same regardless of the amount
of RAM, it may not. Physically, the refresh needs higher current drive when
there are more modules. I have seen a BIOS option to set the DRAM refresh
current (RAS, CAS settable to 10 or 16 mA each), but that was only on one
motherboard that I can remember - you might want to check for this.
-
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/
next prev parent reply other threads:[~2001-01-31 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 2:59 VIA VT82C686X David D.W. Downey
2001-01-31 3:10 ` Byron Stanoszek
2001-01-31 5:12 ` David D.W. Downey
2001-01-31 17:04 ` Byron Stanoszek
2001-01-31 17:13 ` Stephen Wille Padnos [this message]
2001-01-31 17:49 ` alex
2001-01-31 6:49 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2001-01-31 3:19 Frédéric L. W. Meunier
2001-01-31 6:52 ` Andre Hedrick
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=3A7847B1.C8ABDDE1@adelphia.net \
--to=stephenwp@adelphia.net \
--cc=gandalf@winds.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pgpkeys@hislinuxbox.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