From owner-freebsd-current  Wed Nov 15 12:37:39 2000
Delivered-To: freebsd-current@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.66])
	by hub.freebsd.org (Postfix) with ESMTP
	id 2045B37B4E5; Wed, 15 Nov 2000 12:37:34 -0800 (PST)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.11.0/8.11.0) with ESMTP id eAFKbUR18728;
	Wed, 15 Nov 2000 13:37:31 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA58691; Wed, 15 Nov 2000 13:37:30 -0700 (MST)
Message-Id: <200011152037.NAA58691@harmony.village.org>
To: Mike Smith <msmith@freebsd.org>
Subject: Re: Bad commit? 
Cc: current@freebsd.org
In-reply-to: Your message of "Wed, 15 Nov 2000 12:38:34 PST."
		<200011152038.eAFKcYF04489@mass.osd.bsdi.com> 
References: <200011152038.eAFKcYF04489@mass.osd.bsdi.com>  
Date: Wed, 15 Nov 2000 13:37:30 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <200011152038.eAFKcYF04489@mass.osd.bsdi.com> Mike Smith writes:
: Yes; I think it's broken the resource manager.

I'm testing kirk's fix right now on the laptop in question...

It boots one of the kernels that was always crashing before.  Looks
like we have a winner.

Warner


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message