Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 186272
| Summary: | Anaconda might hang when "sata_promise" is loaded | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Florian Sievert <caleb> | ||||
| Component: | kernel | Assignee: | Jeff Garzik <jgarzik> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6 | CC: | bradstewart57, caleb, davej, grejigl-gnomeprevod, kurt, peterm, triage, wtogami | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | athlon | ||||||
| OS: | Linux | ||||||
| Whiteboard: | bzcl34nup | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2008-05-06 15:36:21 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: | |||||||
| Bug Blocks: | 172490 | ||||||
| Attachments: |
|
||||||
|
Description
Florian Sievert
2006-03-22 17:13:31 UTC
Created attachment 126488 [details]
Attached is the system log took from installation, when anaconda doesn't continue.
Same behaviour installing 64 bits FC5 version on: Athlon 64 3200+ 512MB RAM ATI X700 AGP Asus KV8-Deluxe mainboard Via K8T800 North Bridge, Via VT8237 South Bridge SATA Promise 20378 controller Further information also provided when asked. Same behavior installing on different SATA controllers Athlon 64 3200+ 1GB Corsair XMS ATI radeon 9800pro Abit Kv8 max3, VIA K8T800 NB, VIA VT8237 SB VIA onboard SATA controller (main drives) Silicon Image 3114 SATA controller(secondary) Same behavior installing on different SATA controllers Athlon 64 3200+ 1GB Corsair XMS ATI radeon 9800pro Abit Kv8 max3, VIA K8T800 NB, VIA VT8237 SB VIA onboard SATA controller (main drives) Silicon Image 3114 SATA controller(secondary) Is not exactly the same behaviour. In my case the 'linux nobprobe' does not change anything. Same problem even when SATA drivers are not loaded. Probably is not relevant but last line on anaconda.log warns about not finding floppy disks (what is right as my machine has not any floppy). (In reply to comment #2) > Same behaviour installing 64 bits FC5 version on: > Athlon 64 3200+ > 512MB RAM > ATI X700 AGP > Asus KV8-Deluxe mainboard > Via K8T800 North Bridge, Via VT8237 South Bridge > SATA Promise 20378 controller > Further information also provided when asked. 'linux nodmraid' solves the problem! I confirm this. Loading the installation with "linux nodmraid" makes it possible to load sata_promise without having a black screen at the beginning of the installation. Test installation was successfull and everything runs fine. Looks like dmraid cause the problem. Seems like this problem is still reproduceable for me in fc6test1. I am a little bit confused, because I am not sure, if anybody is on this problem and I am just doing some bug spamming here. But the problem does still exist on fc6test3. I am willed to help giving more information that could help to determinate the problem. However, I won't post any further reports, until somebody asks me. 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. The problem does still exist in FC6 final. Like described in the first post the installation hangs when anaconda tries to start. It looks like the X-Server is loaded successfully and the xorg typical x-cross cursor is shown. However nothing else shows up - even after hours. The system itself does respond on user actions, but it looks like anaconda is freezed. I am not sure how to replace a kernel during the installation process. Please point me to a small instruction. However, I guess that "2.6.18-1.2798.fc6" is even newer and the problem does still exist. Installation does work fine, when using "linux nodmraid" as boot arguments. Same problem here with FC6. I was able to resolve it by removing all but one SATA drive (I have Asus K8L-Deluxe with via and promise sata controllers). However, even after successful installation, I was not able to mount any other drive but /boot and / partition. At the beginning I was getting device already mounted or busy error, and with new update, I am getting device is not block device. I just gave fc7test2 a try and it looks like I cannot reproduce this problem anymore on the new version. Whatever it was, it might be fixed in fc7. Fedora Core 6 is no longer maintained. Is this bug still present in Fedora 7 or Fedora 8? Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers This bug is open for a Fedora version that is no longer maintained and will not be fixed by Fedora. Therefore we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |