Date: Wed, 21 Apr 2010 10:04:25 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org, mj@feral.com Subject: Re: FreeBSD kernel doesn't boot on FUJITSU PRIMERGY RX200 S5 server Message-ID: <201004211004.25701.jhb@freebsd.org> In-Reply-To: <4BCE3A52.7060502@feral.com> References: <4BCD5A7B.2070505@FreeBSD.org> <4BCE2E52.1080107@FreeBSD.org> <4BCE3A52.7060502@feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 20 April 2010 7:35:46 pm Matthew Jacob wrote: > On 04/20/2010 03:44 PM, Maxim Sobolev wrote: > > Maxim Sobolev wrote: > >>> Maybe try adding > >>> > >>> hint.atkbdc.0.disabled="1" > >>> hint.atkbd.0.disabled="1" > >>> > >>> to /boot/device.hints? That has reportedly removed minute-long boot > >>> delays on some Nehalem machines. > >> > >> No, that have not helped at all. I measured the delay - it's about 6 > >> minutes from boot command to the first "smap" message. Do you or > >> anybody else have other ideas? > > > > Actually it helped, thank you very much! The problem was that I have > > had my hints compiled into the kernel itself. > > Me too! I can't reproduce this currently, but it would be good to debug this further. My suggestions on how to do this would be to create an array of uint64_t and save TSC values (rdtsc()) into it at specific points in the atkbd/syscons console init. You can then print out the deltas between array entries once the console is fully initialized. Moving the rdtsc() calls around should allow one to determine where in the atkbd/syscons init the long pause is happening. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201004211004.25701.jhb>