From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 16:04:44 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 21F0516A4D8 for ; Wed, 21 Jul 2004 16:04:44 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.200]) by mx1.FreeBSD.org (Postfix) with SMTP id C080F43D2F for ; Wed, 21 Jul 2004 16:04:43 +0000 (GMT) (envelope-from joseph.peterson@gmail.com) Received: by mproxy.gmail.com with SMTP id 72so13339rnf for ; Wed, 21 Jul 2004 09:04:43 -0700 (PDT) Received: by 10.38.209.75 with SMTP id h75mr82457rng; Wed, 21 Jul 2004 09:04:43 -0700 (PDT) Message-ID: <38a23c3604072109046e63cdd9@mail.gmail.com> Date: Wed, 21 Jul 2004 11:04:43 -0500 From: Joseph Peterson To: freebsd-current@freebsd.org In-Reply-To: <1090364563.728.3.camel@klamath.syndrom23.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <1090364563.728.3.camel@klamath.syndrom23.de> 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: Wed, 21 Jul 2004 16:04:44 -0000 I have the same issue, err well similar.... ata1-master: FAILURE - ATAPI_RESET no interrupt acd0: CDRW at ata1-master PIO4 This is on a Toshiba Satelite A25-S279. Do you have any problems with burncd? when I use it, I will sometimes get a lockup. What do you have in your loader.conf? On Wed, 21 Jul 2004 01:02:43 +0200, Andreas Kohn wrote: > Hi, > > today I updated my -CURRENT from ~July 5 to July 20 sources. After > reboot with the new kernel, I saw this: > > ata1-master: FAILURE - ATAPI_RESET no interrupt > acd0: CDRW at ata1-master WDMA2 > > With the old kernel, die FAILURE message was not there, but the acd0 was > running in WDMA2 mode as well. > > This is a > atapci0: port > 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on pci0 > controller. > > Is this message to be expected, or should I worry about anything? > > Regards, > Andreas Kohn > > >