PCI Not using MMConfig
I installed FC6 on a brand new system after my failed attempts to install FC3 and recompiling the kernel 2.6.20 both of which did not worked (infact the problem was that my system was extremely slow it is Pentium D)
then at the first boot when I did not even had a user account I got following errors PCI BIOS Bug area at e0000000 is not E820 reserved PCI Not using MMConfig I am really curious to know what these errors mean what I did to get rid of these erros was I went to my BIOS and enabled the Single Processor Option after which the system was working normally but I had a same problem when I tried to use FC3 with kernel 2.6.20 it gave me a BIOS Bug error with some no . tell me what files I should post here so that some one can point out the problem as I am my self not able to understand the problem . |
The e0000000 is a memory address, MMConfig I believe is also memory related but not up to snuff on that one. Not sure about the E820, could be an Error code that you can verify either through mother board manual or bios error codes.
|
actually I was able to install FC6 on this system I got the same error when I tried to compile kernel 2.6.20.3 the same "sort of"
PCI BIOS Bug came and I got a kernel panic message the result was I could not boot Into the new kernel. where to look in to find the boot failure messages or whatever it is called like log file etc I do not exactly know the names of the files where to look in |
Intel had issued a buggy reference BIOS, that your board uses. These messages are reporting that, and that Linux is not using the information as a result. You can check with your motherboard manufacturer for an update to correct the problem, or disable mmconfig by booting with the kernel option 'pci=nommconf'.
You can read the discussion on this in the kernel mailing list here. |
Quote:
|
|
Ok I got it but what is this MMCOFig for what does it do ,is is a process or some thing in hardware
|
The mmconfig refers to the PCI memory mapped configuration region(s) in the resource map of the BIOS. In other words, it's a BIOS bug. If your manufacturer has released a BIOS update to correct the problem, that would be the way to go.
|
The manufacturer has not released any such bug but I recently switched over to Open Suse 10.2 and there is no such bug when I boot from it and the Suse is utilising both the CPU's
|
The bug still exists, but the message warning of it is not being issued by the Suse kernel.
|
Thanks for this info
I have seen this same problem in some other System that used FC5 and MSI board |
All times are GMT -5. The time now is 02:38 PM. |