Date: Wed, 03 Nov 2010 15:32:24 +0200 From: Andriy Gapon <avg@icyb.net.ua> To: "Sam Fourman Jr." <sfourman@gmail.com> Cc: current@freebsd.org Subject: Re: calcru: runtime went backwards Message-ID: <4CD16468.8060100@icyb.net.ua> In-Reply-To: <AANLkTikv_JEAp6s_sk67=FYy0fFuNohX=Q_E0kZ-NkFT@mail.gmail.com> References: <AANLkTik=WT=B2BaoJUS%2BD_kguK4_AfRpMG66y0HVr7zJ@mail.gmail.com> <4CD12D29.2060501@phat.za.net> <AANLkTikv_JEAp6s_sk67=FYy0fFuNohX=Q_E0kZ-NkFT@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
on 03/11/2010 12:06 Sam Fourman Jr. said the following: > On Wed, Nov 3, 2010 at 4:36 AM, Aragon Gouveia <aragon@phat.za.net> wrote: >> I recently saw these on a Dell server. It was caused by power saving being >> enabled in the BIOS in a mode where the BIOS takes control instead of >> handing it off to the OS. Disable power saving or set it such that the OS >> has control (and then enable powerd(8) if you like). >> >> > > We disabled AMD C1E support in BIOS (it was Enabled) > now we have not seen this problem for 2 days now. What revision do you run? What is output of kern.eventtimer sub-tree? -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CD16468.8060100>