From owner-freebsd-current@FreeBSD.ORG  Fri Dec 19 12:58:29 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 7E6EB16A4CF
	for <current@freebsd.org>; Fri, 19 Dec 2003 12:58:29 -0800 (PST)
Received: from amsfep16-int.chello.nl (amsfep16-int.chello.nl [213.46.243.26])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 71DA943D45
	for <current@freebsd.org>; Fri, 19 Dec 2003 12:58:24 -0800 (PST)
	(envelope-from dodell@sitetronics.com)
Received: from sitetronics.com ([213.46.143.85]) by amsfep16-int.chello.nl
	ESMTP
	<20031219205819.EDZT16196.amsfep16-int.chello.nl@sitetronics.com>;
	Fri, 19 Dec 2003 21:58:19 +0100
Date: Fri, 19 Dec 2003 21:58:10 +0100
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
To: Devon H.O'Dell <dodell@sitetronics.com>
From: Devon H.O'Dell <dodell@sitetronics.com>
In-Reply-To: <CD97E383-3264-11D8-9245-000502C708CB@sitetronics.com>
Message-Id: <0DE5B096-3266-11D8-9245-000502C708CB@sitetronics.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.553)
cc: Peter Schultz <pmes@bis.midco.net>
cc: current@freebsd.org
Subject: Re: Ghetto-debug in new -CURRENT with SCSI controller
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, 19 Dec 2003 20:58:29 -0000

>> You should be able to get it to work by disabling ACPI at boot.
>
> Strange, I thought I had tried that at some point and it hadn't 
> worked. I was apparently not paying attention when I attempted to do 
> so. It works without ACPI which I don't really need anyway. Thanks a 
> ton!
>
> --Devon
>

Ah right, finding the problem I had when disabling ACPI: the machine 
locks up at some point (no set time, sometimes it locks in boot and 
sometimes it locks in userland) no longer accepting input from the KB; 
any network activity appears on the link light but no packets are sent 
back. No panics appear and the machine does not reboot -- it just 
hangs. I don't have this problem in the kernel from a couple weeks ago 
(sorry, I didn't bother to mark the date :\ but it's within 3-4 weeks 
ago) with or without ACPI enabled.

--Devon