Bug 139582 - Clock silently "wins" time - e.g. 5 Minutes each boot ...
Summary: Clock silently "wins" time - e.g. 5 Minutes each boot ...
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Other (show other bugs)
Version: Final
Hardware: i686 SuSE Linux 10.0
: P5 - None : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-16 13:11 UTC by Michael Schwaderer
Modified: 2005-12-23 12:31 UTC (History)
0 users

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Clock configuration file (486 bytes, text/plain)
2005-12-21 05:23 UTC, Michael Schwaderer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Schwaderer 2005-12-16 13:11:39 UTC
Everytime the system boots, the clock silently "wins" roghly 5 Minutes and need a new setup. No extraordinary software is installed - everything was set up "out of the box".

Also, a complete new installation didn´t resolve this problem - it appears at every system start.

Hardware:
PentiumM (745 - Dothan)
Intel855PM + FW82801DBM [ICH4M] (with integrated Audio, Modem, USB2.0 Controller)
2 x 512MB PC2700 DDRRAM
ATI Mobility Radeon 9700, 256MB, 4 x AGP (fglrx installed and configured)
VIA VT1612A
IntelPRO 2200 MiniPCI
Realtek RTL8100CL
TI TSB43AB22A (IEE1394)
OZ711MC1 (yes, it works ...)
Comment 1 Michael Gross 2005-12-19 17:13:39 UTC
This is most likely a drift-time problem. Please attach the file /etc/sysconfig/clock here. This might be caused by an invalid time zone configuration.
Comment 2 Michael Schwaderer 2005-12-21 05:23:01 UTC
Created attachment 61520 [details]
Clock configuration file

File looks OK - by me ...
Comment 3 Michael Gross 2005-12-21 09:58:32 UTC
Please check what time is set in your BIOS before any OS is booted, then the time after booting (check out with `date'). Further, please paste the content of the file /etc/adjtime.
Comment 4 Michael Gross 2005-12-21 11:59:17 UTC
This problem is likely caused by lost timer interrupts due to much USB load or some other quality reasons of your mainboard. You might either synchronize your clock using NTP or you can disable the rc-script that synchronizes the hardware clock (/etc/init.d/boot.clock).

Please notice that this is not a bug in the matter of speaking but a problem that derives from hardware insufficiencies. In the next release, there will be a variable in /etc/sysconfig/clock that makes it easy to disable the boot.clock script which should solve the problem for such users.
Comment 5 Michael Schwaderer 2005-12-23 12:31:53 UTC
After some investigation, I think it depends on an old VMware installation (no one told me about that) which wasn't properly removed. The USB2.0 interfaces were "downgraded" to USB1.1-Speed with the behavior like an insufficient mainbord or chipset. After updating the Kernel a few minutes ago, the problem is gone. I reported this to VMware - perhaps it's an unknown bug within VMware5.5.
Thank you very much for your support.
Merry Christmas and a happy new year.