Bug 243623

Summary: Long delays in booting
Product: [Fedora] Fedora Reporter: Michael Holmes <holmesmich>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: low    
Version: 7CC: chris.brown
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-01-09 14:12:16 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 Michael Holmes 2007-06-10 20:46:43 UTC
Description of problem:
When booting I get the following errors:
ata2.01:unable to set xfer mode (0x4) 
ata2.01:unable to set xfer mode (0x4) 
ata2.01:unable to set xfer mode (0x4) 
ata2.00:unable to set xfer mode (0x40)

This doesn't stop boot; however, it delays it for long periods.

Version-Release number of selected component (if applicable):
Linux (hostname) 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
athlon i386 GNU/Linux

Additional info:
Hardware info:
http://smolt.fedoraproject.org/show?UUID=453915f7-96f7-459b-b123-cfdabe7ab4c6

Cheers, Mike

Comment 1 Christopher Brown 2007-09-16 20:45:28 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 and will try and assist you in resolving it if I can.

There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel?

If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.

Cheers
Chris

Comment 2 Christopher Brown 2008-01-09 14:12:16 UTC
As indicated previously there has been no update on the progress of this bug
therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue
still occurs for you and I will try to assist in its resolution. Thank you for
taking the time to report the initial bug.