Bug 214098 - Timeout and reset in ahci module
Summary: Timeout and reset in ahci module
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-05 18:46 UTC by Heine Andersen
Modified: 2008-08-02 23:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-01-08 00:30:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Output from dmesg + hdparm I + lspci -vvv (10.46 KB, application/octet-stream)
2006-11-05 18:46 UTC, Heine Andersen
no flags Details

Description Heine Andersen 2006-11-05 18:46:13 UTC
Description of problem:
Slow boot

Version-Release number of selected component (if applicable):
Linux XXX 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:39:22 EDT 2006 x86_64 x86_64
x86_64 GNU/Linux

How reproducible:
Always


Steps to Reproduce:
1. Power on and boot Fedora
2.
3.

Actual results:

ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: qc timeout (cmd 0xec)
ata2.00: failed to IDENTIFY (I/O error, err_mask=0x104)
ata2: port is slow to respond, please be patient
ata2: port failed to respond (30 secs)
ata2: COMRESET failed (device not ready)
ata2: hardreset failed, retrying in 5 secs
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-6, max UDMA/133, 640 sectors: LBA
ata2.00: ata2: dev 0 multi count 1
ata2.00: configured for UDMA/133


Additional info:
This is not a problem using 2.6.17.x.

Comment 1 Heine Andersen 2006-11-05 18:46:13 UTC
Created attachment 140404 [details]
Output from dmesg + hdparm I + lspci -vvv

Comment 2 Jon Stanley 2007-12-31 21:52:23 UTC
Hello,

I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the Fedora kernel.

http://fedoraproject.org/wiki/KernelBugTriage

I am CC'ing myself to this bug, however this version of Fedora is no longer
maintained.

Please attempt to reproduce this bug with a current version of Fedora (presently
Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a
few days if there is no further information lodged.

Thanks for using Fedora!

Comment 3 Jon Stanley 2008-01-08 00:30:17 UTC
Closing per previous comment.  If you can provide the requested information,
please feel free to re-open this bug.


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