Bug 688832

Summary:	CPU PCI-E root ports will be disable if SPKR pin of PCH is without pulled up
Product:	Red Hat Enterprise Linux 6	Reporter:	Ducky Lin <Ducky.Lin>
Component:	kernel	Assignee:	Red Hat Kernel Manager <kernel-mgr>
Status:	CLOSED NOTABUG	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.0	CC:	notting, syeghiay
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-11-03 17:58:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Ducky Lin 2011-03-18 07:09:19 UTC

Description of problem:
The CPU PCI-E root ports (Dev 1 Fun 0/1)  will be disabled if  SPKR pin of PCH is without pulled up resister (R890) when the 1st boot of system after SPI flash ROM is updated with *.bin file. This will caused the LOM connected to the root port Dev=1/Fun=1) can't be detected by BIOS and OS.
This issue can't be found after a DC/AC cycling after at lease 30 cycles.
This issue was found on E-sample build. Now we already decide to mount R890 back. 

Version-Release number of selected component (if applicable):
RHEL Kernel version: 2.6.32-71.el6.x86_64

How reproducible:


Steps to Reproduce:
1. To update the SPI flash part with *.bin file by either tool under OS or programmer.
2. AC off then ON
3. power on the system, you can't see the LOM (MAC address) in the BIOS set up menu at the 1st boot. 

  
Actual results:
This will caused the LOM connected to the root port (Dev=1/Fun=1) can't be detected by BIOS and OS.

Expected results:
The LOM connected to the root port Dev=1/Fun=1) should be detected by BIOS and OS.

Additional info:

Comment 2 Richard W.M. Jones 2011-03-18 09:03:16 UTC

I'm pretty sure 'watchdog' is not the correct component
for this bug, although I've no idea what it should be.

Setting component to 'distribution' ... please someone
reassign this appropriately.

Comment 4 RHEL Program Management 2011-07-06 01:34:30 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 5 RHEL Program Management 2011-10-07 15:27:01 UTC

Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 6 Prarit Bhargava 2011-11-03 17:58:37 UTC

Looks like a BIOS problem.

P.