From owner-freebsd-stable@FreeBSD.ORG Thu Dec 23 02:20:37 2004 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 3E2A716A4CE; Thu, 23 Dec 2004 02:20:35 +0000 (GMT) Received: from dd3.kasserver.com (dd2718.kasserver.com [81.209.184.159]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9891743D41; Thu, 23 Dec 2004 02:20:32 +0000 (GMT) (envelope-from freebsd@chillt.de) Received: from [192.168.0.5] (dsl-082-083-059-021.arcor-ip.net [82.83.59.21]) by dd3.kasserver.com (Postfix) with ESMTP id 7920289FF3; Thu, 23 Dec 2004 03:20:22 +0100 (CET) Message-ID: <41CA2B6B.8090509@chillt.de> Date: Thu, 23 Dec 2004 03:20:27 +0100 From: Bartosz Fabianowski User-Agent: Mozilla Thunderbird 1.0 (X11/20041208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ruslan Ermilov References: <6.2.0.14.0.20041222134831.101dc3e8@64.7.153.2> <20041222220444.GB12371@ip.net.ua> In-Reply-To: <20041222220444.GB12371@ip.net.ua> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: CPUTYPE changes ? (RELENG_5) 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: Thu, 23 Dec 2004 02:20:38 -0000 Apparently, the CPU type changes have some unintended side effects. For me, they render the system unbootable. I have been investigating what broke my system between a 10th December cvsup and a 20th December one and it boils down to bsd.cpu.mk. I am on a Centrino laptop, which uses a Pentium M (Pentium III with some additional features) CPU. I have CPUTYPE set to "pentium-m". I know this is officially not documented, but bsd.cpu.ml recognizes it and sets the compiler flags accordingly. Unfortunately, something is wrong with the flags. Some feature gets enabled that this CPU does not support and a freshly compiled kernel simply reboots the box on startup. It also affects the boot loader, which shows a register dump for a split second and then reboots the machine as well. I'd love to get to the root of this as currently, it prevents me from keeping my machine up-to-date since anything newer than 15th December leads to an unbootable system :(. - Bartosz