Just thought I'd pass along an error I received this weekend after upgrading two servers to 5.6. Both are HP Proliant DL380 servers running 64-bit, but one is a G6 model and one is a G7. After the upgrade and the reboot to the 2.6.18-238.9.1.el5 kernel, both servers displayed the following error at boot: "pci_mmcfg_init marking 256MB space uncacheable."
Some Googling found me the following link: https://partner-bugzilla.redhat.com/show_bug.cgi?id=581933
There are apparently performance implications due to this issue. Fortunately, the solution is simple: just boot with the kernel parameter acpi_mcfg_max_pci_bus_num=on
If everyone is already familiar with this, please ignore. :-)
On 04/25/2011 08:58 AM, Windsor Dave L. (AdP/TEF7.1) wrote:
Just thought I'd pass along an error I received this weekend after upgrading two servers to 5.6. Both are HP Proliant DL380 servers running 64-bit, but one is a G6 model and one is a G7. After the upgrade and the reboot to the 2.6.18-238.9.1.el5 kernel, both servers displayed the following error at boot: "pci_mmcfg_init marking 256MB space uncacheable."
Some Googling found me the following link: https://partner-bugzilla.redhat.com/show_bug.cgi?id=581933
There are apparently performance implications due to this issue. Fortunately, the solution is simple: just boot with the kernel parameter acpi_mcfg_max_pci_bus_num=on
If everyone is already familiar with this, please ignore. :-)
Supposedly this issue is fixed in the 5.6 kernel ... not introduced in it :D
https://bugzilla.redhat.com/show_bug.cgi?id=581933
However, the advise is good regardless of version of kernel.
On 4/25/2011 10:26 AM, Johnny Hughes wrote:
On 04/25/2011 08:58 AM, Windsor Dave L. (AdP/TEF7.1) wrote:
Just thought I'd pass along an error I received this weekend after upgrading two servers to 5.6. Both are HP Proliant DL380 servers running 64-bit, but one is a G6 model and one is a G7. After the upgrade and the reboot to the 2.6.18-238.9.1.el5 kernel, both servers displayed the following error at boot: "pci_mmcfg_init marking 256MB space uncacheable."
Some Googling found me the following link: https://partner-bugzilla.redhat.com/show_bug.cgi?id=581933
There are apparently performance implications due to this issue. Fortunately, the solution is simple: just boot with the kernel parameter acpi_mcfg_max_pci_bus_num=on
If everyone is already familiar with this, please ignore. :-)
Supposedly this issue is fixed in the 5.6 kernel ... not introduced in it :D
https://bugzilla.redhat.com/show_bug.cgi?id=581933
However, the advise is good regardless of version of kernel.
Yes, I saw the reference to RHEL 5.5 in the bug description, but I never saw the message before the upgrade to CentOS 5.6. Hardware differences, I guess. The bug description mentions a Dell Precision.
Best Regards,
Dave Windsor
Robert Bosch LLC Team Leader, MES Database Infrastructure Group (AdP/TEF7.1) 4421 Highway 81 North Anderson, SC 29621 USA www.bosch.us
On 25/04/11 15:44, Windsor Dave L. (AdP/TEF7.1) wrote:
On 4/25/2011 10:26 AM, Johnny Hughes wrote:
On 04/25/2011 08:58 AM, Windsor Dave L. (AdP/TEF7.1) wrote:
Just thought I'd pass along an error I received this weekend after upgrading two servers to 5.6. Both are HP Proliant DL380 servers running 64-bit, but one is a G6 model and one is a G7. After the upgrade and the reboot to the 2.6.18-238.9.1.el5 kernel, both servers displayed the following error at boot: "pci_mmcfg_init marking 256MB space uncacheable."
Some Googling found me the following link: https://partner-bugzilla.redhat.com/show_bug.cgi?id=581933
There are apparently performance implications due to this issue. Fortunately, the solution is simple: just boot with the kernel parameter acpi_mcfg_max_pci_bus_num=on
If everyone is already familiar with this, please ignore. :-)
Supposedly this issue is fixed in the 5.6 kernel ... not introduced in it :D
https://bugzilla.redhat.com/show_bug.cgi?id=581933
However, the advise is good regardless of version of kernel.
Yes, I saw the reference to RHEL 5.5 in the bug description, but I never saw the message before the upgrade to CentOS 5.6. Hardware differences, I guess. The bug description mentions a Dell Precision.
Best Regards,
Dave Windsor
I saw and reported the issue during QA for CentOS-5.6.
I think it's quite widespread, I saw it on generic Intel-based motherboards.
I've not had any issues applying the documented "fix" and have been running that since January.
On 04/25/2011 10:19 AM, Ned Slider wrote:
On 25/04/11 15:44, Windsor Dave L. (AdP/TEF7.1) wrote:
On 4/25/2011 10:26 AM, Johnny Hughes wrote:
On 04/25/2011 08:58 AM, Windsor Dave L. (AdP/TEF7.1) wrote:
Just thought I'd pass along an error I received this weekend after upgrading two servers to 5.6. Both are HP Proliant DL380 servers running 64-bit, but one is a G6 model and one is a G7. After the upgrade and the reboot to the 2.6.18-238.9.1.el5 kernel, both servers displayed the following error at boot: "pci_mmcfg_init marking 256MB space uncacheable."
Some Googling found me the following link: https://partner-bugzilla.redhat.com/show_bug.cgi?id=581933
There are apparently performance implications due to this issue. Fortunately, the solution is simple: just boot with the kernel parameter acpi_mcfg_max_pci_bus_num=on
If everyone is already familiar with this, please ignore. :-)
Supposedly this issue is fixed in the 5.6 kernel ... not introduced in it :D
https://bugzilla.redhat.com/show_bug.cgi?id=581933
However, the advise is good regardless of version of kernel.
Yes, I saw the reference to RHEL 5.5 in the bug description, but I never saw the message before the upgrade to CentOS 5.6. Hardware differences, I guess. The bug description mentions a Dell Precision.
Best Regards,
Dave Windsor
I saw and reported the issue during QA for CentOS-5.6.
I think it's quite widespread, I saw it on generic Intel-based motherboards.
I've not had any issues applying the documented "fix" and have been running that since January.
Well if this is wipe spread then we need to add this to the Release Notes too ... I'll take care of that if it is not already there.
On 4/25/2011 5:15 PM, Johnny Hughes wrote:
On 04/25/2011 10:19 AM, Ned Slider wrote:
On 25/04/11 15:44, Windsor Dave L. (AdP/TEF7.1) wrote:
<removed>
I saw and reported the issue during QA for CentOS-5.6.
I think it's quite widespread, I saw it on generic Intel-based motherboards.
I've not had any issues applying the documented "fix" and have been running that since January.
Well if this is wipe spread then we need to add this to the Release Notes too ... I'll take care of that if it is not already there.
I looked in the 5.6 Release Notes on the Wiki and didn't see it under "Known Problems" or anywhere else.
Thanks!
Best Regards,
Dave Windsor
On 04/25/2011 04:32 PM, Windsor Dave L. (AdP/TEF7.1) wrote:
On 4/25/2011 5:15 PM, Johnny Hughes wrote:
On 04/25/2011 10:19 AM, Ned Slider wrote:
On 25/04/11 15:44, Windsor Dave L. (AdP/TEF7.1) wrote:
<removed>
I saw and reported the issue during QA for CentOS-5.6.
I think it's quite widespread, I saw it on generic Intel-based motherboards.
I've not had any issues applying the documented "fix" and have been running that since January.
Well if this is wipe spread then we need to add this to the Release Notes too ... I'll take care of that if it is not already there.
I looked in the 5.6 Release Notes on the Wiki and didn't see it under "Known Problems" or anywhere else.
It should be the last entry under known problems now.
Hello Johnny,
On Mon, 2011-04-25 at 09:26 -0500, Johnny Hughes wrote:
On 04/25/2011 08:58 AM, Windsor Dave L. (AdP/TEF7.1) wrote:
There are apparently performance implications due to this issue. Fortunately, the solution is simple: just boot with the kernel parameter acpi_mcfg_max_pci_bus_num=on
Supposedly this issue is fixed in the 5.6 kernel ... not introduced in it :D
https://bugzilla.redhat.com/show_bug.cgi?id=581933
However, the advise is good regardless of version of kernel.
Not exactly. That kernel parameter *is* the fix.
Regards, Leonard.
On 04/26/2011 06:27 AM, Leonard den Ottolander wrote:
Hello Johnny,
On Mon, 2011-04-25 at 09:26 -0500, Johnny Hughes wrote:
On 04/25/2011 08:58 AM, Windsor Dave L. (AdP/TEF7.1) wrote:
There are apparently performance implications due to this issue. Fortunately, the solution is simple: just boot with the kernel parameter acpi_mcfg_max_pci_bus_num=on
Supposedly this issue is fixed in the 5.6 kernel ... not introduced in it :D
https://bugzilla.redhat.com/show_bug.cgi?id=581933
However, the advise is good regardless of version of kernel.
Not exactly. That kernel parameter *is* the fix.
Yes, I see that now.
Actually, that is a "work around" (IMHO). I don't think it should be considered a final fix but an interim jury-rig. Of course, that is just my opinion ... not to be confused with anything important :D
-
Johnny Hughes -
Leonard den Ottolander -
Ned Slider -
Windsor Dave L. (AdP/TEF7.1)