Bug 311491 - kernel panic - cannot find valid memory map
kernel panic - cannot find valid memory map
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
low Severity high
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
: 312551 (view as bug list)
Depends On:
Blocks: F8Test3
  Show dependency treegraph
Reported: 2007-09-28 14:35 EDT by Thomas J. Baker
Modified: 2013-01-09 23:26 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-01 10:43:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
camera phone shot of screen showing panic (224.92 KB, image/jpeg)
2007-09-28 14:35 EDT, Thomas J. Baker
no flags Details

  None (edit)
Description Thomas J. Baker 2007-09-28 14:35:04 EDT
My Dell XPS1210 laptop can't boot any F8 kernels >= 211.rc8.git2.fc8. It
complains about not finding a memory map. I've tried 211 from rawhide and 213
from koji. The 204 kernel released yesterday in rawhide works. There have been a
few build in between that and 211 which I haven't tried. I can if you need me to.
Comment 1 Thomas J. Baker 2007-09-28 14:35:04 EDT
Created attachment 210791 [details]
camera phone shot of screen showing panic
Comment 2 Thomas J. Baker 2007-09-28 14:44:19 EDT
I should add the 211 kernel boots fine on my two other desktop xeon systems so
it's a conflict with my core2duo laptop.
Comment 3 Jesse Keating 2007-09-28 15:01:03 EDT
We're pretty sure we know whats causing this issue.  A fixed patch is going into
upstream today hopefully at some point, or will be added as a patch in a kernel
Comment 4 Chuck Ebbert 2007-09-28 16:35:31 EDT
Fix is in CVS, will be in the next kernel.
Comment 5 Chuck Ebbert 2007-10-01 10:31:21 EDT
*** Bug 312551 has been marked as a duplicate of this bug. ***
Comment 6 Jesse Keating 2007-10-01 10:43:07 EDT
This is confirmed fixed for me.

Note You need to log in before you can comment on or make changes to this bug.