Bug 5277

Summary: Intel ca810 M-Boards hang on boot, no tick to sync hwclock.
Product: [Retired] Red Hat Linux Reporter: george_georgalis
Component: util-linuxAssignee: David Lawrence <dkl>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-10-12 18:33:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description george_georgalis 1999-09-21 16:42:20 UTC 
It looks like there is a compatibility problem with the
810 series of Intel M-boards (I'm using RH 6.0 but I
expect this issue with earlier versions as well). This
is a Celeron board, my experience has been with two
CA810 boards, the BIOS version of one of them is Phoenix
8c1a100a.86a.0010.p03 (really) and I've come across the
deja post

http://x38.deja.com/getdoc.xp?AN=476753527&CONTEXT=937526718.243400716&hitnum=0

Apparently, the on-board clock doesn't provide a tick for
the system clock to sync to, and rc.sysinit hangs setting
the system clock (/sbin/hwclock). Apparently ctrl-c will
bypass the hang, but I haven't tried tried that.

If the clock section of rc.sysinit is commented out, it
will boot, but expect problems (networking, filesystem,
etc) from not setting the clock. A better solution might
be to write a script to request current time at boot-up
then run a script to set it more accurately from the
network.

#!/bin/bash
rdate -s <url of a timeserver>
setclock

Some links on the board...

http://support.intel.com/support/motherboards/desktop/ca810/
http://support.intel.com/support/graphics/intel810/
http://support.intel.com/support/graphics/intel810/i810feat.htm
http://support.intel.com/design/chipsets/810/

// George

--
Comment 1 Bill Nottingham 1999-09-21 18:04:59 UTC 
Do you have another example on this? Quoting the post:
--
Never mind, I'm banging my head on the keyboard right now. The
motherboard was faulty.
--
Comment 2 george_georgalis 1999-10-12 18:18:59 UTC 
Actually the motherboard was faulty. The bios clock would not advance.
When Linux boots it waits for 1 tick of the clock before booting.

I troubleshot linux to death before even looking at the hardware.

Lesson well learned.

-- original author

Their have been two additional instances that I've been made aware of.