From owner-freebsd-current@FreeBSD.ORG  Fri Feb 13 03:25:12 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 B596A16A4CE
	for <current@freebsd.org>; Fri, 13 Feb 2004 03:25:12 -0800 (PST)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 17C4C43D1D
	for <current@freebsd.org>; Fri, 13 Feb 2004 03:25:12 -0800 (PST)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id i1DBP7MW034008;
	Fri, 13 Feb 2004 12:25:07 +0100 (CET)
	(envelope-from phk@phk.freebsd.dk)
To: Lukas Ertl <l.ertl@univie.ac.at>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Fri, 13 Feb 2004 12:23:45 +0100."
             <20040213122108.C613@korben.in.tern> 
Date: Fri, 13 Feb 2004 12:25:07 +0100
Message-ID: <34007.1076671507@critter.freebsd.dk>
cc: current@freebsd.org
Subject: Re: New kernel resets immediately 
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, 13 Feb 2004 11:25:12 -0000

In message <20040213122108.C613@korben.in.tern>, Lukas Ertl writes:
>Hi,
>
>I upgraded to the latest world and kernel today and now the new kernel
>can't boot.  The machine resets immediately when the loader tries to load
>the kernel; I tried disabling ACPI (the usual suspect), but that didn't
>help either.  No panic, no error message, just a plain reset/reboot.
>
>Previous kernel was from Feb 6, and that one works fine.

Can you try to back out my syscons commit and see if that is responsible ?

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.