Description of problem: xw9400 and xw9300 systems blacklisted for PCI Domain support. This was done at a time when PCI Domain support was not enabled in RHEL5 and these systems did not boot because of the extra domain. Version-Release number of selected component (if applicable): -125.el5 How reproducible: 100% Steps to Reproduce: 1. Boot 2. lspci -D 3. Actual results: lspci -D output shows single domain. Expected results: lspci -D output should show two. Additional info: Noticed by tcamuso, onsite engineer for HP.
Created attachment 326131 [details] RHEL5 fix for this issue
Prarit tested his PCI domain patch on these systems by removing them from the blacklist. However, HP feels that we are too close to the end of the 5.3 cycle to make this change and get adequate test exposure before the GA date, so we would like to defer the fix to 5.4.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
in kernel-2.6.18-130.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5
Created attachment 330880 [details] Output for lspci -D on the -128 kernel attached a text file with the output after running lspci -D on the 2.6.18-128 kernel
Created attachment 330881 [details] Output for lspci -D on the -129 kernel Attached a text file with the output after running lspci -D on the 2.6.18-129 kernel. I do not see a difference in the text file 128kernel.txt when running a diff againest the 129kernel.txt file. Is this expected behavior?
(In reply to comment #6) > Created an attachment (id=330881) [details] > Output for lspci -D on the -129 kernel > > Attached a text file with the output after running lspci -D on the 2.6.18-129 > kernel. I do not see a difference in the text file 128kernel.txt when running > a diff againest the 129kernel.txt file. Is this expected behavior? This wasn't committed to a kernel until -130.el5 . P.
Created attachment 331140 [details] Output for lspci -D on the -130 kernel I'm assuming this is now fixed since I was able to boot with the -130 kernel with AHCI Bus Segmentation enabled.
Yes, I believe it is fixed and this BZ can be closed.
Updating PM score.