From owner-freebsd-current@FreeBSD.ORG Fri Sep 19 10:23:23 2003 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 1F62C16A4B3 for ; Fri, 19 Sep 2003 10:23:23 -0700 (PDT) Received: from MAILSERVER.ofw.fi (ns.ofw.fi [194.111.144.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12B1243FB1 for ; Fri, 19 Sep 2003 10:23:22 -0700 (PDT) (envelope-from dan.naumov@ofw.fi) Received: from [172.16.161.81] by MAILSERVER.ofw.fi (NTMail 7.00.0022/NT1439.00.90501b21) with ESMTP id srnzlaaa for freebsd-current@freebsd.org; Fri, 19 Sep 2003 20:21:57 +0300 From: Dan Naumov To: freebsd-current@freebsd.org In-Reply-To: <20030919182152.A98528@newtrinity.zeist.de> References: <20030918134850.GA22643@student.agh.edu.pl> <200309181354.h8IDsa0F023908@spider.deepcore.dk> <20030918155125.GC22643@student.agh.edu.pl> <20030919182152.A98528@newtrinity.zeist.de> Content-Type: text/plain Message-Id: <1063989720.683.6.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Fri, 19 Sep 2003 20:23:32 +0300 Content-Transfer-Encoding: 7bit Subject: Re: ATAng still problematic 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: Fri, 19 Sep 2003 17:23:23 -0000 On Fri, 2003-09-19 at 19:21, Marius Strobl wrote: > On Thu, Sep 18, 2003 at 05:51:25PM +0200, Jan Srzednicki wrote: > > > > Anyway, here's backtrace for atapicam panic I've mentioned. It's > > triggered by: > > > > cdrecord dev=1,1,0 /some/track > > > > This panic isn't ATAPICAM related. Could you try the patch below? It's > against the cdrtools-devel port but should also work with the cdrtools > port. Hello. I am sorry for "breaking into" this conversation, but I thought it's worthy to report that if I have ATAPICAM enabled in my kernel and have my Lite-On DVD/CDRW Combo Drive attached to the system, today's -CURRENT fails to boot (both single- and multiuser). It gets stuck right after: acd0: CDRW at ata1-master PIO4 Disabling atapicam in the kernel or detaching the drive from the system works around the problem. Sincerely, Dan Naumov