From: Harold Oga <ogah@shaw.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Random (hard) lockups
Date: Mon, 30 Jul 2001 18:37:10 -0600 [thread overview]
Message-ID: <20010730183710.A680@ogah.cg.shawcable.net> (raw)
In-Reply-To: <419E5D46960FD211A2D5006008CAC79902E5C3ED@pcmailsrv1.sac.unify.com> <Pine.LNX.4.30.0107301424580.21409-100000@anime.net>
In-Reply-To: <Pine.LNX.4.30.0107301424580.21409-100000@anime.net>
On Mon, Jul 30, 2001 at 02:31:49PM -0700, Dan Hollis wrote:
>On Mon, 30 Jul 2001, Manuel A. McLure wrote:
>> I am seeing something very similar on my K7T Turbo/Athlon 900/256M PC133
>> SDRAM (note to Dan, the K7T Turbo is an SDRAM mobo, not DDR)
>
>Hmm. I have an MSI pro2-A which works fine with K7 optimizations...
>tbird900, 256mb sdram...
>
>May very well be a hardware design flaw. The pro2-a appears very carefully
>engineered to keep most traces short and they went through a lot of effort
>to keep traces the same length.
>
>The only stability problems I've had were overloading the 300W PS with a
>geforce2, all 6 PCI slots filled, 3 HD, 1 CDRW, and one DVDrom. Removing
>one of the drives (CDRW or DVDrom) lowers the power consumption back into
>the realm of 100% stability.
>
>Next on my shopping list is a 450W PS :-)
>
>Has anyone tried swapping buffered/unbuffered DIMMs to see if it made a
>difference?
>
>-Dan
Hi,
I also have a pro2a with no problems. However, the pro2a has a KT133,
and all the problems I've seen reported on the list seem to be with the
KT133A or KT266. Maybe its only a problem with chipsets that support
266FSB. Just tossing out ideas here.
-Harold
--
"Life sucks, deal with it!"
next prev parent reply other threads:[~2001-07-31 0:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 21:17 Manuel A. McLure
2001-07-30 21:31 ` Dan Hollis
2001-07-31 0:37 ` Harold Oga [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-29 18:34 James A. Treacy
2001-07-29 18:49 ` Alan Cox
2001-07-30 20:21 ` Kurt Garloff
2001-07-30 20:46 ` Dan Hollis
2001-07-30 21:36 ` Kurt Garloff
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=20010730183710.A680@ogah.cg.shawcable.net \
--to=ogah@shaw.ca \
--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®