Bug 280781 - ahci error -22 in dmesg
ahci error -22 in dmesg
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i686 Linux
medium Severity low
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-09-06 11:39 EDT by Peter H. Jones
Modified: 2007-12-06 18:48 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-12-06 18:48:40 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Peter H. Jones 2007-09-06 11:39:07 EDT
Description of problem:
ahci gives error -22 while booting.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Boot Fedora
Actual results:
Diagnostic messages in dmesg:

ahci 0000:00:1f.2: version 2.3
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 21
ACPI: PCI interrupt for device 0000:00:1f.2 disabled
ahci: probe of 0000:00:1f.2 failed with error -22
ata_piix 0000:00:1f.2: version 2.12
ata_piix 0000:00:1f.2: MAP [ P0 P2 IDE IDE ]
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 21
PCI: Setting latency timer of device 0000:00:1f.2 to 64
scsi0 : ata_piix
scsi1 : ata_piix

Expected results:
No diagnostics

Additional info:

lspci -v gives:
00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev
03) (prog-if 80 [Master])
        Subsystem: Toshiba America Info Systems Unknown device 0001
        Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 21
        I/O ports at 01f0 [size=8]
        I/O ports at 03f4 [size=1]
        I/O ports at 0170 [size=8]
        I/O ports at 0374 [size=1]
        I/O ports at afa0 [size=16]
        Capabilities: [70] Power Management version 2

Diagnostics reminiscent of old bugs #180773 and #178434, dating back to FC5,
with error code different from -22.
Comment 1 Chuck Ebbert 2007-09-06 12:19:37 EDT
It looks like the ata_piix driver loads successfully after that error. Does the
system work OK even with the errors?
Comment 2 Peter H. Jones 2007-09-06 14:00:19 EDT
Yes, unlike the two bugs I referred to. That's why I gave it a low severity. But
I was wondering if I might be getting less than optimal performance from my hard
Comment 3 Chuck Ebbert 2007-12-06 18:48:40 EST
This is normal for this controller. It supports both legacy and AHCI mode, and
both drivers will be tried.

Note You need to log in before you can comment on or make changes to this bug.