Bug 182598
| Summary: | ia64: /dev/efirtc accessed before udev runs | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Prarit Bhargava <prarit> | ||||
| Component: | mkinitrd | Assignee: | Peter Jones <pjones> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | David Lawrence <dkl> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | rawhide | CC: | ktokunag, kzak, notting | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2006-08-10 20:05: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: | |||||||
| Bug Depends On: | 182597 | ||||||
| Bug Blocks: | 163350 | ||||||
| Attachments: |
|
||||||
/dev/rtc is handled in mkinitrd. /dev/efirtc probably should be as well. So what's the correct major/minor for the device? Peter: [root@altix3 ~]# ls -l /dev/efirtc crw------- 1 root root 10, 136 Feb 22 08:31 /dev/efirtc [root@altix3 ~]# P. Ok, I've committed it to cvs head. Next build will have it. Created attachment 129358 [details]
Additional patch for mkinitrd to correctly initialize /dev/efirtc
Peter,
This patch is needed to fix the problem ...
P.
Hmmm ... the patch above seems to have a bug in it :( Prarit, Fujitsu has opened an IT related to this problem (IT100192) and Mori-san gave us a pointer to this bug. I tested the patch above on my box (PRIMEQUEST) and it seems that it fixed the problem. According to your last comments, there may still be a bug in the patch. Could you tell me what kind of bug do you think there is in the patch? I'd like to share that information with Fujitsu engineers if appropriate. Kei, This BZ is closed, however, please see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=202110 P. Prarit, OK. I understand the situation. Thank! |
Description of problem: On ia64 platforms, hwclock is accessed via /dev/efirtc. This file is 'created' by udev which runs AFTER the hwclock sync is performed. Version-Release number of selected component (if applicable): latest rawhide pull (fedora-devel branch) How reproducible: 100% Steps to Reproduce: 1. Install Fedora ia64 2. Boot. 3. Actual results: Following error is seen on the console: Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method. Setting clock (localtime): Tue Feb 21 20:00:15 EST 2006 [ OK ] Starting udev Expected results: No errors should be seen. Additional info: The bug is that /dev/efirtc does not exist. This differs from RHEL -- in that case the clock starts AFTER udev has run and the modules have loaded: Press 'I' to enter interactive startup. Starting udev: [ OK ] Initializing hardware... storage network audio done[ OK ] Configuring kernel parameters: [ OK ] Setting clock (localtime): Tue Feb 21 11:07:55 EST 2006 [ OK ] Is there a reason that the rc.sysinit has been modified to startup the clock before udev and module loading?