Date: Sun, 24 Aug 2003 11:37:52 -0400 (EDT) From: Daniel Eischen <eischen@vigrid.com> To: Soren Schmidt <sos@spider.deepcore.dk> Cc: thomas@freebsd.org Subject: Re: HEADS UP! ATAng committed Message-ID: <Pine.GSO.4.10.10308241133480.23295-100000@pcnet5.pcnet.com> In-Reply-To: <200308241410.h7OEAUev067489@spider.deepcore.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 24 Aug 2003, Soren Schmidt wrote: > It seems Matt wrote: > > I have just cvsup'd and done a full buildworld/kernel and on reboot had a > > kernel panic. Unfortunatly I do not have ddb or anything compiled into the > > kernel but I can sort this out and get a proper backtrace etc if you don't > > immediatly know what's wrong. > > > > I have the following hardware: > > > > ad0: 76319MB <ST380020A> [155061/16/63] at ata0-master UDMA100 > > acd0: DVD-ROM <Compaq DVD-ROM SD-616T> at ata1-master PIO4 > > acd1: CD-RW <SAMSUNG CD-R/RW SW-240B> at ata1-slave PIO4 > > > > This did work perfectly with the old ATA, but the new ATA panic's. I have > > found that it is due to having device atapicam for the SCSI emulation. If I > > recompile the kernel with this option commented out the kernel boots and > > everything works normally (except the SCSI emulation). > > > > If you need a full panic message and backtrace then I will recompile it with > > debugging options enabled and get one for you. > > This is a case for Thomas I guess, atapicam is his baby I just allow it > to be around :) I appreciate all the work you've done for ATA. But that said, atapicam has been present for a while, and it should have been tested and made to work -- at least so it doesn't panic the system -- before committing ATAng. -- Dan Eischen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10308241133480.23295-100000>