From: Jonathan Kamens <jik@kamens.brookline.ma.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16392.734.505550.6731@jik.kamens.brookline.ma.us>
Date: Fri, 16 Jan 2004 10:27:26 -0500
To: linux-kernel@vger.kernel.org
Subject: Re: Updated on UDMA BadCRC errors + subsequent problems (was: Is it safe to ignore UDMA BadCRC errors?)
In-Reply-To: <200401160747.i0G7ln1I000368@81-2-122-30.bradfords.org.uk>
References: <16368.20794.147453.255239@jik.kamens.brookline.ma.us>
	<16389.63781.783923.930112@jik.kamens.brookline.ma.us>
	<16391.24288.194579.471295@jik.kamens.brookline.ma.us>
	<200401160747.i0G7ln1I000368@81-2-122-30.bradfords.org.uk>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 763
Lines: 20

John Bradford writes:
 > Quote from Jonathan Kamens <jik@kamens.brookline.ma.us>:
 > > ... hde: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
 > > ... hde: drive_cmd: error=0x04 { DriveStatusError }
 > 
 > The drive doesn't seem to understand the command it was sent.

I'm not sure what this means, but assuming that it's going to happen
again at some point, what do I need to do to my kernel/configuration
now to be able to capture additional debugging information the next
time it happens?

Thanks,

  jik
-
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/