Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 7 Jan 2005 11:26:16 +1100
From:      Peter Jeremy <PeterJeremy@optushome.com.au>
To:        Lukas Ertl <lukas.ertl@gmail.com>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: VIA C3 CPU not recognized
Message-ID:  <20050107002616.GB39552@cirb503493.alcatel.com.au>
In-Reply-To: <4379f910050106143641d4613c@mail.gmail.com>
References:  <4379f910050106143641d4613c@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2005-Jan-06 23:36:43 +0100, Lukas Ertl wrote:
>5.3-STABLE refuses to recognize my VIA C3 CPU, it panics immediately
>after the loader with
>
>CPU class not configured
>
>Last known working kernel is from Sun Nov  7 16:27:23 CET 2004, it
>recognizes the CPU as
>
>CPU: VIA C3 Samuel 2 (601.37-MHz 686-class CPU)
>  Origin = "CentaurHauls"  Id = 0x673  Stepping = 3
>  Features=0x803035<FPU,DE,TSC,MSR,MTRR,PGE,MMX>
>
>The new kernel says it's an "unknown class" CPU.

The exact message may help diagnose what has gone wrong.

>  I haven't changed my
>kernel config since I built the old kernel, so maybe I have overlooked
>some new option for VIA CPUs, but I couldn't find a change at first
>glance.

FWIW, I can't see anything that has changed.

Assuming you've double-checked the obvious things (like both kernels
really were built using the same config file and you're updating along
the correct branch), I'd suggest you either need to do a binary search
between 7th November and now to work out what broke, or (if "boot -d"
enters the debugger early enough) spend some time with DDB working out
why the CPU ident code no longer works for you.

The relevant files are: 
/sys/i386/i386/identcpu.c
/sys/i386/i386/initcpu.c
/sys/i386/i386/locore.s

-- 
Peter Jeremy



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050107002616.GB39552>