From owner-freebsd-current@FreeBSD.ORG  Fri Aug 27 19:10:16 2004
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 CFCFE16A4CE
	for <freebsd-current@freebsd.org>;
	Fri, 27 Aug 2004 19:10:16 +0000 (GMT)
Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A7A4A43D31
	for <freebsd-current@freebsd.org>;
	Fri, 27 Aug 2004 19:10:16 +0000 (GMT)
	(envelope-from linimon@lonesome.com)
Received: by mail.soaustin.net (Postfix, from userid 502)
	id 065A8148C1; Fri, 27 Aug 2004 14:10:15 -0500 (CDT)
Date: Fri, 27 Aug 2004 14:10:15 -0500 (CDT)
From: Mark Linimon <linimon@lonesome.com>
X-X-Sender: linimon@pancho
To: "Conrad J. Sabatier" <conrads@cox.net>
In-Reply-To: <20040827105210.49ae3918@dolphin.local.net>
Message-ID: <Pine.LNX.4.44.0408271409230.18407-100000@pancho>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Sat, 28 Aug 2004 11:47:57 +0000
cc: freebsd-current@freebsd.org
Subject: Re: Good news re: sound problem!
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: Fri, 27 Aug 2004 19:10:17 -0000

On Fri, 27 Aug 2004, Conrad J. Sabatier wrote:

> I'm not sure whether this is due to the fact that I had to disable
> ACPI to get the kernel to boot without panicking, or if it has to do
> with having disabled a few of the more esoteric kernel options

It would be interesting to narrow it down -- at least, to try with
the options turned back on.

mcl