Bug 116412
| Summary: | hwclock hangs during install | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Thompson <athompso> |
| Component: | util-linux | Assignee: | Elliot Lee <sopwith> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ben Levenson <benl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1 | CC: | davej |
| 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: | 2004-09-24 20:37:09 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: | |||
Either an hwclock or a kernel bug... Since the kernel has changed to a new major version since this report, I think it would be worthwhile to try FC2 on the system and see if that works. It sounds hardware-dependant, so I don't know how helpful I can be in debugging the problem. If you can attach gdb to hwclock and find out what it's up to, we can work together on tracking down the cause of the problem. 1) it's definitely hardware dependant, as other Linux users (not just RH or FC) have reported similar problems on other ASUS motherboards from the same generation and chipset. 2) I am scheduled to install FC2 on one of the affected systems in the near future already. 3) The simple workaround: --directisa (which implies the bug lives in the kernel's RTC driver, maybe?) FC2 works fine. Grepping usenet indicates most people with this generation of ASUS motherboard are experiencing the same thing - 2.6 fixes it. |
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322) Description of problem: During install, no matter whether text mode or graphical, interactive or kickstart, at the "setuptime" stage, hwclock runs and... hangs. Killing hwclock from tty1 allows the installation to proceed. Occurs on CD boot, PXE boot, local install and net install. Version-Release number of selected component (if applicable): FC1 How reproducible: Always Steps to Reproduce: 1. Install FC1 2. Wait forever :-) 3. Actual Results: Installer waits forever for hwclock to return (hwclock --systohc -w) Expected Results: clock should be set and install should proceed Additional info: Motherboard: ASUS CUV4X