From owner-freebsd-current@FreeBSD.ORG Wed Mar 23 00:50:12 2005 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 62D6516A4CE for ; Wed, 23 Mar 2005 00:50:12 +0000 (GMT) Received: from S1.cableone.net (smtp1.cableone.net [24.116.0.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB7C543D54 for ; Wed, 23 Mar 2005 00:50:11 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from vixen42.local.lan (unverified [24.119.71.105]) by S1.cableone.net (CableOne SMTP Service S1) with ESMTP id 14153733 for multiple; Tue, 22 Mar 2005 17:50:33 -0700 Date: Tue, 22 Mar 2005 18:49:15 -0600 From: Vulpes Velox To: Harry Coin Message-ID: <20050322184915.2656cde1@vixen42.local.lan> In-Reply-To: <4.3.2.7.2.20050322121618.01ddbef8@mail.qconline.com> References: <4.3.2.7.2.20050322071722.038787d0@mail.qconline.com> <20050322120017.6E90816A4EC@hub.freebsd.org> <4.3.2.7.2.20050322071722.038787d0@mail.qconline.com> <4.3.2.7.2.20050322121618.01ddbef8@mail.qconline.com> X-Mailer: Sylpheed-Claws 1.0.1 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-IP-stats: Incoming Last 0, First 11, in=15, out=0, spam=0 X-External-IP: 24.119.71.105 X-Abuse-Info: Send abuse complaints to abuse@cableone.net cc: John-Mark Gurney cc: freebsd-current@freebsd.org Subject: Re: ATAPICAM? 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: Wed, 23 Mar 2005 00:50:12 -0000 On Tue, 22 Mar 2005 12:24:26 -0600 Harry Coin wrote: > John, > > Thanks for answering. The relation appears to be some combination > of atapicam's interaction with an ata DVD burner and multiple ata > controllers. Actually, IIRC, it should happen with any atapi device if atapi cam is going to have a problem. I would have to check agian, but I don't remember it being related to my DVD burner. > I mentioned the four umass0 devices because that appears to be the > only unusual thing about this box in the storage world. Anyhow > here's a link to the dmesg and conf > showing the problem. HTH. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=78929 > > If whoever it is that knows about atapicam is still around, just do > a search in the freebsd mail lists for atapicam and hanging or > interrupt storms on boot, you'll see there's been a lurking problem > there that hasn't been really addressed since somewhere in late > 4.x. > > I think the reason it's important is that k3b and the programs it > uses can only deal with SCSI appearing burners. If there was an > atapi burner interface directly in the various multimedia program > then atapicam wouldn't be needed at all. > > Right now it's a rock and a hard place, I have to boot another OS > whenever I need to write on CD's or DVD's as it is now. Burncd, for CDs, works nicely. And with out the useless bloat of several of the CD programs. The big problem is the lack of a useful atapi dvd burning program. > Anyhow I hope I'm not barging in the wrong list, I gathered this was > the place to report 5.x system lockups on boot. Excuse the newbie > error! That would be stable and iirc there is also a ata mailing list.