Date: Fri, 19 Sep 2003 19:07:51 -0400 (EDT) From: Bryan Liesner <bleez@comcast.net> To: Dan Naumov <dan.naumov@ofw.fi> Cc: Soren Schmidt <sos@spider.deepcore.dk> Subject: Re: ATAng still problematic Message-ID: <20030919190341.E458@gravy.homeunix.net> In-Reply-To: <1063989720.683.6.camel@localhost.localdomain> References: <20030918134850.GA22643@student.agh.edu.pl> <20030918155125.GC22643@student.agh.edu.pl> <1063989720.683.6.camel@localhost.localdomain>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 19 Sep 2003, Dan Naumov wrote: > 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 <LITE-ON COMBO LTC-48161H> at ata1-master PIO4 > > Disabling atapicam in the kernel or detaching the drive from the system > works around the problem. I'm seeing this too. it happened right after the commit of ata-queue.c rev 1.5. Revert back to version 1.4 and see if boots again. -- ============================================================= = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = bleez@comcast.net Home of the Gipper = =============================================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030919190341.E458>