Bug 22318 - hwclock hangs when auto power on enabled
Summary: hwclock hangs when auto power on enabled
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: clock   
(Show other bugs)
Version: 7.0
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Florian La Roche
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-12-14 22:56 UTC by John Saare
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-28 22:21:40 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description John Saare 2000-12-14 22:56:13 UTC
	Asus A7V mobo
	Athlon/T-bird 1Ghz
	IDE drives
	SMC PCI network card
	GeForce 2 GTS display adapter
	SB Live sound

I would like the machine to power on at a fixed time, everyday.  I've
enabled the "Everyday"
(at 8am) automatic power feature of the mobo.  Regardless of whether the
machine is
powered on manually or allowed to come on automatically, the problem
manifests itself

The problem is that when the system's BIOS settings specify auto power on, 
the invocation
of /sbin/hwclock by /etc/rc.d/rc.sysinit, hangs.  Just the process running
hwclock hangs.
If you ctl-C, the boot continues until logging is started, then the boot
will progress no

Repeat by:

	1.  halt system
	2.  Bring up BIOS menu, enable auto power on feature, Everyday, 8am.
	3.  Save new BIOS settings.
	4.  Permit system to finish booting (it probably will succeed).
	5.  Halt system, power off system.
	6.  Power on, Boot system..., will probably hang in hwclock as specified

To "fix":

	7.  reset system...
	8.  Bring up BIOS menu, disable auto power on
	9.  Continue booting (boot single user "linux -s").
	10.  System will probably hang in hwclock.
	11.  Hit ctl-C if/when it hangs during single user boot.
	12.  Not sure why..., but the following "fixes" the hang:

		#fsck /dev/hda1  (Always reports clean)
		#mount -o remount,rw /dev/hda1 / 

	13.  Power system off
	14.  Power on, and allow to boot normally, everything should be back to

I'll dig around on the Asus website when I can get access.  I know that
this may not be
a Redhat/Linux issue, but I thought it worth mentioning..., and in these
days of "Stage 2
power alerts", I'd like to be a good power citizen.

Comment 1 Florian La Roche 2003-02-28 22:21:40 UTC
This has been the only report and it is not reproducable for me, so I am
closing this down.


Florian La Roche

Note You need to log in before you can comment on or make changes to this bug.