From owner-freebsd-questions@FreeBSD.ORG Wed Nov 2 17:40:16 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D763916A41F for ; Wed, 2 Nov 2005 17:40:16 +0000 (GMT) (envelope-from jon.brisbin@npcinternational.com) Received: from mail1.npci.com (mail.npcinternational.com [63.76.154.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 876B643D48 for ; Wed, 2 Nov 2005 17:40:16 +0000 (GMT) (envelope-from jon.brisbin@npcinternational.com) Received: from fc63r41.npci.com ([172.16.0.131]) by mail1.npci.com (MOS 3.5.9-GR) with ESMTP id BXT00417 (AUTH via LOGINBEFORESMTP); Wed, 2 Nov 2005 11:34:58 -0600 (CST) Date: Wed, 2 Nov 2005 11:40:19 -0600 From: Jon Brisbin To: freebsd-questions@freebsd.org Message-ID: <20051102114019.52526d07@fc63r41.npci.com> Organization: NPC International X-Mailer: Sylpheed-Claws 1.9.13 (GTK+ 2.6.9; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: 54_STABLE kernel doesn't boot for me X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 17:40:17 -0000 I updated my 5.4 stable source tree yesterday and rolled a new kernel with SMP for my dual Xeon, 2.4GHz PowerEdge. It froze on boot after saying something to the effect: "AS started on CPU #1..." It looks like it recognizes 4 processors (HTT) but it won't ever boot with the SMP kernel. I first thought maybe it was something in ULE, but I put the 4BSD scheduler back in and that didn't fix it. I can boot on my stock, non-SMP kernel and I've turned hyperthreading on, so it can recognize the first one. But the kernel that just has one extra line (options SMP) in it won't boot. There's no logging or anything because it hangs before it can write any of that stuff. I'm not doing anything strange. loader.conf and sysctl.conf only have settings for my hardware and to tweak the time slicing. I'm updating userland stuff now, thinking maybe something in userland broke the new kernel, but I can't figure out what. Any suggestions would be greatly appreciated! :-) -- Thanks! Jon Brisbin Webmaster NPC International, Inc.