Bug 676923 - no /dev/rtc until after udev starts
Summary: no /dev/rtc until after udev starts
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: realtime-kernel
Version: 1.3
Hardware: All
OS: Linux
high
medium
Target Milestone: ---
: ---
Assignee: John Kacur
QA Contact: David Sommerseth
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-11 21:08 UTC by Guy Streeter
Modified: 2018-11-14 14:43 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-08 19:01:53 UTC
Target Upstream Version:


Attachments (Terms of Use)
console log showing the error (17.79 KB, text/plain)
2011-02-11 21:33 UTC, Guy Streeter
no flags Details

Description Guy Streeter 2011-02-11 21:08:07 UTC
There was a patch in the 2.6.24 RT kernel to create a /dev/rtc device so that the hwclock command would work during system startup. It appears to be missing from the 2.6.33 kernel.
Without the patch, this error occurs:

		Welcome to Red Hat Enterprise Linux Client
		Press 'I' to enter interactive startup.
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.

After the system boots and the udev rule created the link from /dev/rtc0 to /dev/rtc, the hwclock command works correctly.

Comment 1 Guy Streeter 2011-02-11 21:33:05 UTC
Created attachment 478318 [details]
console log showing the error

Comment 3 David Sommerseth 2011-03-03 14:51:10 UTC
Verified by code review and checking boot log.

Found bz465837-rtc-compat-rhel5.patch-ported-to-V2.patch applied to the kernel-rt-2.6.33.7-rt29.53.src.rpm.

When booting kernel-rt-2.6.33.7-rt29.47, this message is shown during the boot process:
-----------------------------------------------------------------
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
-----------------------------------------------------------------

This error is not happening when booting kernel-rt-2.6.33.7-rt29.53.


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