The time keeps changing from GMT to GMT+1 this not only causes the clock to jump but also anything that creates ETA's like wget goes haywire. You cant assign a cron job etc.
Does this happen after reboots only or during any other specific time? are you running any cron jobs currently? (check for your username AND root) atd jobs? Are you dual booting? How long of time is it between setting the correct time to when it is off by an hour? More details are needed.
It happens after random time, however once it had started it will frequently change the time usually every 30 seconds, this makes me think it could be a process. I do dual boot, however I do this very rarely, once a month. I'm not running any cron jobs at the moment, I can't be sure if their going to start. The time doesn't need to be reset it flips to GMT+1 and then after about a second flips back to GMT. This can be seen quite easily on the system clock in KDE
okay... one more question... If you have exited out of xwindows and kde, and are just logged into the console... do you notice the time shift then?
I downloaded a large file with wget recently, just in the console. As the ETA seemed correct It looks like it happens only when in X. KDE is the only window manager I use so it could be X or KDE. Next time it happens I will get a list of all running procceses.
Created attachment 2240 [details] Output of top This is the output of 'top' during the time problems
I think it probably a KDE problem. Once it starts it seems I can trigger it by moving my cursor over the taskbar. In particular the virtual desktop panel.
kde-3.0.2 is the currently released stable version. It appears that you are still running kde-3.0.1 Check out these bug reports for kde... http://bugs.kde.org/db/41/41147.html http://bugs.kde.org/db/42/42713.html Try kde-3.0.2 as developers appear to have fixed some things fairly recently. I also experienced some strange crashes related to the kde date/time applet before I installed kde-3.0.2. Please do an "emerge --clean rsync" and "emerge - -update world" to update your currently installed software which should also update your installation of kde. Please let me know if the problem is still happening after that. -Nick
are things working for you or are you still having problems? Did the upgrade to KDE 3.0.2 help?
I've been doing some tests on my system. It looks like once it's starts it can be triggered by moving over the taskbar but even if KDE is shutdown it will periodicaly happen in console mode. I created a bash script to show me the time every second and I noticed a change. I have upgraded KDE but it still hasn't helped. I though perhapse it could be todo with a mismatch of config files dealing with timezone. timezone info is set in /etc/rc.conf as UTC where else would timezone infomation be stored?
what is your /etc/localtime pointing to? Is it set the same as the timezone setting on the kde clock? If you disable the kde clock does the timezone still change?
I dont have /etc/localtime Should I create it, should it have been created during my stage 3 install? You asked me earlier to do emerge --update world. Do you want me to do this, it could take a few days i'm on a modem.
/etc/localtime is very important. ln -s /usr/share/zoneinfo/{timezone} /etc/localtime from the Gentoo Install doc... 13.Final steps: timezone At this point, you should have a stage3 system that's ready for final configuration. We'll start this process by setting the timezone. By setting the timezone before building the kernel we ensure that users get reasonable uname -a output. Look for your timezone (or GMT if you using Greenwich Mean Time) in /usr/share/zoneinfo. Then, make a symbolic link by typing: Code listing 23 # ln -sf /usr/share/zoneinfo/path/to/timezonefile /etc/localtime Let me know how things go.
Sorry I read the readme file last night and created the file. It didnt stop the problem as it was happening but i've restarted adn well see what happens. I feel so foolish I hope it isnt the cause of the problem I should RTFM.
So how's the system doing now? Problem fixed?
Damm, no it's not fixed. I've just finished doing an update world. My systems been up for about 8 hours and it's just started.
If the problems are continually in kde and you didn't set your proper time on previous occassions then this is my current suggestion for troubleshooting... Seeing as your time is set correctly now and you are doing an update, the new kde release will be built. I would suggest you move your ~/.kde configuration directories to somewhere else temporarily so the new installation can pull in the defaults. Let me know how things go.
I too am losing about 10 minutes for every hour. Judging by the comments on forums.gentoo.org the problem may be related to ide-scsi kernel modules. I am noticing the biggest time lag while ripping oggs from an ide-scsi device.
I am running ide-scsi but it's not critical, only for burning cd's. Do you think it's worth disabling it. I did try upgrading my kernel to gentoo-r7 however it doesn't seem to work with my nvidia driver, yes i have emerged nvidia-kernel again. Is this a kernel bug? I'm not losing time it just flicks back and forward.
I can tell you that I have personal experience with the nvidia drivers and the latest gentoo-sources... It works like a charm, I promise. :) What kind of nvidia card do you have? what version of the nvidia-drivers do you have installed? are you using the nvidia opengl or the xfree opengl? what errors do you find in /var/log/XFree86...log? how's that for starters? :)
Regarding the time flipping problem, it is possible that the kernel module issue could be affecting you. It doesn't sound consistent with the other problem descriptions exactly but close enough to ring some alarms. I'll do a little more research into that bug and see what I come upon.
latest nvidia, nvidia-opengl. Errors says it can't find NVDriver module. Is it worth upgrading the kernel, is this bug fixed in the latest gentoo sources?
I've installed the latest kernel, NVdriver working fine now /usr/src/linux was pointing to r5 and not r7 and confiusing the system. We'll see if this new kernel works, i've disabled SCSI
No, not working
I know we talked about this a couple of days ago... but... If you do a crontab -e as root OR your normal username... are there ANY entries? I know you said that you can't run cron jobs... but did you see if any were actually entered into the crontab? If you have the new kernel, ide-scsi disabled, /etc/localtime set correctly, and you have exited kde, deleted ~/.k* and restarted kde and it still doesn't work... it sounds like a malicious cron job.
I have no running cron jobs.
what about the removal of kde configuration files in your home directory so it recreates your default options? Have you done that? If you have any logs from the time when it is screwing up like /var/log/syslog or something of the like that would give me some sort of idea what the system is doing when the time changes I can maybe give you more clean direction...
Yes i've remove .kde and let it create new files. I'll get some log entrys when it starts again, however It must be a process running with greater privaleges than the user i'm logged on as, this is becuase I cannot change the time.
the only user allowed to change time is root... (possibly and/or someone in the root group?) Or some process that is running with root priveleges. Whatever the case is I look forward to seeing some logs :)
I am now VERY sure that my time lag issue (which might differ from Ross's, or might not) is related to ide-scsi. When I'm ripping CD's via /dev/scsi/host0/bus0/target0/lun0/cd the system clock runs at about half speed. When not ripping it runs at the correct accurate speed. In reading my kernel logs, I see many entries like the following but I'm not sure if it relates at all. Jul 23 15:18:12 [kernel] scsi0 channel 0 : resetting for second half of retries. Jul 23 15:18:12 [kernel] sr0: CDROM (ioctl) error, command: Pause/resume 00 00 00 00 00 00 00 00 00 I am using NVdriver if that matters and the 2.4.19-gentoo-r7 kernel.
I've removed all scsi entries from my kernel now, so if our problems are linked it may be to do with the kernel we are using or the NVdriver. It hasn't happened for a few days, but I wouldn't say its fixed. When it happens ill send some logs.
Created attachment 2680 [details] var log messages output of /var/log/messages after the time stated changing
I think I've solved it, it you look at the log i've sent in it shows the following lines via82cxxx: timeout while reading AC97 codec (0x9A0000) via82cxxx: timeout while reading AC97 codec (0x9A0000) via82cxxx: timeout while reading AC97 codec (0x9A0000) I have noticed this appear once the time problems starts by running dmesg Also in the log the time changes. I think this is it, a kernel bug?
The sound card chipset you are using would most likely be better suited by an ALSA driver. ALSA provides an oss compatibility layer if that is a concern. The kernel sound drivers are less maintained from my experience. I am assuming that you are using a kernel sound driver, correct? The alsa sound module is either snd-via686 or snd-via8233. Let me know what happens when you change the driver from kernel to alsa.
I can't use ALSA with my card. If I enable it I can't get SDL, esound, arts sound to work, it hisses alot, which makes sound on my system almost useless. Is there anythink else I can do?
I think it may be fixed. I used my sound card as a module instead of compiled in. If the bug hasn't show its head within a week i'll mark it as fixed.
Good news to hear! I will watch this thread for further posts.
No It hasn't worked. I tried unloading and re-loading the module but it had no effect.
What hasn't worked? The module wont load or when loaded the module causes time screw ups?
The module loads, it works but eventually the time screws up.
I'm trying to reset /etc/adjtime, how do I do this. I've also been informed the problem could be due to kmix.
"hwclock --adjust" adjusts /etc/adjtime This functionality is taken care of by gentoo's /etc/init.d/clock script. It is taken care of at boot time. OR, run... /etc/init.d/clock restart If you think kmix is the source of the problem then go ahead and disable kmix and let me know what happens for you.
You still around? What's the current report on the problem?
I've adjusted the time, disabled kmix and upgraded the kernel. Still it happens. This is a gentoo problem as i've never had this problem in mandy 8.1.
One thing you might want to try is deleting /etc/adjtime : http://sifter.org/~aglisi/JournalG/20000408.html When you run hwclock --adjust it will be recreated. (Actually I think it gets recreated with many hwclock operations). This may be related to this bug here: http://bugs.gentoo.org/show_bug.cgi?id=4260
I've reset /etc/localtime and /etc/adjtime, they are not the problem. I've been researching this alot. I think it could be todo with my agp board and possible the NVDriver. Currently im using agpart I could switch to the nvidia driver for agp but it has caused problems with my mobo says nvidia. If you can think of a way to trace a process that changes the time please tell me.
looking through logs a possibility is the onboard sound card causing issues. It appears that you are using one of the new VIA chipsets. Get a BIOS upgrade if there is one available. Also if you are using the kernel-based sound driver, I'd suggest using the ALSA driver for your sound card as it is a little more up to date in the ALSA package. No other ideas have surfaced as of yet and the KDE guys here at Gentoo have not seen any issues like this either. Keep me posted.
I have now been running KDE3 for a couple months on multiple systems without experiencing the same problem. This definitely appears to be a hardware specific problem and most likely not gentoo-related.
Strange it didn't hapen when I was running KDE3 on mandrake.
Best thing I can suggest is trying an install with gcc3.2 as your base (from our 1.4_rc1 install cd) optimization settings make a significant difference... especially on a gentoo 1.2 system (gcc2) What are you using for C[XX]FLAGS??? Have you changed at all during the process?
Hi, This might or might not help, in the kernel, Advanced Power Management Bios, Does RTC stores time in GMT?, your system might go in suspend, before it goes, time got convert back to GMT and so time shifts. Or not.
I've disabled the suspend feature, thats not the problem.
do you have acpi enabled in the kernel?
No
The problem is to do with the BIOS of my PC. There can be a conflict between the RTC and my onboard soundcard. I'm currently emailing my vendor to see what I can do about it. Long story, basically the vendors website says OK, flash bios program says it's not supported. I really don't want to fry my chip. Thanks for your help
