RE: Really fast clock (diagnosed?)
I think I finally tracked down the why... though I haven't yet confirmed this, nor figured out a fix.
I believe when I switched from apt-get to aptitude it decided I needed acpi functionality. Well, that's all fine and good, but I use APM... so I think now when I wake up after 20 minutes of sleep, APM forwards the clock 20 minutes, and then ACPI does the same thing.
Or perhaps I did something else to get them both running, a setting when I last compiled my kernel perhaps?
Does anyone know how I can verify/fix this problem?
Are
-----Original Message-----
From: Rob Brenart (TT) [mailto:Rob.Brenart@tradingtechnologies.com]
Sent: Tuesday, February 08, 2005 10:41 AM
To: debian-user@lists.debian.org
Subject: RE: Really fast clock
Just adding some information to this, as I'd really like to solve this annoyance!
On wake, this is what's added to dmesg
Warning: CPU frequency is 1600000, cpufreq assumed 600000 kHz.
PCI: Setting latency timer of device 0000:00:1d.0 to 64
PCI: Setting latency timer of device 0000:00:1d.1 to 64
PCI: Setting latency timer of device 0000:00:1d.2 to 64
PCI: cache line size of 32 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: USB 2.0 restarted, EHCI 1.00, driver 26 Oct 2004
PCI: Found IRQ 11 for device 0000:00:1f.1
PCI: Sharing IRQ 11 with 0000:00:1d.2
PCI: Sharing IRQ 11 with 0000:02:02.0
PCI: Found IRQ 11 for device 0000:00:1f.5
PCI: Sharing IRQ 11 with 0000:00:1f.3
PCI: Sharing IRQ 11 with 0000:00:1f.6
PCI: Sharing IRQ 11 with 0000:02:00.1
PCI: Setting latency timer of device 0000:00:1f.5 to 64
PCI: Found IRQ 11 for device 0000:01:00.0
PCI: Sharing IRQ 11 with 0000:00:1d.0
PCI: Sharing IRQ 11 with 0000:02:00.0
PCI: Sharing IRQ 11 with 0000:02:01.0
PCI: Found IRQ 11 for device 0000:02:01.0
PCI: Sharing IRQ 11 with 0000:00:1d.0
PCI: Sharing IRQ 11 with 0000:01:00.0
PCI: Sharing IRQ 11 with 0000:02:00.0
PCI: Enabling device 0000:02:02.0 (0000 -> 0002)
PCI: Found IRQ 11 for device 0000:02:02.0
PCI: Sharing IRQ 11 with 0000:00:1d.2
PCI: Sharing IRQ 11 with 0000:00:1f.1
e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
And it is indeed a problem in KDE and Gnome... and in case it was missed below, it only affects "date" not "hwclock --show"
-----Original Message-----
From: Kent West [mailto:westk@acu.edu]
Sent: Mon 2/7/2005 2:19 PM
To: debian-user@lists.debian.org
Subject: Re: Really fast clock
Rob Brenart (TT) wrote:
>My system has gone nuts, running incredibly fast.
>
<snip>
>When I say way fast, I rebooted, reset the clock in the BIOS, logged in.
>It was correct. I put the system into standby (suspend to RAM), and it
>came back up maybe 8-10 hours later, and was about 12 hours fast.
>
>Earlier in the week I wasn't paying any attention, and when I did look,
>about 4 days later, it was about 6 days fast.
>
>
Is it the system clock ("date") that's running fast, or the hardware
clock ("hwclock --show")?
--
Kent
--
Kent West
Technology Support
/A/bilene /C/hristian /U/niversity
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
It's apparently just the system clock ("date")... the hwclock --show stays fine, until reboot when shutdown rewrites it.
And my latest test shows exactly twice as fast while sleeping (13 minutes in sleep set it 13 minutes fast)
Leaving it to do nothing it seems to do fine.
Does this give me some good info to solving the problem?
Reply to: