From owner-freebsd-current@FreeBSD.ORG  Sun Aug 24 08:37:54 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 9619516A4BF; Sun, 24 Aug 2003 08:37:54 -0700 (PDT)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id A822743FB1; Sun, 24 Aug 2003 08:37:53 -0700 (PDT)
	(envelope-from eischen@vigrid.com)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h7OFbqUK025492;
	Sun, 24 Aug 2003 11:37:52 -0400 (EDT)
Date: Sun, 24 Aug 2003 11:37:52 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
X-Sender: eischen@pcnet5.pcnet.com
To: Soren Schmidt <sos@spider.deepcore.dk>
In-Reply-To: <200308241410.h7OEAUev067489@spider.deepcore.dk>
Message-ID: <Pine.GSO.4.10.10308241133480.23295-100000@pcnet5.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
cc: thomas@freebsd.org
Subject: Re: HEADS UP! ATAng committed
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: deischen@freebsd.org
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Aug 2003 15:37:54 -0000

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