mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: DevilKin <devilkin-lkml@blindguardian.org>
To: vda@port.imtp.ilyichevsk.odessa.ua, Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org, Torrey Hoffman <thoffman@arnor.net>
Subject: Re: [2.420] Unexplained repeatable Oops
Date: Tue, 13 May 2003 20:13:39 +0200	[thread overview]
Message-ID: <200305132013.46118.devilkin-lkml@blindguardian.org> (raw)
In-Reply-To: <200305131322.h4DDMSu31637@Port.imtp.ilyichevsk.odessa.ua>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 13 May 2003 15:29, Denis Vlasenko wrote:
> On 12 May 2003 08:21, DevilKin wrote:
> > > Good old VIA chipset. I solved a similar problem by underclocking a
> > > cpu on a similar chipset :-(
> > >
> > > Try the mprime client stress test to ensure your hardware is ok.
> > > www.mersenne.org
> >
> > Ah.
> > Strange thing is that it has worked perfectly for atleast a year,
> > problems only started yesterday morning while I was doing what I've
> > done a zillion times before...
>
> Maybe your AGP card, RAM or mobo AGP chipset is not healthy anymore.
> Cosmic rays etc. 8(

Bah.

Memtest86 gives for both RAM dimms the same problem on the same address. 
I think that 1. both chips are fried, or 2. the bus is fried. I will test the DIMMS in another 
system to make sure.

Thanks for the answers sofar.

Jan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE+wTXWpuyeqyCEh60RAoZSAJ45Gg14HD+E5dlVVMqF3eM/o5pPBQCeNjIg
lL3wx/pvuihyI0eEDnxtasA=
=pXRc
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2003-05-13 18:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-11 18:52 DevilKin-LKML
2003-05-11 21:39 ` Con Kolivas
2003-05-12  5:21   ` DevilKin
     [not found]     ` <200305131322.h4DDMSu31637@Port.imtp.ilyichevsk.odessa.ua>
2003-05-13 18:13       ` DevilKin [this message]
2003-05-13  5:40   ` DevilKin
2003-05-13  5:49     ` Con Kolivas
2003-05-13  6:12       ` DevilKin

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=200305132013.46118.devilkin-lkml@blindguardian.org \
    --to=devilkin-lkml@blindguardian.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thoffman@arnor.net \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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®