Forum clock

Cadillac · Post by **Cadillac** » Fri Mar 21, 2008 10:51 pm

But Hercule Poirot has discovered something most disturbing indeed.

The forum clock is 10 minutes behind.

FYI I'm not one of those *this will bug me till i die* people, but it confuses me greatly how the time can be so different. (Yes I checked my time is correct.)

Where does the forum clock get its time from?

Post by **Tigereye** » Sat Mar 22, 2008 3:21 am

Hmm, I didn't notice. Thanks for pointing it out.

I don't know off-hand where it's getting its time, but I'll look into it.

EDIT: Fixed

--TE

Cadillac · Post by **Cadillac** » Sat Mar 22, 2008 10:37 am

Semper Vigilans /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />

Post by **BlackViper** » Sat Mar 22, 2008 2:29 pm

It is a conspiracy I say! Now the forums are being lag hacked!

IB_ · Post by **IB_** » Sat Mar 22, 2008 2:38 pm

Was Fuzz on the forums recently? Coz that'd explain it.

Cadillac · Post by **Cadillac** » Sat Mar 22, 2008 2:43 pm

BlackViper wrote:QUOTE (BlackViper @ Mar 22 2008, 02:29 PM) It is a conspiracy I say! Now the forums are being lag hacked!

/laugh.gif" style="vertical-align:middle" emoid=":lol:" border="0" alt="laugh.gif" /> /wub.gif" style="vertical-align:middle" emoid=":iluv:" border="0" alt="wub.gif" />

MrChaos · Post by **MrChaos** » Sat Mar 22, 2008 2:44 pm

IB_ wrote:QUOTE (IB_ @ Mar 22 2008, 09:38 AM) Was Fuzz on the forums recently? Coz that'd explain it.

/laugh.gif" style="vertical-align:middle" emoid=":lol:" border="0" alt="laugh.gif" />

* smack *

Leave fuzzy wuzzy alone IB you big old meanie you

MrChaos <--- appreciates the cleverness

Post by **Tigereye** » Tue Mar 25, 2008 3:39 pm

When investigating the logs of the last forum downtime, I found an interesting section:

Code: Select all

Mar 24 10:18:34 localhost kernel: PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=1
Mar 24 10:18:34 localhost kernel: PCI: Using configuration type 1
Mar 24 10:18:34 localhost kernel: Setting up standard PCI resources
Mar 24 10:18:34 localhost kernel: ACPI: Interpreter enabled
Mar 24 10:18:34 localhost kernel: ACPI: Using IOAPIC for interrupt routing
Mar 24 10:18:34 localhost kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)
Mar 24 10:18:34 localhost kernel: * The chipset may have PM-Timer Bug. Due to workarounds for a bug,
Mar 24 10:18:34 localhost kernel: * this clock source is slow. If you are sure your timer does not have
Mar 24 10:18:34 localhost kernel: * this bug, please use "acpi_pm_good" to disable the workaround

That explains why the clock changed. Since it's a hardware problem, it can't be solved. The only thing to do is get it to sync regularly which it now does.

--TE

fuzzylunkin1 · Post by **fuzzylunkin1** » Sun Mar 30, 2008 1:47 am

I'm on the forums all the time xD.

peet · Post by **peet** » Sun Mar 30, 2008 4:54 pm

Meh, the clock approximately 6 hours wrong, so I don't mind a few minutes more or less.