Mailinglist Archive: opensuse-bugs (5344 mails)
| < Previous | Next > |
[Bug 278621] System time (clock) is not accurate.
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Thu, 7 Jun 2007 03:36:13 -0600 (MDT)
- Message-id: <20070607093613.9A304CC782@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=278621
ak@xxxxxxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEEDINFO
Info Provider| |mike_wells@xxxxxxx
------- Comment #9 from ak@xxxxxxxxxx 2007-06-07 03:36 MST -------
The problem is unlikely to be in KDE, which just gets the time
from the kernel, but either hardware or some
low level interaction with your hardware/BIOS combination. Since
we don't have access to your particular system we require you
to run some tests because it is unlikely it can be reproduced elsewhere
(and even if it could be it wouldn't be clear if it was the same problem)
That is different from other non hardware near software you
might have experience with.
It could be just broken hardware. Some PC chipsets are very bad time keepers.
You could try to boot with "noapic" and if that doesn't help
afterwards with notsc and see if that avoids the drift.
If yes please attach hwinfo output from the working boot.
Also did you see the same problem with older releases?
Also running NTP would be a likely workaround.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
ak@xxxxxxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEEDINFO
Info Provider| |mike_wells@xxxxxxx
------- Comment #9 from ak@xxxxxxxxxx 2007-06-07 03:36 MST -------
The problem is unlikely to be in KDE, which just gets the time
from the kernel, but either hardware or some
low level interaction with your hardware/BIOS combination. Since
we don't have access to your particular system we require you
to run some tests because it is unlikely it can be reproduced elsewhere
(and even if it could be it wouldn't be clear if it was the same problem)
That is different from other non hardware near software you
might have experience with.
It could be just broken hardware. Some PC chipsets are very bad time keepers.
You could try to boot with "noapic" and if that doesn't help
afterwards with notsc and see if that avoids the drift.
If yes please attach hwinfo output from the working boot.
Also did you see the same problem with older releases?
Also running NTP would be a likely workaround.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
| < Previous | Next > |