Bug 101793

Summary: Using an SMP kernel, the system hangs when the configuration space of the PCI device is actively communicating.
Product: [Retired] Red Hat Linux Reporter: Need Real Name <david>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED WONTFIX QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: high    
Version: 8.0CC: riel
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-09-30 15:41:24 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 Need Real Name 2003-08-06 22:13:50 UTC
VERSION/RELEASE:
All SMP kernels in RedHat 7.3, 8.0, 9.0

REPRODUCIBLE:
Yes

STEPS TO REPRODUCE:
0) List the PCI devices on your system:

$lspci

The output will be a long list of devices, in the following format:

00:07.0 VGA compatible controller: Chips an...

1) run the following command (which reads the configuration space):

$while [ 1 ] ; do cat /proc/bus/pci/00/07.0 > /dev/null ; done &

Notice how the lspci output is used in this command - 00:07.0 
becomes /proc/bus/pci/00/07.0 (feel to use a different device or more than one)

2) start and stop X windows (using xinit) between 3 and 15 times

ACTUAL RESULTS:
The system enters a completely unresponsive state and must be rebooted.

EXPECTED RESULTS:
Interaction with the PCI configuration space should not alter system stability 
and should not cause a system crash.

ADDITIONAL INFORMATION:
This problem has been identified and tested in numerous hardware environments 
(dual PIII & dual XEON, different motherboards).  In all of these situations 
(using an SMP kernel), activity in the configuration space of the PCI bus, 
along with the initialization of X, caused the system to crash.

This test was also run on single processor machines and the symptoms were NOT 
detected.

Comment 1 Bugzilla owner 2004-09-30 15:41:24 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/