public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitri <dmitri@users.sourceforge.net>
To: Sampson Fung <sampson@attglobal.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: A Flightening and Strange experience compiling 2.5.58
Date: 19 Jan 2003 10:55:43 -0800	[thread overview]
Message-ID: <1043002544.1982.564.camel@usb.networkfab.com> (raw)
In-Reply-To: <000001c2bfe9$28bf8340$febca8c0@noelpc>

[-- Attachment #1: Type: text/plain, Size: 954 bytes --]

On Sun, 2003-01-19 at 10:32, Sampson Fung wrote:

> Does anyone has similar problems?  That is:  H/W POST do not start after
> machine hangs.

Sure. I have one m/b here that:

a) enters POST only if the planets are in favorable position
b) once running, it sometimes stops unpredictably; then goto a;

I suspect a crack in the m/b, since the RAM was tested in other boxes
and appears to be fine. I already retired this m/b, and it is on its way
to the trash.

Messages that you saw are probably related to some hardware that went
belly up while the box was running, and the code mistook the hardware
failure for some valid condition that only asked for a reset.

Generally, if the box does not enter POST after hard reset then the m/b
or other major components such as RAM or CPU are broken. This is by
definition, because RESET is supposed to reinit all the h/w, and any
memory of the past is not supposed to be there.

Dmitri


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2003-01-19 18:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-19 18:32 A Flightening and Strange experience compiling 2.5.58 Sampson Fung
2003-01-19 18:55 ` Dmitri [this message]

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=1043002544.1982.564.camel@usb.networkfab.com \
    --to=dmitri@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sampson@attglobal.net \
    /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