From: "Steven J. Hill" <sjhill@realitydiluted.com>
To: Karol Olechowskii <karol_olechowski@acn.waw.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Athlon XP 1800+ segemntation fault
Date: Mon, 22 Jul 2002 12:39:43 -0500 [thread overview]
Message-ID: <3D3C435F.7080603@realitydiluted.com> (raw)
In-Reply-To: 20020722133259.A1226@acc69-67.acn.pl
Karol Olechowskii wrote:
>
> Few days ago I've bought new processor Athlon XP 1800+ to my computer
> (MSI K7D Master with 256 MB PC2100 DDR).Before that I've got Athlon ThunderBird
> 900 processor and everything had been working well till I change to the new one.
> Now for every few minutes I've got segmetation fault or immediate system reboot.
> Could anyone tell me what's goin' on?
>
I too have the MSI K7D Master. As Alan mentioned, the 2.4.19-rc2-ac2
patch works fine. My machine has been rock solid and I'm running dual
XP 2000+. However, I'm running Radeon 8500 (I refused to give my money
to a company that doesn't release it's drivers). Bad memory is a
possibility, so run 'memtest' and see what happens as mentioned by
others. Also, I suggest you upgrade to v1.3 of the MSI 6501 BIOS which
is always a good idea. As far as your X crashes, you might try building
the latest X out of CVS and see if that helps at all, but it looks
like memory problems. Spend the money and buy good name brand like
Micron/Crucial has been good for me. Just my $0.02.
-Steve
next prev parent reply other threads:[~2002-07-22 17:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 13:32 Athlon XP 1800+ segemntation fault Karol Olechowskii
2002-07-22 11:34 ` Dave Jones
2002-07-22 12:44 ` Alan Cox
2002-07-22 15:46 ` Karol Olechowski
2002-07-22 16:10 ` metf28
2002-07-22 16:30 ` venom
2002-07-22 16:53 ` Giro
2002-07-22 16:59 ` Richard B. Johnson
2002-07-22 22:49 ` Diego Calleja
2002-07-22 14:28 ` Kurt Garloff
2002-07-22 14:49 ` Olivier Galibert
2002-07-22 16:43 ` Alan Cox
2002-07-22 17:39 ` Steven J. Hill [this message]
2002-07-23 0:04 ` [OT] " J Sloan
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=3D3C435F.7080603@realitydiluted.com \
--to=sjhill@realitydiluted.com \
--cc=karol_olechowski@acn.waw.pl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.