Date: Tue, 22 Mar 2005 12:24:26 -0600 From: Harry Coin <harrycoin@qconline.com> To: John-Mark Gurney <gurney_j@resnet.uoregon.edu> Cc: freebsd-current@freebsd.org Subject: Re: ATAPICAM? Message-ID: <4.3.2.7.2.20050322121618.01ddbef8@mail.qconline.com> In-Reply-To: <20050322175808.GJ37984@funkthat.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>
next in thread | previous in thread | raw e-mail | index | archive | help
John, Thanks for answering. The relation appears to be some combination of atapicam's interaction with an ata DVD burner and multiple ata controllers. 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. 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! Harry Coin At 09:58 AM 3/22/2005 -0800, John-Mark Gurney wrote: >Harry Coin wrote this message on Tue, Mar 22, 2005 at 07:23 -0600: > > Gary Jennejohn <garyj@jennejohn.org wrote: > > > > >What's with ATAPICAM? > > > > I'm not sure what the issue is with the new ata drivers, but I know > > Atapicam in the context of USB memory chip solid state disk readers and an > > ata DVD burner hangs the bootup process with an interrupt storm right > after > > the hard disks are enumerated and just before the SMP message announcing > > the launch of the second processor would have been displayed. > >atapicam is completely unrelated to USB... atapicam is only used with >ata controlers... which USB is not... USB uses umass to hook into >the cam layer... So I have no clue what you are talking about... > >-- > John-Mark Gurney Voice: +1 415 225 5579 > > "All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.3.2.7.2.20050322121618.01ddbef8>