Hi, Here is the information of HP Proliant ML 370 G4 and trace of panic: ProLiant System BIOS - P50 (11/09/2005) Copyright 1982, 2005 Hewlett-Packard Development Group, L.P. 1024 MB Detected Processor 1 initialized at 3.20 GHz/800 MHz(2MB L2) Processor 2 initialized at 3.20 GHz/800 MHz(2MB L2) Advanced Memory Protection Mode: Advanced ECC Support Redundant ROM Detected - This system contains a valid backup system ROM. 1024 MB Initialized / 1024 MB Detected ProLiant System BIOS - P50 (11/09/2005) Copyright 1982, 2005 Hewlett-Packard Development Group, L.P. Processor 1 initialized at 3.20 GHz/800 MHz(2MB L2) Processor 2 initialized at 3.20 GHz/800 MHz(2MB L2) Advanced Memory Protection Mode: Advanced ECC Support Redundant ROM Detected - This system contains a valid backup system ROM. LSI Logic Corp. MPT BIOS Copyright 1995-2005 LSI Logic Corp. MPTBIOS-5.05.20.00 HP Build <<<Press F8 for configuration options>>> HBA ID LUN VENDOR PRODUCT REV SYNC WIDE CAPACITY --- -- --- -------- ---------------- -------- ----- ---- ------------ 0 0 0 COMPAQ BD1468A4B5 HPB8 80.0 16 146 GB ** 0 7 0 LSILogic LSI1030-IT 1032700 320.0 16 1 7 0 LSILogic LSI1030-IT 1032700 320.0 16 This device has been validated to run at 80MB/s and should support, (**) 320MB/s, when the operating system is loaded. LSI Logic Corp. MPT boot ROM successfully installed! Integrated Lights-Out is disabled. Use the iLO Security Override Switch and iLO F8 ROM-Based Setup Utility to enable iLO functionality. Press "F9" key for ROM-Based Setup Utility Press "F10" key for System Maintenance Menu For access via BIOS Serial Console Press "ESC+9" for ROM-Based Setup Utility Press "ESC+0" for System Maintenance Menu Attempting Boot From CD-ROM Attempting Boot From Hard Drive (C:) -\|/-\|// bboooott..ccoonnffiigg:: --DDhh FFrreeeeBBSSDD//ii338866 bboooott DDeeffaauulltt:: 00::ddaa((00,,aa))//bboooott//llooaaddeerr bboooott:: //--\\||//-- GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 7.0-CURRENT #0: Tue Apr 4 01:16:20 ULAST 2006 tsgan_at_asiatel.micom.mng.net:/usr/obj/usr/src/sys/GW WARNING: WITNESS option enabled, expect reduced performance. MPTable: <HP PROLIANT > Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.20GHz (Unknown-class CPU) Origin = "GenuineIntel" Id = 0xf43 Stepping = 3 Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> Features2=0x641d<SSE3,RSVD2,MON,DS_CPL,CNTX-ID,CX16,<b14>> AMD Features=0x20000000<LM> 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> 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+0x23 cpu_startup(0,c1ec00,c1e000,0,c043d4e5) at cpu_startup+0x14 mi_startup() at mi_startup+0x96 begin() at begin+0x2c db> where 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+0x23 cpu_startup(0,c1ec00,c1e000,0,c043d4e5) at cpu_startup+0x14 mi_startup() at mi_startup+0x96 begin() at begin+0x2c db> c panic: sched_bind: cannot bind non-running thread cpuid = 0 KDB: enter: panic [thread pid 0 tid 0 ] Stopped at kdb_enter+0x2b: nop db> Ganbold Peter Jeremy wrote: > On Tue, 2006-Apr-04 18:24:07 +0900, Ganbold wrote: > >> Peter Jeremy wrote: >> >>> On Tue, 2006-Apr-04 11:07:33 +0900, Ganbold wrote: >>> >>> >>>> 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) >>>> ... >>>> >>>> >>> The indented lines after 'CPU:' are fairly critical as they define >>> what the CPU is reporting which can then be compared to the logic >>> in i386/i386/identcpu.c to see why the CPU isn't being identified. >>> > > Basically, FreeBSD can't identify the CPU and so is panicing. If > you care to post the indented lines after 'CPU:' which you elided, > someone may be able to work out why. > >Received on Wed Apr 05 2006 - 04:27:10 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:54 UTC