From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 12:36:11 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 7F83016A4CE for ; Wed, 21 Jul 2004 12:36:11 +0000 (GMT) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EC9843D62 for ; Wed, 21 Jul 2004 12:36:10 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (8.12.11/8.12.11) with ESMTP id i6LCa6p6090537 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 21 Jul 2004 14:36:06 +0200 (CEST) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.12.11/8.12.5/Submit) id i6LCa6B8090536; Wed, 21 Jul 2004 14:36:06 +0200 (CEST) Date: Wed, 21 Jul 2004 14:36:06 +0200 From: Divacky Roman To: Andreas Kohn Message-ID: <20040721123606.GA90043@stud.fit.vutbr.cz> References: <1090364563.728.3.camel@klamath.syndrom23.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1090364563.728.3.camel@klamath.syndrom23.de> User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) 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: Wed, 21 Jul 2004 12:36:11 -0000 On Wed, Jul 21, 2004 at 01:02:43AM +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 via8235 ata controller was marked as AST broken and doesnt not get timing set anymore... I am not sure whtere this is correct - linux does so... anyway - if its bening dont worry ;) roman