From owner-freebsd-current@FreeBSD.ORG Tue Apr 4 08:31:01 2006 Return-Path: X-Original-To: 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 EEE9516A401 for ; Tue, 4 Apr 2006 08:31:01 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC03B43D45 for ; Tue, 4 Apr 2006 08:31:00 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=[192.168.0.18]) by publicd.ub.mng.net with esmtpa (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FQh1Y-0003xf-Sc; Tue, 04 Apr 2006 17:36:28 +0900 Message-ID: <44322EC2.2080700@micom.mng.net> Date: Tue, 04 Apr 2006 17:30:58 +0900 From: Ganbold User-Agent: Thunderbird 1.5 (X11/20060202) MIME-Version: 1.0 To: Scott Long References: <4431D4E5.3080507@micom.mng.net> <4431D9FE.4030602@samsco.org> In-Reply-To: <4431D9FE.4030602@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: CPU class not configured problem in CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 04 Apr 2006 08:31:02 -0000 Scott Long wrote: > Ganbold wrote: >> Hi, >> >> I've got panic "CPU class not configured" on today's CURRENT. >> I have HP Proliant ML370 G4 machine with Xeon CPU 3.20GHz CPU. >> >> When machine tries to boot following message appears: >> ... >> CPU: Intel(R) Xeon(TM) CPU 3.20GHz (Unknown-class CPU) >> ... >> logical CPUs per core: 2 >> panic: CPU class not configured >> cpuid = 0 >> KDB: enter: panic >> [thread pid 0 tid 0 ] >> stopped at kdb_enter+0x2b : nop >> db> >> >> Ganbold >> > > You need to provide the exact kernel config file that you used to > produce this problem. > > Scott I got this trace: db>trace Tracing pid 0 tid 0 td 0xc084ff78 kdb_enter(c0796996) at kdb_enter+0x2b panic(c07b3500,c0c20d74,c072ea1c,c4ace4ec,c08292f0) at panic+0x127 panicifcpuunsupported(c4ace4ec,c08292f0,c0c20d88,c05c3d66,0) at panicifcpuunsupported+0x123 cpu_startup(0,c1ec00,c1e000,0,c043d4e5) at cpu_startup+0x14 mi_startup() at mi_startup+0x96 begin() at begin+0x2c db> Ganbold