Date: Wed, 29 Sep 2010 10:26:35 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: Jurgen Weber <jurgen@ish.com.au> Cc: freebsd-stable@freebsd.org Subject: Re: cpu timer issues Message-ID: <4CA2EA2B.1040706@icyb.net.ua> In-Reply-To: <4CA2B753.4010107@ish.com.au> References: <4CA19F27.6050903@ish.com.au> <4CA1BE59.7060906@icyb.net.ua> <4CA2B753.4010107@ish.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
on 29/09/2010 06:49 Jurgen Weber said the following: > Andriy > > You can find everything you are after here: > > http://pastebin.com/WH4V2W0F Looks like this was with ACPI disabled? Can you try to re-enable it? Also, it doesn't look like the dmesg is verbose. > On 28/09/10 8:07 PM, Andriy Gapon wrote: >> on 28/09/2010 10:54 Jurgen Weber said the following: >>> # dmesg | grep Timecounter >>> Timecounter "i8254" frequency 1193182 Hz quality 0 >>> Timecounters tick every 1.000 msec >>> # sysctl kern.timecounter.hardware >>> kern.timecounter.hardware: i8254 >>> >>> Only have one timer to choose from. >> >> Can you provide a little bit more of "hard" data than the above? >> Specifically, the following sysctls: >> kern.timecounter >> dev.cpu >> >> Output of vmstat -i. >> _Verbose_ boot dmesg. >> >> Please do not disable ACPI when taking this data. >> Preferably, upload it somewhere and post a link to it. > -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CA2EA2B.1040706>