On Sat, Jun 12, 2010 at 8:01 AM, Jeff Dowsley wrote:
> You're not alone. Noticed the calcru messages after a rebuild in May on a
> Compaq PIII, but assumed it wasn't doing any harm, and that it would
> eventually be fixed.
>
> JeffD
>
It appears to be related to VESA, because when support for it
wrote:
On Fri, Jun 11, 2010 at 7:03 AM, Jilles Tjoelker
wrote:
On Fri, Jun 11, 2010 at 12:35:05AM +0800, Jansen Gotis wrote:
Hi, for the past couple of months since moving to RELENG_8 I've been
receiving "calcru: runtime went backwards" messages on the console.
This may w
On Fri, Jun 11, 2010 at 7:03 AM, Jilles Tjoelker wrote:
> On Fri, Jun 11, 2010 at 12:35:05AM +0800, Jansen Gotis wrote:
>> Hi, for the past couple of months since moving to RELENG_8 I've been
>> receiving "calcru: runtime went backwards" messages on the cons
On Fri, Jun 11, 2010 at 12:35:05AM +0800, Jansen Gotis wrote:
> Hi, for the past couple of months since moving to RELENG_8 I've been
> receiving "calcru: runtime went backwards" messages on the console.
> My machine is a dual Pentium III 1.26GHz with an Intel SAI2 board.
Hi, for the past couple of months since moving to RELENG_8 I've been
receiving "calcru: runtime went backwards" messages on the console.
My machine is a dual Pentium III 1.26GHz with an Intel SAI2 board.
Disabling EIST is not an option in my BIOS, and I've tried disabling
th
