All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Art Haas" <ahaas@airmail.net>
To: sparclinux@vger.kernel.org
Subject: Re: Question about recent copy_user.S change
Date: Sun, 01 Aug 2004 20:04:18 +0000	[thread overview]
Message-ID: <20040801200418.GC7321@artsapartment.org> (raw)
In-Reply-To: <20040801192158.GB7321@artsapartment.org>

On Sun, Aug 01, 2004 at 12:57:41PM -0700, William Lee Irwin III wrote:
> 
> Could you post some system log information about the SCSI errors?
> 

The next time one happens I'll see what I can recover. Usually the
machine is just sailing along happily, then BLAM! From memory I recall
seeing messages like "SCSI Reset", but I don't have any files I can send
along now. Also, the hard-drives in the machine get remounted as
read-only, so all errors usually sent to system logs fail. Once the
error happens the machine is essentially dead and needs rebooting via
the magic Stop-A key combo.

I'd be game for running some filesystem stressing programs if someone
can suggest a good means of capturing the output on a remote machine
when/if the SCSI controller goes boom.

Art Haas
-- 
Man once surrendering his reason, has no remaining guard against absurdities
the most monstrous, and like a ship without rudder, is the sport of every wind.

-Thomas Jefferson to James Smith, 1822

  parent reply	other threads:[~2004-08-01 20:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-01 19:21 Question about recent copy_user.S change Art Haas
2004-08-01 19:57 ` William Lee Irwin III
2004-08-01 20:04 ` Art Haas [this message]
2004-08-02 17:00 ` Tom 'spot' Callaway
2004-08-02 18:09 ` Art Haas
2004-08-02 21:47 ` Question about recent copy_user.S change - with patch Art Haas
2004-08-02 21:51 ` William Lee Irwin III

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=20040801200418.GC7321@artsapartment.org \
    --to=ahaas@airmail.net \
    --cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.