All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Matthias Benkmann" <haferfrost@web.de>
To: linux-kernel@vger.kernel.org
Subject: Re: sym53c875: reading /proc causes SCSI parity error
Date: Wed, 28 Nov 2001 20:40:02 +0100	[thread overview]
Message-ID: <3C054BA2.9822.8DFF90@localhost> (raw)
In-Reply-To: <3C053AF2.10037.4CCE47@localhost>
In-Reply-To: <xltelmiso7t.fsf@shookay.e-steel.com>

On 28 Nov 2001, at 14:13, Mathieu Chouquet-Stringer wrote:

> I bet it only happens when you're root and you read /proc/scsi/sym53c8xx/0
> (or whatever in your case).
> 
> I had this discussion with Gérard Roudier and it's not a bug, rather a
> feature...

Care to elaborate? What happens when you read that file? And why does it 
cause an error even when the disk is not currently being accessed? As I 
said there can be considerable time between running my script and 
accessing the disk. And why do I get different errors depending on whether 
I access the disk before I run the script or run the script before I 
access the disk?

MSB

----
Who is this General Failure,
and why is he reading my disk ?


  reply	other threads:[~2001-11-28 19:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-28 18:28 sym53c875: reading /proc causes SCSI parity error Matthias Benkmann
2001-11-28 18:14 ` Gérard Roudier
2001-11-28 21:15   ` David S. Miller
2001-11-28 19:51     ` Gérard Roudier
2001-11-28 22:49       ` David S. Miller
2001-11-29 19:40         ` Gérard Roudier
2001-11-28 23:47     ` Alan Cox
2001-11-28 19:13 ` Mathieu Chouquet-Stringer
2001-11-28 19:40   ` Matthias Benkmann [this message]
2001-11-28 19:56     ` Mathieu Chouquet-Stringer

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=3C054BA2.9822.8DFF90@localhost \
    --to=haferfrost@web.de \
    --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 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.