From owner-freebsd-current@FreeBSD.ORG  Tue Aug 26 11:18:24 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 7E69216A4BF
	for <current@freebsd.org>; Tue, 26 Aug 2003 11:18:24 -0700 (PDT)
Received: from mailhub.yumyumyum.org (dsl092-171-091.wdc2.dsl.speakeasy.net
	[66.92.171.91])	by mx1.FreeBSD.org (Postfix) with ESMTP id DFDD443FFB
	for <current@freebsd.org>; Tue, 26 Aug 2003 11:18:21 -0700 (PDT)
	(envelope-from culverk@yumyumyum.org)
Received: by mailhub.yumyumyum.org (Postfix, from userid 1001)
	id 80C8F282; Tue, 26 Aug 2003 14:17:54 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by mailhub.yumyumyum.org (Postfix) with ESMTP
	id 71E6724A; Tue, 26 Aug 2003 14:17:54 -0400 (EDT)
Date: Tue, 26 Aug 2003 14:17:54 -0400 (EDT)
From: Kenneth Culver <culverk@yumyumyum.org>
To: Alfred Perlstein <bright@mu.org>
In-Reply-To: <20030826180902.GO32483@elvis.mu.org>
Message-ID: <20030826141734.W37007@alpha.yumyumyum.org>
References: <20030826180902.GO32483@elvis.mu.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
Subject: Re: atapicam panic at boot.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
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: Tue, 26 Aug 2003 18:18:24 -0000

> free_hcb()
> atapi_action()
> xpt_run_dev_sendq()
> xpt_action()
> probe_start()
> ...
>
I think some people are already tracking this down related to the recent
update of the ata drivers.

Ken