Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 23 Dec 2004 03:20:27 +0100
From:      Bartosz Fabianowski <freebsd@chillt.de>
To:        Ruslan Ermilov <ru@freebsd.org>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: CPUTYPE changes ? (RELENG_5)
Message-ID:  <41CA2B6B.8090509@chillt.de>
In-Reply-To: <20041222220444.GB12371@ip.net.ua>
References:  <6.2.0.14.0.20041222134831.101dc3e8@64.7.153.2> <20041222220444.GB12371@ip.net.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
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



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