From: Clock <clock@twibright.com>
To: Alistair J Strachan <alistair@devzero.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nforce2 lockups
Date: Fri, 15 Aug 2003 23:15:13 +0200 [thread overview]
Message-ID: <20030815231513.A5681@beton.cybernet.src> (raw)
In-Reply-To: <200308151847.20128.alistair@devzero.co.uk>; from alistair@devzero.co.uk on Fri, Aug 15, 2003 at 06:47:20PM +0100
On Fri, Aug 15, 2003 at 06:47:20PM +0100, Alistair J Strachan wrote:
> On Friday 15 August 2003 20:06, Clock wrote:
> [SNIP]
> >
> > I have had three boards with nforce2 replaced (all of them Soltek
> > SL75FRN2-L) and all three did the same. However it seemed the frequency of
> > the crashes varies with actual piece of board.
>
> That's certainly interesting.
>
> >
> > The crashes aren't in software - bare 'cat /dev/hda > /dev/null' is
> > often to lock up the machine to the point that poweroff fails.
>
> [root] 06:43 PM [/home/alistair] time cat /dev/discs/disc0/disc > /dev/null
> (I ctrl-C'd here)
>
> real 1m23.275s
> user 0m0.979s
> sys 0m12.608s
>
> I don't know how obvious the problem is on your machine, but it's clearly not
> an issue on this nForce2. When I was referring to software, that included the
> kernel i.e., I suspect it isn't a design fault.
It seems to occur fairly often just after boot time. When you try later,
you usually fail in an attempt to lockup the machine and have to freshly RESET
(not ctrl-alt-del!) the machine to get the behaviour back.
Cl<
next prev parent reply other threads:[~2003-08-15 19:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <df962fdf9006.df9006df962f@us.army.mil>
2003-08-15 15:15 ` nforce2 lockups 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 [this message]
2003-08-17 19:27 ` Jussi Laako
2003-08-17 20:02 ` Patrick Dreker
2003-08-18 13:28 ` Pavel Machek
[not found] <fa.ih2vscq.35m1rs@ifi.uio.no>
[not found] ` <fa.gbe06ic.1ki851c@ifi.uio.no>
2003-08-17 13:00 ` walt
[not found] <20030817233306.CC67A2D0074@beton.cybernet.src>
2003-08-17 23:41 ` Karel Kulhavý
2003-08-18 8:04 kenton.groombridge
2003-08-18 9:31 ` Ookhoi
2003-08-18 11:00 ` Karel Kulhavý
2003-08-21 1:39 kenton.groombridge
2003-08-21 11:05 ` Patrick Dreker
2003-08-23 1:41 kenton.groombridge
2003-08-23 12:20 Mikael Pettersson
2003-08-23 12:48 ` Patrick Dreker
2003-08-23 15:50 Mikael Pettersson
2003-08-23 18:52 ` Patrick Dreker
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=20030815231513.A5681@beton.cybernet.src \
--to=clock@twibright.com \
--cc=alistair@devzero.co.uk \
--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;
as well as URLs for NNTP newsgroup(s).