Messages in this thread |  | | From | "Matthias Benkmann" <> | Date | Wed, 28 Nov 2001 20:40:02 +0100 | Subject | Re: sym53c875: reading /proc causes SCSI parity error |
| |
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 ?
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |