Hardware :: Hwclock (BIOS): Time Set Wrong During Shutdown And Also Reboot?
Nov 15, 2010
System time was drifting ahead increasingly for several days time in the end. This is what I did with the clock about 6 hours "in the future":
Quote:
sntp -P no -r pool.ntp.org
hwclock --systohc
i.e. I got the (more or less) exact time from the time server and set the hardware / BIOS timer with this value.I renamed "/etc/adjtime" to beginn with a clean slate. During reboot (shut down phase) I noticed a message saying something like: "hwclock set to system time". I checked in the BIOS and there was a new time about one hour early(!). The boot phase then reset the time again, this time several hours forward (usually two to six hours). This is an iterating process, with a net gain of several hours per boot. It is not always whole hours -- like in a time zone error but it involves also minutes. System is set to UTC as affirmed by the "date" command. What could be the cause of this behaviour of the clock / timer?
Every time I reboot my computer the system time always comes up exactly 10 hours behind where it should be. So if I reboot it at 16:00 it comes up as 06:00.
This has only been happening since I got back from a trip to Australia, where I naturally changed the computer's timezone to match the local one. I'm now back in Central European Time which is 10 hours behind Australia's. This is on opensuse 11.3.
I've used the YAST date and time tool to set the timezone correctly, and /etc/localtime is set correctly:
Every time I reboot my computer the system time always comes up exactly 10 hours behind where it should be. So if I reboot it at 16:00 it comes up as 06:00.
This has only been happening since I got back from a trip to Australia, where I naturally changed the computer's timezone to match the local one. I'm now back in Central European Time which is 10 hours behind Australia's. This is on opensuse 11.3.
I've used the YAST date and time tool to set the timezone correctly, and /etc/localtime is set correctly:
Further to this LQ thread which Tinkster solved by suggesting the last command (thanks Tinkster) I have been exploring last -x reboot and have found that the reported duration is incorrect for the last reboot and shutdown when a old wtmp file is used. Not having a record for the following shutdown, last assumes that the system has been up until the current time and similarly for the shutdown.
The output comes in time order, latest first, each line showing the time of the reboot and the uptime from then to shutdown. Using last -x reboot shutdown to show the shutdown time, here's an illustration
Code:
shutdown system down 2.6.29.6-smp Sun Mar 7 15:35 - 03:02 (11:27) reboot system boot 2.6.29.6-smp Sun Mar 7 09:35 (05:59) 09:35 until 15:35 is 05:59.
When the uptime exceeds 24 hours it is shown as (<days>+<hours:minutes) like this Code: shutdown system down 2.6.29.6-smp Sun Feb 21 12:39 - 13:20 (00:40) reboot system boot 2.6.29.6-smp Sat Feb 20 09:39 (1+02:59) 09:39 until 12:39 the next day is 1 day 02:59.
The time in parentheses at the end of the shutdown lines is normally the time until the next shutdown.
So far so good. The incorrect output is for the last reboot and shutdown of an old wtmp file. Here's the output of last /var/log/wtmp -x reboot shutdown; last -f /var/log/wtmp.1 -x reboot shutdown
Code:
[snip] reboot system boot 2.6.29.6-smp Fri Mar 12 07:42 (01:54) shutdown system down 2.6.29.6-smp Fri Mar 12 01:31 - 09:37 (08:05) wtmp begins Thu Mar 11 08:25:26 2010 [snip] reboot system boot 2.6.29.6-smp Wed Mar 10 14:12 (15+01:42) shutdown system down 2.6.29.6-smp Wed Mar 10 12:41 - 15:54 (15+03:13) [snip]
The boot started at "Wed Mar 10 14:12" which had an actual uptime of 1 day 11:20 is reported as 15 days 03:13 which is the time from then until the last -f /var/log/wtmp.1 -x reboot shutdown command was issued. The time from shutdown to shutdown is similarly affected.
os vista ultimate ver 6.0.6002sp2ubuntu amd athlon 64x2 dual core pro 5000+ 2.59 ghbios american megatrends v1.6smbios 2.56 g ramnvidia gforce 7900 gt/gtomemorex 5395 cd-r/rw driveVirginia Beach VAyellowsony optiarc dvd rw ad-7190s ata 1.02hd crucial ssd 64ghd ibm deskstarhd wd caviar se 3200aajb 320gi wanted to change to a 64 bit system and was in a hurry, loaded the wrong one, well i finaly got ubuntu back up, vista wont boot, cry cry , its about to be xp, but now im lost in the linux frequency driver gedit, its not a download, how do i install it, ?? im supposed to load the powersaved0.8.19, cpuspeed1.20.1 and cpufreq1.20,,, and im not to the motherboard yet, how do i get even into the processor bios to change them and with what program,,
I installed Ubuntu inside windows(Win 7).Both works good.I found that system time is wrong in both OS.Every time i Change it manually but it changes again on reboot!
Everytime i reboot ubuntu karmic, or shut down then turn on later, it greets me with a screen that says "your bios has detected your computer was sent into hibernation mode due to overheating" of course this is not the case, and the message is very annoying, help? =x
Is there a way to have the system shut down automatically after a set number of wrong user password entries? Am using ubuntu and kubuntu on two different machines. Am thinking it would make sense to have this feature on an encrypted laptop system in case someone were to take it whilst it's on suspend, screenlock, hibernate or login screen and hence the disk is vulnerable.
I have a problem where my PC will stop at the BIOS logo screen after a reboot. The keyboard and mouse don't get power ie no lights. I can power off / on and it will boot normally. The problem started after a fresh install and after installing the updates. ie before updates I could reboot and it was ok. I moved from Slackware and have Win7 and they don't have this problem. Also Ubuntu and Arch rebooted normally when I tried them. I have Opensuse 11.4 x64 on it's own HDD (Samsung F3) The system board is an Asus P8P67 Deluxe (Sandy Bridge) and the HDD is on a SATA3 port. Could it have something to do with the EFI BIOS? Would it be worth trying a newer kernel? it may better support my hardware. I'm hesitant as I don't want to break Lirc as it took awhile to get it working properly on the stock kernel.
Also where can I add '/etc/init.d/lirc restart' so I don't have to run it manually every time time I launch XBMC. I couldn't find 'rc.local'
A couple of days ago I asked why my pc changes the wireless card name.It switches between AR9285 ( right) and AR5008 ( wrong). Well, it is not the case. When system identified with AR9285,it loads ath9k and I can connect to the router. When system identifies my card as AR5008, no kernel module is present at all ( lspci -k). The wrong card name occurs only when system rebooted. If I gracefully shut down the system, it always comes up with a right name for the card( AR9285). So, how to force the system identify my card right no matter if I reboot or shut down?
I just installed Debian6-squeezie and upgraded to wheeny, that went fine for itself But now i discover that Debian INSIST in changing my BIOSCLOCKI realy dont like that. Its MY computer and I dicide MY SELF if i 'follow' winter versus summer time commercial brain-f#ck.
I'm successfully dual booting and running Windows XP and Fedora 11 (with EVERY recent update installed), everything works fine EXCEPT that I cannot get both System times to synchronize.. Evey time I run Fedora I find the system time is always an hour different to Windows. Evert time I correct the system time in Fedora it affects my BIOS time settings. If I then go into Windows I first have to go into the BIOS and correct the BIOS time setting by one hour before I get the correct time in Windows........ Nothing is wrong with my Windows side of things, I know this because if I don't log into Fedora then my system times stay correct, only when I correct the settings in Fedora (which are always an hour out) do I get my BIOS changed. Also in Fedora, although I live in the UK (London) Fedora ALWAYS DEFAULTS TO Guernsey, no matter how many times I correct this to LONDON, Fedora always defaults back to Guernsey.... Has anyone else experienced this as I'm sure it's a Bug in Fedora, surely it shouldn't alter my BIOS settings, should it ??
I want reliable way to print bios clock. Using Redhat 5.5. "hwclock --show" command prints out bios time in local format. So if linux is configured UTC=false when "hwclock --show" is the same as bios clock, but if UTC=true "hwclock --show" still prints local time and I must adjust it according to my TZ - something like `hwclock --show`-2 (only example). So method above depends on UTC setting. Is there an unambigous method to print bios time? (Only os interprets bios time as UTC or local - value of bios time is the same if time is not changed).
I have recently upgraded to the 10.04 Alpha and have been unable to reboot or shutdown. I know it's just an alpha and therefore problems are bound to exist, so I tried reinstalling from a live cd of Alpha 3. But I am still unable to reboot or shutdown.To clarify what happens, I click on shutdown or reboot, the pop-up appears, I click on the shutdown/reboot button and it seems to complete it. It says that processes have been killed and something has exited with 255. But my computer is still on. I am guessing that Ubuntu is shutting down, it's just not actually shutting my computer down or restarting it.
I have a remote server (Xubuntu 10.04) which suffered an electricity brownout yesterday. The server itself is backed with an ups, but it is connected to a external firewire disk, which is not, and this disk malfunctioned as a result of the brownout.
The problem: Now, any process trying to access the external disk freezes and ends up in eternal D state in the process list, including ls and umount. Even trying to ls a directory which contains a symbolic link to a file in that drive just causes ls to freeze. These processes cannot be killed even with SIGKILL, so I proceeded to reboot but...
None of the reboot commands work. Instead they just get added to the ever increasing list of D state processes. I tried (sudo) shutdown -r now, reboot -f now and finally plain shutdown -h now. Is there anything else to try other than ask somebody to actually go to the server and pull the plug (which is not at all trivial)? Some way to tell kernel not to worry about messing stuff up, and just reboot?
we've just bought 30 newest nettops ACER Aspire R3700 with ION 2. I've tried ubuntu, kubuntu, xubuntu. Everything works as expected, but... the first one freezes when trying to reboot, shutdown or enter sleep mode. Checked on several hardware units. The desktop just freezes and nothing happens (ubuntu 10.10, both x32 and amd64). Also no one installs the wi-fi drivers, only ethernet
From a 11.04 Ubuntu, I installed the meta-package xfce4 (*). Now, in the xfce4 session, "suspend" and "logout" (from the xfce4-panel button) works, but "shutdowmn" and "reboot" not, they only lead to GDM. (the shutdowm option there works.)
I tried to solve that by installing the meta-package "xubuntu-desktop" (maybe there are some necessary settings included?), and in fact, the login-screen changed (it's still GDM, I suppose) and there is now a "xubuntu" session, but in that, the probem is just the same: shutdown only leads to the login screen.
In Gnome Classic or Unity, shutdowmn works as it shoulds, so it's not a general problem with my computer.
In Detail, in forst tried to install xfce4 with ubuntu-software-center, but although it seemed to succeed, there was no xfce session. In Synaptic, installing the xfce3 metapackage worked. In fact, software-center seemed to have overlooked some dependencies...
I am facing the issue that the PC not capable to shutdown or reboot; In order to debug that, htop tells me the running processes but all seems normal, I killed few but still cold reset is needed.There is certainly a problem somewhere. the best would be to know which process are weirdly hanging. It could make this testing debian bit better to know which package has these issues.
When I start my computer sometimes I get an error that my floppy drive isn't working and the boot process is halted. So I disabled the floppy disk seek. But Once in a while (sometimes almost every time I start) the BIOS settings are reset and I have to disable floppy disk seek and reorder boot device list again. I have checked the battery and it's fine. What else can be the problem?
Recently I installed Fedora 12 64bit in my HP Compaq 6720s. Among many other problems that I had and I solved with your help, I have the following problem:When I restart or shut-down Fedora 12 it crushes and hangs and only thing that I can do is to stop and restart my laptop by means of ON/OFF button.My question is:Is there any way to see this error (maybe some log file or something) so I can send this message or log file here in this forum and get some help?
I hoping someone can point me in a direction. I installed F13 KDE from the live cd and now when I Shutdown or Reboot, it takes 2 minutes and 8 seconds for the machine to power off. Yes, I timed it.Happens everytime like that. Even when booting from both "mainstream" live cd and the KDE spin live cd. When I hit the Shutdown or Reboot, it goes through the daemons/services shutdown the flashes up the Halting System or Please wait while the system reboots messages (respectivley), turns off the LCD and then just... sits with the power light on and hard drive activity light on. I should mention this is on a Toshiba Laptop about 2 years old now. Intel Chipsets. (Satellite Pro S300M-S2142 if anyone is really curious). The hard drive light stays on for about 1:03 minutes and then it turns off, at 2:08 minutes - the Power light finally turns off and the thing finally shuts down or reboots. If this sounds familiar, it's because it is and I've posted about it with F12 and it's still there with F13. Running kernel-2.6.33.3-85.fc13.x86_64
After a couple of days, some commands related to the disk (df) or files (ls) or killing process (kill -9) doesn't respond. Even I can't reboot or shutdown my server. After an hard reboot, some files are not here anymore or the log files are not filled anymore until I restart.My disk are behind the RAID controller i6 and are configure in RAID 1. The disks are two HP SCSI 72,8GB 10k RPM.Maybe I am totally wrong to check the disk access side, so I am open to other explanation.I can also add that my CPU is running under 1% et my RAM under 10%.
I don't follow why the Suspend option is there and the Reboot and Shutdown is not. Can anyone guide me to the code needed to add the selections. I know I can use a Terminal to shutdown or reboot but a simpler solution would be nice. I expect there are methods to fix most of what I don't like about Gnome 3 but I haven't found them yet. Is there a central place for the solutions needed to deminimalize Gnome 3? I really prefer one click control.
A couple of little niggles seen with KDE4.6. On 32bit install, (openSUSE11.3 was clean install)
-- reboot and shut down do nothing but hibernate and sleep are ok, can only powerdown with su privileges, -- order of applications in plasma bar change after reboot.
On 64bit install, (openSUSE11.3 was update of openSUSE11.2)
-- slow poweroff overcome with new user profile, (no longer a problem with latest update) -- inconsistent mouse curser theme, over desktop theme is Oxygen White, over application windows its DMZ (resolved mouse cursor theme issue on 64bit install. -- /etc/sysconfig, parameter X_MOUSE_CURSOR="DMZ" -- and -- /usr/share/icons/default was a link to DMZ -- /usr/share/icons/default.kde4 was a link to oxygen -- changed so that both were linked to DMZ -- mouse cursor now consistent within windows and across desktop.
On one of my computers that I upgraded from 11.3 to 11.4 with a SSD HDD, it no longer umounts any disks on reboot or shutdown, there are no errors shown, it goes from sending TERM and KILL to rebooting.here is my fstab:
