Bug 142454 - RHEL4 U2: pciehp driver may not loaded under some BIOS/FW implementations
Summary: RHEL4 U2: pciehp driver may not loaded under some BIOS/FW implementations
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.0
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
: ---
Assignee: Geoff Gustafson
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-12-09 20:17 UTC by Ed Ciechanowski
Modified: 2020-01-13 16:44 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-13 16:44:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
fix for the problem that pciehp driver may not load (393 bytes, patch)
2004-12-09 20:19 UTC, Ed Ciechanowski
no flags Details | Diff
plaintext version of previous patch (659 bytes, patch)
2005-03-16 23:06 UTC, Geoff Gustafson
no flags Details | Diff

Description Ed Ciechanowski 2004-12-09 20:17:20 UTC
Description of problem:
This patch contains a two-line fix for an issue that pciehp driver 
may not load depending on the implementation of ACPI 3.0 methods to 
grant native control.



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

How reproducible:
With some implementation of ACPI 3.0 methods in the BIOS to grant 
native control causes the pciehp driver not to load.

Steps to Reproduce:
1. Need BIOS with implementation of ACPI 3.0 methods to grant native 
control.
2. Try loading the driver.
3.
  
Actual results:
pciehp driver does not load

Expected results:
pciehp driver should load correctly

Additional info:

Comment 1 Ed Ciechanowski 2004-12-09 20:19:26 UTC
Created attachment 108255 [details]
fix for the problem that pciehp driver may not load 

Please get this two line fix into the next RC build.

Comment 6 Ed Ciechanowski 2005-03-15 18:32:58 UTC
With regards to this specific patch/bug fix:
Currently the hotplug code is not adhering to the ACPI 3.0 spec on 
how OSC should be used in conjunction with OSHP.
The patch in Bugzilla 142454 fixes a bug in the hotplug driver so 
that the driver will be compliant with ACPI 3.0 usage model for OSC 
and OSHP. 
This patch has been Accepted upstream and tested at Intel.  Any 
platform implementing ACPI 3.0 methods with OSC, will be vulnerable 
to this issue.

Intel cannot provide any information with regards to specific BIOS 
implementations by OEM's.  Consequently we can only comment on BIOS 
implementations that Intel is shipping.

If any vendor ships a BIOS per the ACPI 3.0 spec. the hotplug driver 
is vulnerable to loading when _OSC denies control to native hot-plug. 
Intel's Harwich platform is shipping with ACPI 3.0 methods with in 
the next 3 weeks. 

Thanks,
*EDC*

Comment 7 Geoff Gustafson 2005-03-16 23:06:15 UTC
Created attachment 112062 [details]
plaintext version of previous patch

Comment 9 dff 2005-04-18 18:25:37 UTC
This bug is currently *not* scheduled to be resolved in RHEL 4 Update 1.

Comment 12 Brian Maly 2005-06-16 14:22:07 UTC
devel ACK for U2

Comment 13 Brian Maly 2005-06-17 16:56:15 UTC
I have a test kernel ready for testing, but we dont seem to have any ACPI 3.0
systems in house. 

Is there any way we could get some vendor testing done on on the some systems
affected by this issue? If not, could we procure some hardware to test on?

I can post a test kernel on people.redhat.com if needed


Comment 23 Peter Martuccelli 2006-11-14 16:22:41 UTC
Geoff - This is an old request.  Please determine if Intel is still asking for
this change, and that we have systems to test on. 

Comment 24 Geoff Gustafson 2006-12-06 19:30:51 UTC
Trying to get a status update from Ed.


Comment 26 Fedora Update System 2017-06-26 08:29:57 UTC
xastir-2.0.8-4.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-06f5ed024f

Comment 27 Fedora Update System 2017-06-27 06:24:39 UTC
xastir-2.0.8-4.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-06f5ed024f


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