From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: CPU error codes
Date: 6 Feb 2001 20:21:40 -0800 [thread overview]
Message-ID: <95qigk$bje$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.SOL.4.21.0101250913590.15936-100000@orange.csi.cam.ac.uk> <E14Nz6N-0002Vj-00@the-village.bc.nu> <14976.24819.276892.26475@hoggar.fisica.ufpr.br>
Followup to: <14976.24819.276892.26475@hoggar.fisica.ufpr.br>
By author: Carlos Carvalho <carlos@fisica.ufpr.br>
In newsgroup: linux.dev.kernel
>
> Really? I thought it could be because of RAM. Here's the story:
>
> The kernel is 2.2.18pre24.
>
> I'm having VERY frequent of this (sometimes once a day, sometimes once
> a week, sometimes twice a day, on a much used machine)
>
> CPU 1: Machine Check Exception: 0000000000000004
> Bank 4: b200000000040151<0>Kernel panic: CPU context corrupt
>
> CPU 0: Machine Check Exception: 0000000000000004
> Bank 4: b200000000040151<0>Kernel panic: CPU context corrupt
>
> CPU 0: Machine Check Exception: 0000000000000004
> Bank 4: b200000000040151<0>Kernel panic: CPU context corrupt
>
> This is on an ASUS P2B-DS with two PIII 700MHz and 100MHz FSB, 1GB of
> RAM. The mce happens with both processors (the above is just part of
> it).
>
> I've already changed the motherboard and processors, and it continued.
> Then I changed the memory, and it continues. I also changed the
> power supply just in case, to no avail...
>
> It happens with PC100 and PC133 memory. I increased the memory latency
> (the SPD says it's cl2, I put it 3T and 10T DRAM) but the problem
> persists.
>
> Since I changed the main board and processor, I think the most likely
> cause is ram. It seems the x86 can access ram directly, so if there's
> a NMI there what will happen?
>
Much more likely is that your CPU is bad, or overclocked.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
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-02-07 4:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-24 19:30 CPU error codes James Simmons
2001-01-25 1:34 ` Alan Cox
2001-01-25 9:14 ` James Sutherland
2001-01-28 21:29 ` H. Peter Anvin
2001-01-31 15:23 ` Alan Cox
2001-01-31 21:24 ` James Sutherland
2001-01-31 21:33 ` Dan Hollis
2001-02-06 20:39 ` Carlos Carvalho
2001-02-07 4:21 ` H. Peter Anvin [this message]
2001-02-07 8:53 ` Alan Cox
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='95qigk$bje$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--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