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 436591
Summary: | kernel 2.6.24.3-12.fc8 fails to recognize disks so it does not boot | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Michal Jaegermann <michal> | ||||||
Component: | kernel | Assignee: | Jeff Garzik <jgarzik> | ||||||
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 8 | CC: | kernel-maint, peterm | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2008-03-10 22:11:38 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
Michal Jaegermann
2008-03-08 06:28:53 UTC
Created attachment 297268 [details]
dmesg from a booting 2.6.23.15-137.fc8 kernel
Hm, that looks like that http://kerneltrap.org/mailarchive/linux-kernel/2008/2/9/795354 http://kerneltrap.org/mailarchive/linux-kernel/2008/2/17/885364 Unfortunately it does not say which BIOS version was used. I will try to update that BIOS when I will have a chance and report back. I had a chance to try this morning a BIOS update. Eventually I used version 1009 which is the latest "non-beta" available from ASUS. After a protracted fight with BIOS I eventually managed to boot a machine and that worked with 2.6.24.3-12.fc8. dmesg from that boot shows what looks like essential differences so it is attached below. Should this be closed then? The issue is that an older BIOS was good enough for 2.6.23.15-137.fc8 but not for 2.6.24.3-12.fc8. Luckily a suitable update did exist (but I would not dare to tell my wife to apply it :-). Created attachment 297519 [details]
dmesg from 2.6.24.3-12.fc8 (on the same machine after a BIOS update)
Looks like the BIOS now disables PMP and 64-bit DMA. > Looks like the BIOS now disables PMP and 64-bit DMA.
That could be because of mis-settings after a BIOS update.
I had a really hard time to get that BIOS to a state where
it was booting anything at all ("safe defaults" were not suitable
for this) and after I managed to accomplish that feat I really
had to hurry somewhere else with no time to rescan and fish out
what else could/should possibly be changed without making
the machine unbootable again.
I cannot even tell you if there are options to enable the above.
> Looks like the BIOS now disables PMP and 64-bit DMA.
> (Chuck Ebbert in comment #5)
I looked again at dmesg output for 2.6.23.15-137.fc8 with 0804, i.e.
old, BIOS and 2.6.24.3-12.fc8 booting with 1009. If a comment is
about these two lines:
ahci 0000:00:12.0: controller can't do 64bit DMA, forcing 32bit
ahci 0000:00:12.0: controller can't do PMP, turning off CAP_PMP
then the first one is the same in both cases and only the second
one showed up after updates. I do not see also any other info
about DMA which would change in any essential way.
(Not that I have a clue what PMP is and Google is not of much help :-).
I am not that convinced that closing that as NOTABUG was not a bit too hasty. True, I found a way to boot that particular hardware but see also http://lkml.org/lkml/2008/3/9/136 . It looks strangely familiar. That may be buggy BIOSes but what is new here? http://lkml.org/lkml/2008/3/9/171 and follow-ups also seem to have some relevance. (In reply to comment #7) > (Not that I have a clue what PMP is and Google is not of much help :-). PMP = port multiplier port http://www.sata-io.org/portmultiplier.asp i have those issues described in the original post too. However i have found a kernel parameter that fixes it: pci=nomsi without that parameter i get: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: qc timeout (error 0xec) ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) ata1.00: failed to recognize some devices, retrying in 5 sec With pci=nomsi it works fine and recognizes my western digital HDD (Jmicron sata controller, kernel 2.6.24-2.fc9 on FC9 Alpha, i had this in the regular FC8 too, after the latest kernel 2.6.24 update) |