Bug 238410

Summary: FC7-T4 Problem with ATA66 module.
Product: [Fedora] Fedora Reporter: Joshua <woodguy552010>
Component: kernelAssignee: Alan Cox <alan>
Status: CLOSED UPSTREAM QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: alan
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: 2007-05-21 17:09:18 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:
Attachments:
Description Flags
dmesg from FC5 where there is no problem
none
lspci -vvxxx output from FC5
none
dmesg from FC7-t4 where the problem is
none
Proposed fix none

Description Joshua 2007-04-30 11:33:16 UTC 
Description of problem: pata_hpt66 module fails to initialize onboard Highpoint
ATA66 controller.


Version-Release number of selected component (if applicable):
kernel-2.6.20-1.3104.fc7
kernel-2.6.21-1.3116.fc7

How reproducible:
It fails on every boot and will not boot if drives on the controller (hde hdg)
are listed in fstab.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Joshua 2007-04-30 11:33:16 UTC 
Created attachment 153782 [details]
dmesg from FC5 where there is no problem
Comment 2 Joshua 2007-04-30 11:36:51 UTC 
Created attachment 153785 [details]
lspci -vvxxx output from FC5
Comment 3 Joshua 2007-04-30 11:54:36 UTC 
Created attachment 153787 [details]
dmesg from FC7-t4 where the problem is
Comment 4 Alan Cox 2007-05-01 11:18:25 UTC 
Bug identified - just testing a patch now. It got broken in the move to iomaps.
Comment 5 Alan Cox 2007-05-01 12:01:57 UTC 
Created attachment 153855 [details]
Proposed fix
Comment 6 Alan Cox 2007-05-01 16:33:14 UTC 
Patch send to DaveJ, and stable tree after checking with Tejun Heo

Not going into the dev tree as further rewriting of the port registration code
has already fixed this by accident
Comment 7 Alan Cox 2007-05-21 17:09:18 UTC 
Resolved upstream and in stable