From owner-freebsd-current@FreeBSD.ORG  Mon Nov 10 08:29:48 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 1C04416A4CE
	for <current@freebsd.org>; Mon, 10 Nov 2003 08:29:48 -0800 (PST)
Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za
	[146.64.24.58])	by mx1.FreeBSD.org (Postfix) with ESMTP id 3E5B343FDD
	for <current@freebsd.org>; Mon, 10 Nov 2003 08:29:45 -0800 (PST)
	(envelope-from jhay@zibbi.icomtek.csir.co.za)
Received: from zibbi.icomtek.csir.co.za (localhost [IPv6:::1])
	hAAGTdNJ043928
	for <current@freebsd.org>; Mon, 10 Nov 2003 18:29:39 +0200 (SAST)
	(envelope-from jhay@zibbi.icomtek.csir.co.za)
Received: (from jhay@localhost)
	by zibbi.icomtek.csir.co.za (8.12.9/8.12.9/Submit) id hAAGTdsr043927
	for current@freebsd.org; Mon, 10 Nov 2003 18:29:39 +0200 (SAST)
	(envelope-from jhay)
Date: Mon, 10 Nov 2003 18:29:38 +0200
From: John Hay <jhay@icomtek.csir.co.za>
To: current@freebsd.org
Message-ID: <20031110162937.GA43708@zibbi.icomtek.csir.co.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Subject: diskless panic with new interrupt code
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: Mon, 10 Nov 2003 16:29:48 -0000

Hi,

My old diskless dual Pentium I 100MHz system does not like the latest
code. I use etherboot to boot it. I have tried both an UP and SMP kernel
but it panic in the same way. Looking at the low address values, it
looks as if it happens very early. Maybe something depends on the
loader initializing things nowadays? A kernel of about 2 weeks ago
did boot without a problem, even an SMP one.

On bootup this is what I see:

#########################################
WARNING: loader(8) metadata is missing!
instruction pointer	= 0x0:0xa00
stack pointer		= 0x0:0xffe
frame pointer		= 0x0:0x0
code segment		= base 0x0, limit 0x0, type 0x0
			= DPL 0, pres 0, def32 0, gran 0
processor eflags	= interrupt enabled, vm86, IOPL = 0
current process		= 0 ()
kernel: type 30 trap, code=0
Stopped at	0xa00:	cli
db>
#########################################

John
-- 
John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org