Thanks in
2008/7/24 Dimitar Vasilev [EMAIL PROTECTED]
2008/7/24 Kris Kennaway [EMAIL PROTECTED]:
Dimitar Vasilev wrote:
The calcru went backwards message can have two causes:
1) Your time counter really went backwards and is too broken to use.
2) Something caused clock interrupts to
Hi,
I'm having calcru went backwards issues on a machine with the following
config:
MB: MSI K8D Master-F
2xOpteron 242 2.2Ghz
BIOS - от 2005-та
7-stable
areca 1120
8 disks
HDD temperature 28-29 for 1st five, 38-39 for the last 3.
bios is as of 2005 - ami bios or something like this.
Initial
Dimitar Vasilev wrote:
Hi,
I'm having calcru went backwards issues on a machine with the following
config:
MB: MSI K8D Master-F
2xOpteron 242 2.2Ghz
BIOS - от 2005-та
7-stable
areca 1120
8 disks
HDD temperature 28-29 for 1st five, 38-39 for the last 3.
bios is as of 2005 - ami
Michael Powell wrote:
Dimitar Vasilev wrote:
Hi,
I'm having calcru went backwards issues on a machine with the following
config:
MB: MSI K8D Master-F
2xOpteron 242 2.2Ghz
BIOS - от 2005-та
7-stable
areca 1120
8 disks
HDD temperature 28-29 for 1st five, 38-39 for the last 3.
bios is as of
The calcru went backwards message can have two causes:
1) Your time counter really went backwards and is too broken to use.
2) Something caused clock interrupts to be delayed for extremely long
periods of time. This happens if you break to DDB for example. It can also
happen if there are
2008/7/24 Kris Kennaway [EMAIL PROTECTED]:
Dimitar Vasilev wrote:
The calcru went backwards message can have two causes:
1) Your time counter really went backwards and is too broken to use.
2) Something caused clock interrupts to be delayed for extremely long
periods of time. This
Dimitar Vasilev wrote:
The calcru went backwards message can have two causes:
1) Your time counter really went backwards and is too broken to use.
2) Something caused clock interrupts to be delayed for extremely long
periods of time. This happens if you break to DDB for example. It can also
