From owner-freebsd-current@FreeBSD.ORG Wed Sep 12 17:03:26 2007 Return-Path: Delivered-To: current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1704116A417 for ; Wed, 12 Sep 2007 17:03:26 +0000 (UTC) (envelope-from thomas@FreeBSD.ORG) Received: from melamine.cuivre.fr.eu.org (melusine.cuivre.fr.eu.org [82.225.155.84]) by mx1.freebsd.org (Postfix) with ESMTP id B796113C459 for ; Wed, 12 Sep 2007 17:03:25 +0000 (UTC) (envelope-from thomas@FreeBSD.ORG) Received: by melamine.cuivre.fr.eu.org (Postfix, from userid 1000) id 5EF745C50D; Wed, 12 Sep 2007 18:45:35 +0200 (CEST) Date: Wed, 12 Sep 2007 18:45:35 +0200 From: Thomas Quinot To: Patrick Hajek Message-ID: <20070912164535.GA84727@melamine.cuivre.fr.eu.org> References: <20070911210234.GC21433@lbl.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070911210234.GC21433@lbl.gov> X-message-flag: WARNING! Using Outlook can damage your computer. User-Agent: Mutt/1.5.16 (2007-06-09) Cc: claus@endresconsulting.com, current@FreeBSD.ORG, bug-followup@freebsd.org Subject: Re: kern/115614: Recent changes in atapi-cam? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2007 17:03:26 -0000 * Patrick Hajek, 2007-09-11 : > Commenting out atapicam_load="YES" in loader.conf and not precompiled it in > the kernel, the errors disappear. > > dmesg shows: > > d0: 95205MB at ata0-master UDMA100 > acd0: DVDR at ata1-master UDMA33 > > No sense errors. So, it appears to point to the atapi-cam module. Don't jump to conclusions hastily. Just because an error shows up only when ATAPI/CAM is loaded doesn't mean it's necessarily a bug there. > Suggestions? It looks to me like this is similar to the issue described in kern/115614. In general, it's a good habit to first check for an already open PR when you encounter a problem, and to open one if there isn't an existing one. This ensure that the issue and its resolution are properly tracked and do not fall into the cracks. It is all to easy to miss or lose track of an untracked discussion on -current. To help investigate this issue, it would be useful to identify as precisely as possible at what point of 6.2-STABLE it appeared. Also, boot -v output and CAM debugging traces (see "man 4 cam") will be useful. Please preserve subject line and include bug-followup@freebsd.org in all correspondence to ensure a proper audit trail. Thanks! Thomas.