Bug 467457

Summary: pata_sch driver not finding slave devices
Product: [Fedora] Fedora Reporter: Mark Salter <msalter>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: medium    
Version: 10CC: kernel-maint
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: 2.6.27.15-170.2.24.fc10 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-02-19 23:40:06 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
Add SLAVE_POSS flag to pata_sch driver. none

Description Mark Salter 2008-10-17 15:16:25 UTC
Created attachment 320678 [details]
Add SLAVE_POSS flag to pata_sch driver.

Description of problem:

PATA SCH driver does not see slave devices.

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


How reproducible:

100%

Steps to Reproduce:
1.Connect slave device to PATA controller of Intel SCH (AF82US15W, AF82US15L, AF82UL11L) chipsets

2.
3.
  
Actual results:

Slave device not found.

Expected results:

Slave device found.

Additional info:

The driver doesn't set the ATA_FLAG_SLAVE_POSS flag so the ATA layer doesn't look for slave devices. Trivial patch attached.

Comment 1 Alan Cox 2008-11-04 15:33:46 UTC
Agreed. Please post the diff with a Signed-off-by: line to linux-ide.org and cc jgarzik

Comment 2 Alan Cox 2008-11-10 14:00:41 UTC
Reminded Jeff about this patch

Comment 3 Bug Zapper 2008-11-26 03:57:37 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Chuck Ebbert 2009-02-10 04:17:13 UTC
The bug fell off the radar when Alan closed it after it was fixed upstream.

Comment 5 Chuck Ebbert 2009-02-10 06:44:51 UTC
Patch went in  2.6.27.15-170.2.21