Bug 11852 - When startup script runs "hwclock --hctosys -u" - Asus K7x system freeze or stop.
Summary: When startup script runs "hwclock --hctosys -u" - Asus K7x system freeze or s...
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
(Show other bugs)
Version: 6.2
Hardware: i386 Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-06-02 16:26 UTC by Ivo Sarak
Modified: 2014-03-17 02:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-06-02 16:26:28 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 Ivo Sarak 2000-06-02 16:26:27 UTC
I experience a strange problem with RH6.2/RH6.1 startup when startup 
script tries to set clock (I tracked it down to command "hwclock --
hctosys -u") my system stops responding (I tried on two different AMD 
Athlon Motherboards: ASUS K7V and ASUS K7M). Only way to continue on ASUS 
K7V (with RH6.2) is to press [Print Scrn/SysRq] key, but on ASUS K7M (with 
RH6.1) only reset switch. Strange is that this problem happens on K7V 
(almost) every boot and K7M at least at every third boot.
With K7M problem comes up almost certainly when IDE HD drives are changed 
or swapped, on K7V it seemed to coincident with IDE CDROM presence but now 
it happens every time with or without CDROM.

Same result with "hwclock --hctosys -u" on console, too.
(At the same time third machine with K7M board (with RH6.2) does not have 
this error.)

Comment 1 Bill Nottingham 2000-08-07 05:31:21 UTC
Sorry, but it sounds like that's a hardware problem; these
machines apparently don't implement the RTC clock interface
too well...

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