cpu timer issues

Jurgen Weber jurgen at ish.com.au
Wed Sep 29 22:27:32 UTC 2010


Ah, ok. Learn something new everyday. Fantastic. The first time the 
machine stopped during the boot process, but that is ok the 2nd time we 
have success.


I am not sure if ACPI is on, Jeremy you mention below that it should be 
in just by booting with this option so let me know if there are any 
problems there.



On 30/09/10 7:56 AM, Jeremy Chadwick wrote:
> On Thu, Sep 30, 2010 at 07:51:49AM +1000, Jurgen Weber wrote:
>>   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.
>> On 29/09/10 5:29 PM, Jeremy Chadwick wrote:
>>> On Wed, Sep 29, 2010 at 01:49:39PM +1000, Jurgen Weber wrote:
>>>> Andriy
>>>> You can find everything you are after here:
>>>> http://pastebin.com/WH4V2W0F
>>> The information provided here shows ACPI is disabled in addition to the
>>> boot not being verbose.
> When the machine boots (when loader starts), you'll see the FreeBSD logo
> with a menu of choices (boot, boot with ACPI disabled, single user mode,
> etc.).  One of them is boot verbosely; I think it's #5, labelled "Boot
> with verbose logging" or something like that.
> Choose that.  That will cause your machine to boot with ACPI enabled, in
> addition to booting verbosely.  There will be a LOT more information
> printed on the screen during the boot process, and it should be visible
> in /var/log/messages after the machine is started.  This is the
> information we're looking for.
> HTH!

Level 1, 30 Wilson Street Newtown 2042 Australia
phone +61 2 9550 5001   fax +61 2 9550 4001

More information about the freebsd-stable mailing list