From owner-freebsd-current@FreeBSD.ORG Sat Jul 3 18:40:05 2004 Return-Path: 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 EA6E916A4CE; Sat, 3 Jul 2004 18:40:05 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E8E043D45; Sat, 3 Jul 2004 18:40:05 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i63IdbRL024357; Sat, 3 Jul 2004 14:39:37 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i63Idbk7024354; Sat, 3 Jul 2004 14:39:37 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sat, 3 Jul 2004 14:39:37 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Thomas T. Veldhouse" In-Reply-To: <40E6D627.3030308@veldy.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: src-committers@freebsd.org cc: current@freebsd.org cc: cvs-src@freebsd.org cc: cvs-all@freebsd.org cc: Steve Kargl cc: Kris Kennaway Subject: Re: HEADSUP: Native preemption added to the kernel scheduler X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jul 2004 18:40:06 -0000 On Sat, 3 Jul 2004, Thomas T. Veldhouse wrote: > No such problem. I simply added NULL myself, by hand. It compiles > fine, but the kernel panics on boot. Hmm. I couldn't find the panic information in your e-mail (such as panic message) or previous messages. If I missed it, could you forward it to me via private e-mail; if I didn't, could you resend the report with documentation of the panic? Some initial instructions on providing post-mortem information on a panic can be found in the handbook. At minimum, the panic string is useful, but if it's a page fault, the faulting address would also be important, along with (ideally) stack trace and surrounding text. Thanks, Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research