From: Ookhoi <ookhoi@humilis.net>
To: kenton.groombridge@us.army.mil
Cc: Patrick Dreker <patrick@dreker.de>,
Jussi Laako <jussi.laako@pp.inet.fi>,
Alistair J Strachan <alistair@devzero.co.uk>,
Clock <clock@twibright.com>,
linux-kernel@vger.kernel.org
Subject: Re: nforce2 lockups
Date: Mon, 18 Aug 2003 11:31:35 +0200 [thread overview]
Message-ID: <20030818093135.GA19937@favonius> (raw)
In-Reply-To: <7a3f387a6ef2.7a6ef27a3f38@us.army.mil>
kenton.groombridge@us.army.mil wrote (ao):
> It seems that the kernel recognizes all nforce2 chipsets as revision
> 162. That is my bad since I found that seemed to be a common
> denominator. Taking shots in the dark. :^)
My Shuttle SN41G2 also has "NFORCE2: chipset revision 162"
> I will tell you that I know it isn't related to bad hardware. I used a
> program that I borrowed from my office (not a cheap program, and it is
> thorough).
> The reason I say this, is that I have read a few posts where one
> person had lock-ups with one distro and not the other. Kernels are
> pretty much the same (I think we are all downloading the latest kernel
> source and building our own kernels), but gcc is different.
I've had a few different 2.5 kernels on this one, compiled under always
up to date debian sid (unstable). The system is (and has been) rock
solid, now running 2.5.70 with an uptime of 70 days. Running
http://www.stanford.edu/group/pandegroup/folding
I get this now and then:
favonius kernel: Bank 2: 940040000000017a
favonius kernel: MCE: The hardware reports a non fatal, correctable
incident occurred on CPU 0.
but this goes unnoticed to me.
This all with an athlon XP 3000+ btw.
next prev parent reply other threads:[~2003-08-18 9:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 8:04 nforce2 lockups kenton.groombridge
2003-08-18 9:31 ` Ookhoi [this message]
2003-08-18 11:00 ` Karel Kulhavý
-- strict thread matches above, loose matches on Subject: below --
2003-08-23 15:50 Mikael Pettersson
2003-08-23 18:52 ` Patrick Dreker
2003-08-23 12:20 Mikael Pettersson
2003-08-23 12:48 ` Patrick Dreker
2003-08-23 1:41 kenton.groombridge
2003-08-21 1:39 kenton.groombridge
2003-08-21 11:05 ` Patrick Dreker
[not found] <20030817233306.CC67A2D0074@beton.cybernet.src>
2003-08-17 23:41 ` Karel Kulhavý
[not found] <fa.ih2vscq.35m1rs@ifi.uio.no>
[not found] ` <fa.gbe06ic.1ki851c@ifi.uio.no>
2003-08-17 13:00 ` walt
[not found] <df962fdf9006.df9006df962f@us.army.mil>
2003-08-15 15:15 ` Clock
2003-08-15 16:38 ` Alistair J Strachan
2003-08-15 19:06 ` Clock
2003-08-15 17:47 ` Alistair J Strachan
2003-08-15 21:15 ` Clock
2003-08-17 19:27 ` Jussi Laako
2003-08-17 20:02 ` Patrick Dreker
2003-08-18 13:28 ` Pavel Machek
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=20030818093135.GA19937@favonius \
--to=ookhoi@humilis.net \
--cc=alistair@devzero.co.uk \
--cc=clock@twibright.com \
--cc=jussi.laako@pp.inet.fi \
--cc=kenton.groombridge@us.army.mil \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@dreker.de \
/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;
as well as URLs for NNTP newsgroup(s).