From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 23:47:17 2004 Return-Path: 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 0522A16A4CE for ; Tue, 20 Jul 2004 23:47:17 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 2390B43D41 for ; Tue, 20 Jul 2004 23:47:16 +0000 (GMT) (envelope-from andreas.kohn@gmx.net) Received: (qmail 4161 invoked by uid 65534); 20 Jul 2004 23:47:14 -0000 Received: from unknown (EHLO [212.204.44.203]) (212.204.44.203) by mail.gmx.net (mp001) with SMTP; 21 Jul 2004 01:47:14 +0200 X-Authenticated: #2431876 From: Andreas Kohn To: conrads@cox.net In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-xkqUgx3NAVE8SDv9rbm4" Message-Id: <1090367228.728.7.camel@klamath.syndrom23.de> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 21 Jul 2004 01:47:08 +0200 cc: freebsd-current@freebsd.org Subject: Re: FAILURE - ATAPI_RESET no interrupt in newer current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jul 2004 23:47:17 -0000 --=-xkqUgx3NAVE8SDv9rbm4 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2004-07-21 at 01:22, Conrad J. Sabatier wrote: > On 20-Jul-2004 Andreas Kohn wrote: > > Hi, > >=20 > > today I updated my -CURRENT from ~July 5 to July 20 sources. After > > reboot with the new kernel, I saw this: > >=20 > > ata1-master: FAILURE - ATAPI_RESET no interrupt > > acd0: CDRW at ata1-master WDMA2 > >=20 > > With the old kernel, die FAILURE message was not there, but the acd0 > > was running in WDMA2 mode as well. >=20 > The mode seems to have no bearing on this issue; I get the same in > either PIO4 or WDMA2 modes. >=20 > > This is a=20 > > atapci0: port > > 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on > > pci0 controller. > >=20 > > Is this message to be expected, or should I worry about anything? >=20 > I'm seeing the same (and this is not the first time someone has > reported this, either). >=20 > The drive works normally, it seems, at least for a while. Last night, > I tried playing a DVD in mplayer, and it worked fine until the whole > machine suddenly hung. Hard to say whether or not this is an > ata/atapi issue, or maybe due to the other, well-known preemption > problem that's being discussed here lately. Thank you. The thing is, I have absolutely no problems with this drive. It's just that this message is new, and so made me wonder a little :) Regards, -- Andreas --=-xkqUgx3NAVE8SDv9rbm4 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBA/a78Yucd7Ow1ygwRAjkXAJ9vSmxjNWC4evZxlDWKaizWRJNX3wCgiJ9B vSte4u7PdlYGWOTAkxAAuQA= =A9LF -----END PGP SIGNATURE----- --=-xkqUgx3NAVE8SDv9rbm4--