Date: Fri, 19 Sep 2003 20:23:32 +0300 From: Dan Naumov <dan.naumov@ofw.fi> To: freebsd-current@freebsd.org Subject: Re: ATAng still problematic Message-ID: <1063989720.683.6.camel@localhost.localdomain> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Sincerely, Dan Naumov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1063989720.683.6.camel>