From owner-freebsd-current@FreeBSD.ORG  Thu Nov  6 13:58:53 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 90A2016A4CE
	for <current@freebsd.org>; Thu,  6 Nov 2003 13:58:53 -0800 (PST)
Received: from genius.tao.org.uk (genius.tao.org.uk [212.135.162.51])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C60E043FF7
	for <current@freebsd.org>; Thu,  6 Nov 2003 13:58:50 -0800 (PST)
	(envelope-from joe@genius.tao.org.uk)
Received: by genius.tao.org.uk (Postfix, from userid 100)
	id 6B1FE4D51; Thu,  6 Nov 2003 21:58:49 +0000 (GMT)
Date: Thu, 6 Nov 2003 21:58:49 +0000
From: Josef Karthauser <joe@FreeBSD.org>
To: current@freebsd.org
Message-ID: <20031106215849.GA1129@genius.tao.org.uk>
Mail-Followup-To: Josef Karthauser <joe@FreeBSD.org>,
	current@freebsd.org
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="82I3+IH0IqGh5yIs"
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
Subject: acd0: FAILURE - READ_BIG status=51<READY,DSC,ERROR>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Nov 2003 21:58:53 -0000


--82I3+IH0IqGh5yIs
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

I've been getting a lot of this kind of error from my cdrom drive on a
variety of disks recently:

    acd0: FAILURE - READ_BIG status=3D51<READY,DSC,ERROR> sensekey=3DILLEGA=
L REQUEST error=3D1<ILLEGAL_LENGTH>
    acd0: FAILURE - READ_BIG status=3D51<READY,DSC,ERROR> sensekey=3DILLEGA=
L REQUEST error=3D1<ILLEGAL_LENGTH>
    acd0: FAILURE - READ_BIG status=3D51<READY,DSC,ERROR> sensekey=3DMEDIUM=
 ERROR error=3D0


Is this a bug in the new atapi code or an indication of a hardware fault
that's just developed?

Joe

p.s.:

FreeBSD genius.tao.org.uk 5.1-CURRENT FreeBSD 5.1-CURRENT #135: Tue Nov  4 =
02:01:14 GMT 2003     joe@genius.tao.org.uk:/stable/usr/obj/current/usr/src=
/sys/GENIUS  i386
--=20
Josef Karthauser (joe@tao.org.uk)	       http://www.josef-k.net/
FreeBSD (cvs meister, admin and hacker)     http://www.uk.FreeBSD.org/
Physics Particle Theory (student)   http://www.pact.cpes.sussex.ac.uk/
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D An eclectic mix of fact an=
d theory. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

--82I3+IH0IqGh5yIs
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iEYEARECAAYFAj+qxBgACgkQXVIcjOaxUBYAgwCfdzojS1cfRVkCZK5E4I3g97xP
lNEAn0v1j1N9cInrgNjIT1dGpxb++yVg
=9xQs
-----END PGP SIGNATURE-----

--82I3+IH0IqGh5yIs--