From owner-freebsd-bugs@FreeBSD.ORG Mon Jan 22 11:50:24 2007 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8688A16A404 for ; Mon, 22 Jan 2007 11:50:24 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 76E6E13C467 for ; Mon, 22 Jan 2007 11:50:24 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l0MBoOTH043313 for ; Mon, 22 Jan 2007 11:50:24 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l0MBoNCr043308; Mon, 22 Jan 2007 11:50:23 GMT (envelope-from gnats) Date: Mon, 22 Jan 2007 11:50:23 GMT Message-Id: <200701221150.l0MBoNCr043308@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Neil Darlow Cc: Subject: Re: kern/108202: atapicam error after upgrade to 6.2 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Neil Darlow List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 11:50:24 -0000 The following reply was made to PR kern/108202; it has been noted by GNATS. From: Neil Darlow To: bug-followup@FreeBSD.org, neil@darlow.co.uk Cc: Subject: Re: kern/108202: atapicam error after upgrade to 6.2 Date: Mon, 22 Jan 2007 11:49:43 +0000 The errors associated with acd0 were from an attempt to determine if the problem was just SCSI related. I normally access the device as cd0. My bug submission includes many lines associated with cd0 i.e. those starting with (cd0:ata1:0:0:0). Looking further into the cronology of the problem, it appears my write to DVD completed *before* the first (cd0:ata1:0:0:0): READ(10). CDB: 28 0 ff fd 0 0 0 0 1 0 error was reported. After a complete powerdown, and restart, of the system I was able to mount cd0 so it appears the hardware got into a spurious state. Whether that's the fault of poorly designed device firmware, or a buggy driver, frequent power-cycling on a system that is a server is not desirable.