Bug 133048
| Summary: | install is unreasonably slow and appears stopped | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Russell Coker <russell> |
| Component: | kernel | Assignee: | Dave Jones <davej> |
| Status: | CLOSED CANTFIX | QA Contact: | Brian Brock <bbrock> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5 | CC: | cacruden, nobody+pnasrat, pfrields |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-10-30 14:52:48 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
Russell Coker
2004-09-21 05:39:39 UTC
What sort of messages are there on tty3 and tty4 during this time? What sort of hardware are you using? On tty3 when it hangs:
* trying to mount CD device hdc
On tty4 the following is displayed when it starts working:
<6>ide-cd: cmd 0x28 times out
<4>hdc: DMA interrupt recovery
<4>hdc lost interrupt
<4>hdc status timeout: status=0xd0 { Busy }
<4>hdc status timeout: error=0x00
<6>hdc: DMA disables
<3>hdc: drive not ready for command
<4>hdc: ATAPI reset complete
Booting with the FC3T2 and FC3T1 CDs gives the same results.
I am having the same problem on my computer (test 1 & test 2 -- but stopped test 1 since i started it yesterday and figured I would go with test 2 today). The computer is a self-built: ASUS P4C800-E Deluxe 3.0 Ghz processor Bios just updated to newest version 4 GBytes of Memory 4 x 250 GB Disk Space / FastTrak SX-4 M Nvidia GeForce 3 (I think) It has taken 3 hours to get to the point of sitting on NEXT button at Automatically partition (been there 10+ minutes now -- but I am sure it will move on because it has taken this long at many of the steps). oops, I was too optimistic -- probably a different problem -- but ended up getting an Input/output error during write on /dev/sda. Switched the last drive from the array to the motherboard SATA and restarted -- but it is still as slow as molasses. Russell, Was FC4 any better ? How about current rawhide ? I have not updated from rawhide, but FC4 was the same. I had some help a while ago and it looks as though they use something in the bios to determine the amount of memory. This says 4G (4G is installed), but some of the top memory is used by Southbridge - I determined the top memory on my machine was around 3808m of useable memory (before conflict). I am guessing windows does not have this problem because it uses a maximum of 3.5G of the memory and ignores the rest. A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you. Closing per lack of response to previous request for information. Note that FC3 and FC4 are supported by Fedora Legacy for security fixes only. Please install a still supported version and retest. If it still occurs on FC5 or FC6, please reopen and assign to the correct version. Otherwise, if this a security issue, please change the product to Fedora Legacy. Thanks, and we are sorry that we did not get to this bug earlier. |