Bug 205871
Summary: | Anaconda hangs initialising ahci | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Gwendolen <gwendolen.lynch> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED DUPLICATE | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | chlunde, wtogami |
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: | 2007-02-16 18:10:35 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
Gwendolen
2006-09-09 08:38:50 UTC
Current rawhide (20060910) fixes this. Problem is back in rawhide 20060912. Several attempts using rawhide from in between days were all successful. While playing around I noticed on one of the tty's before it locked up that device 0000:00:1f.2 "failed with error -12" Changed summary and component. Exact error on tty4 is: ahci 0000:00:1f.2 version 2.0 ahci: probe of 0000:00:1f.2 failed with error -12 Kernel 2.6.17-1.2647.fc6 boots fine. Do'h! Might help if I reassign to the right people. The problem is that the kernel is saying that the PCI id is supported by both ahci and ata_piix so it's a tossup as to which gets loaded by anaconda -- the hang then shouldn't occur. This seems to be happening with a lot more frequency this time around... I'm wondering what's changed in sata land to be tickling this more I have the same problem on my Dell Precision M20. Same message on tty4, and my lspci-output is the same. FC6 Test 3. Being that this is not an uncommon chipset I'm adding it to FC6KernelBlocker. /me wants FC6 goodness too. This may have been fixed by bug #195779 - however I'm not sure how to verify that it works now. Carl is correct, the fix for bug #195779 seems to coincide with this working for me again. *** This bug has been marked as a duplicate of 195779 *** |