I have a 326m running 3.9/amd64 for months without a glitch. Dmesg
below. Perhaps something changed after 3.9 that causes the before
mentioned problems.
OpenBSD 3.9-stable (GENERIC.MP) #7: Mon Aug 21 10:28:18 CEST 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 214
Last update.
The only thing that I also saw what this clock:
In normal operation:
cpu0: apic clock running at 199MHz
Before a reboot when I have the problem:
cpu0: apic clock running at 678MHz,
But this is not always the same value.
Anyway, that's all I have.
Not a huge deal, I can always
Ronnie Garcia wrote:
Daniel Ouellet a icrit :
But luck I happen to monitor the sessions and realize that the clock
on the server run about 1/4 of real time.
Everything run 1/4 of what it should be.
Ping answer oneping each 4 seconds instead of one.
Top refresh every 20 seconds instead of 5,
Daniel Ouellet a icrit :
But luck I happen to monitor the sessions and realize that the clock on
the server run about 1/4 of real time.
Everything run 1/4 of what it should be.
Ping answer oneping each 4 seconds instead of one.
Top refresh every 20 seconds instead of 5, etc.
[...]
dmesg b
I had various problem with my bgpd as session were dropping and couldn't
figure out why that was.
But luck I happen to monitor the sessions and realize that the clock on
the server run about 1/4 of real time.
Everything run 1/4 of what it should be.
Ping answer oneping each 4 seconds instead
5 matches
Mail list logo
