Red Hat Bugzilla – Bug 322351
firstboot hangs after set date&time
Last modified: 2008-02-06 12:56:32 EST
Description of problem: Version-Release number of selected component (if applicable): How reproducible: always? Steps to Reproduce: 1. boot for the first time 2. firstboot, set date&time and click forward 3. Actual results: system hangs, mouse doesn't move. Only way out is to press the power button. Expected results: Additional info: fedora 8 test 3 x86_64 on HP dv9000z series laptop. I had to use the interactive startup to boot. platform x86_64?
Are you using rhgb or not? Most people are, but if you have removed the rhgb option from your kernel boot parameters or didn't install the package (because you deselected it, did a text mode install, etc.) then you're not.
yes, using rhgb. Just guessing here, could it be problem contacting the time server? Right now kde clock is unable to contact time server.
Perhaps there's something we can do regarding timeouts and error handling in system-config-date, then.
I can't think of why contacting the time server should cause the mouse to hang, it shouldn't even cause the GUI to not refresh. Riku, did you enable NTP in the firstboot step? If yes, can you check if running system-config-date normally (i.e. not from within firstboot, but all other settings similarly) works?
Just tested system-config-date, system hangs always.
(In reply to comment #5) > Just tested system-config-date, system hangs always. Does it only do this when you configure NTP or also when you switch NTP off?
Also when NTP is off. When NTP is off it hangs immediately I press OK, with NTP enabled I see the message connecting to NTP for a few second then it hangs.
I suspect that your box freezes when the hardware clock is set. Please check if the following command (as root) freezes your system as well: /sbin/hwclock --systohc
yes it freezes
This seems to be either a HW-related kernel bug or a flaw in the hardware that eventually has to be worked around. Changing component to kernel.
There were a few other bug reports regarding system hangs when touching the system clock. I think they *should* be fixed by the latest rawhide kernel. Try updating to the latest kernel and see if it still happens...
Freezes with 2.6.23-5.fc8 just by running /sbin/hwclock as root. Even without the --systohc
What does "hwclock --show --debug" do?
hwclock from util-linux-ng 2.13 using /dev interface to clock. And then freeze.
I'm using rawhide now, last line when running "hwclock --show --debug" before freeze: /dev/rtc does not have interrupt functions. waiting in loop for time from /dev/rtc to change
kernel 2.6.24-0.79.rc4.git5.fc9 [root@localhost ~]# hwclock --show --debug hwclock from util-linux-ng 2.13 hwclock: Open of /dev/rtc failed, errno=19: No such device. No usable clock interface found. Cannot access the Hardware Clock via any known method. [root@localhost ~]# Don't know if it matters anything, but this is f8 and right now I only updated kernel from rawhide and nothing else yet.
F9 alpha: immediate freeze when running hwclock, except it worked at least once.
Just noticed, this is duplicate of 227234 ? I'll close this. *** This bug has been marked as a duplicate of 227234 ***