Red Hat Bugzilla – Bug 343761
Kernel hangs error message: "PCI BIOS Bug e0000000is not e820 - reserved"
Last modified: 2008-02-15 21:48:52 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:126.96.36.199) Gecko/20070718 Fedora/188.8.131.52-1.fc7 Firefox/184.108.40.206
Description of problem:
boot up hangs at the
Red Hat nash 6.0.9 message
If I choose an earlier kernel from the grub/boot menu everything works as expected.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.boot my computer to the kernel 220.127.116.11-91.fc7.i686
Boot up hangs at the Red hat nash message and the preceding line is an error message that says: PCI BIOS Bug e80000000 is not e820 - reserved.
I would expect it to start up normally
(In reply to comment #0)
> Boot up hangs at the Red hat nash message and the preceding line is an error
> message that says: PCI BIOS Bug e80000000 is not e820 - reserved.
That is just a warning.
What version is the latest kernel that works?
And see also:
I have the same situation. I am using F7 and similar message appeared from the
beginning and exists in all kernels till now. I upgraded from FC6 with yum and
there was no such message in any of FC6 kernels.
I googled a bit and have found very nice description of situation in lkml:
I have the same laptop model (Hewlett Packard nc6320) and I see the same
messages during the boot process:
PCI: BIOS Bug: MCFG area at f8000000 is not E820-reserved
PCI: Not using MMCONFIG.
and a bit later:
usb 1-1: device not accepting address 2, error -71
I forgot to say that for me kernel is not hanging and never hanged duing the boot.
After upgrading to 18.104.22.168-21.fc7 I see no more PCI error messages during the
boot. But error message about usb 1-1 still appears.
I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the Fedora kernel.
I am CC'ing myself to this bug and will try and assist you in resolving it if I can.
There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel?
If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.
Closing as per previous comment. Please re-open if this is still an issue for you.