Re: cpu timer issues

Hi

  I do not understand what you mean by a verbose dmesg...... looking at 
the man page there is no verbose option for dmesg except what I 
completed (dmesg -a).

Once that is clarified I can reboot the backup machine and turn on ACPI 
for you.

Thanks

On 29/09/10 5:26 PM, Andriy Gapon wrote:
> 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.
>>
>
>

-- 
-------------------------->
ish
http://www.ish.com.au
Level 1, 30 Wilson Street Newtown 2042 Australia
phone [phone]   fax [phone]
_______________________________________________
[e-mail] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[e-mail]"