Date: Thu, 8 Nov 2007 10:29:36 -0500 From: Vivek Khera <khera@kcilink.com> To: Jack Vogel <jfvogel@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org>, FreeBSD Stable List <freebsd-stable@freebsd.org> Subject: Re: Bringing up new Intel non-legacy system Message-ID: <EE4DE217-ADF8-4A62-AB01-966DE1E914B9@kcilink.com> In-Reply-To: <2a41acea0711071617p1ec29072y76b6ce662961ab39@mail.gmail.com> References: <2a41acea0711071617p1ec29072y76b6ce662961ab39@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 7, 2007, at 7:17 PM, Jack Vogel wrote: > And, is the ACPI subsystem likely to be the source of the problem? I've had several systems in which I've needed to disable the ACPI timer component and then the system worked fine. in /boot/loader.conf: debug.acpi.disabled="timer" When installing, break to boot loader and type: set debug.acpi.disabled="timer" You can try the various acpi components to isolate which one is the culprit and leave the rest working.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EE4DE217-ADF8-4A62-AB01-966DE1E914B9>