From owner-freebsd-stable@FreeBSD.ORG Fri Jan 7 00:26:19 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43CCF16A4CE for ; Fri, 7 Jan 2005 00:26:19 +0000 (GMT) Received: from mail25.syd.optusnet.com.au (mail25.syd.optusnet.com.au [211.29.133.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id A70F743D46 for ; Fri, 7 Jan 2005 00:26:18 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j070QHYu007992 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 7 Jan 2005 11:26:17 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j070QGxP041149; Fri, 7 Jan 2005 11:26:17 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)j070QGRK041148; Fri, 7 Jan 2005 11:26:16 +1100 (EST) (envelope-from pjeremy) Date: Fri, 7 Jan 2005 11:26:16 +1100 From: Peter Jeremy To: Lukas Ertl Message-ID: <20050107002616.GB39552@cirb503493.alcatel.com.au> References: <4379f910050106143641d4613c@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4379f910050106143641d4613c@mail.gmail.com> User-Agent: Mutt/1.4.2i cc: freebsd-stable@freebsd.org Subject: Re: VIA C3 CPU not recognized X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jan 2005 00:26:19 -0000 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 > >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