Date: Mon, 16 Jan 2017 11:31:50 -0800 From: John Baldwin <jhb@freebsd.org> To: Hans Petter Selasky <hps@selasky.org> Cc: FreeBSD Current <freebsd-current@freebsd.org>, Konstantin Belousov <kib@freebsd.org> Subject: Re: Strange issue after early AP startup Message-ID: <3466870.vFI8cjabAc@ralph.baldwin.cx> In-Reply-To: <b9c53237-4b1a-a140-f692-bf5837060b18@selasky.org> References: <b9c53237-4b1a-a140-f692-bf5837060b18@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, January 16, 2017 04:51:42 PM Hans Petter Selasky wrote: > Hi, > > When booting I observe an additional 30-second delay after this print: > > > Timecounters tick every 1.000 msec > > ~30 second delay and boot continues like normal. > > Checking "vmstat -i" reveals that some timers have been running loose. > > > cpu0:timer 44300 442 > > cpu1:timer 40561 404 > > cpu3:timer 48462822 483058 > > cpu2:timer 48477898 483209 > > Trying to add delays and/or prints around the Timecounters printout > makes the issue go away. Any ideas for debugging? I have generally used KTR tracing to trace what is happening during boot to debug EARLY_AP_STARTUP issues. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3466870.vFI8cjabAc>