From owner-freebsd-current@FreeBSD.ORG  Thu Feb 12 09:38: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 1E82C16A4CE; Thu, 12 Feb 2004 09:38:16 -0800 (PST)
Received: from fisk.demonized.net (h97n2fls33o834.telia.com [213.66.186.97])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 7988B43D1F; Thu, 12 Feb 2004 09:38:15 -0800 (PST)
	(envelope-from manlix@demonized.net)
Received: from beard.demonized.net (beard.demonized.net [172.22.1.2])
	by fisk.demonized.net (8.12.10/8.12.10) with SMTP id i1CHcL3d095465;
	Thu, 12 Feb 2004 18:38:21 +0100 (CET)
	(envelope-from manlix@demonized.net)
Date: Thu, 12 Feb 2004 18:38:14 +0100
From: Johan Pettersson <manlix@demonized.net>
To: freebsd-current@freebsd.org
Message-Id: <20040212183814.7ab9adfd.manlix@demonized.net>
In-Reply-To: <20040211025317.13af3d36.manlix@demonized.net>
References: <20040211025317.13af3d36.manlix@demonized.net>
X-Mailer: Sylpheed version 0.9.9 (GTK+ 1.2.10; i386-portbld-freebsd5.2)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: Bad interrupt routing causes my SATA controller to fail.
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: Thu, 12 Feb 2004 17:38:16 -0000

I noticed another thing... wheen rebooting it hangs in all cases just after the uptime message is printed, except when apic is disabled. With hint.apic.0.disabled set to 1 it reboots as it should.