|
Bugzilla – Full Text Bug Listing |
| Summary: | memtest86+ Error 28: selected item cannot fit into memory | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.4 | Reporter: | Dirk Mueller <endlichstudent> |
| Component: | Basesystem | Assignee: | Torsten Duwe <duwe> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P3 - Medium | CC: | aspiers, bwiedemann, cobexer, dheidler, endlichstudent, jochen.schaefer, ptesarik |
| Version: | Factory | ||
| Target Milestone: | Factory | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 11.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Dirk Mueller
2010-04-20 10:13:17 UTC
looks like debian has the same problem: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=319837 Interesting. I'd like to find some time to look into this. Do memtest + grub from 11.3 work on that machine? I have the same problem here on openSuSE Factory! (ot: and the YaST bootloader module is stupid) Hi, not sure if my observations are related to this problem. I've meet the erreor message from grub (selected item cannot fit into memory) after installation of OpenSuSE 11.3. But in my case it occured when loading initrd by grub. Initrd was about 12M in size. After disabling memory hole setting in Bios grub reported no errors anymore and everything went fine. Thanks, Jochen Hi all , I close it because no response , fell free to reopen if you can provide the need information .Thank you . I can reproduce the same thing on my Thinkpad x61s. I have tried the following combinations: GRUB memtest86+ result 11.3 11.3 FAIL 11.3 11.4 FAIL 11.4 11.3 FAIL 11.4 11.4 FAIL I'm going to attach the BIOS-provided memory map, too. Stay tuned. BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 0000000000099800 (usable) BIOS-e820: 0000000000099800 - 00000000000a0000 (reserved) BIOS-e820: 00000000000d6000 - 00000000000d8000 (reserved) BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000007d6b0000 (usable) BIOS-e820: 000000007d6b0000 - 000000007d6cc000 (ACPI data) BIOS-e820: 000000007d6cc000 - 000000007d700000 (ACPI NVS) BIOS-e820: 000000007d700000 - 000000007e000000 (reserved) BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved) BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved) BIOS-e820: 00000000fed00000 - 00000000fed00400 (reserved) BIOS-e820: 00000000fed14000 - 00000000fed1a000 (reserved) BIOS-e820: 00000000fed1c000 - 00000000fed90000 (reserved) BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved) Size of memtest.bin is 165080 bytes (0x284d8). AFAICS it should fit into the available memory, but maybe I'm missing something. Argh, the real problem is that memtest86.bin doesn't contain the magic signature ("HdrS"), so it still uses the legacy boot protocol, which always places the command line at 0x99800-0x99fff. Since 0x99800 is already used for the Extended BIOS Data Area (EBDA) on this machine, memtest86+ cannot be booted.
IMO you must rewrite memtest86+ boot code to use a 2.02+ boot protocol.
I also just hit this on a Dell Optiplex 990MT with 16GB of RAM. I downloaded the patched version from http://bitcube.co.uk/content/memtest-failures-0 and it ran fine with kernel --type=netbsd. As machines with larger amounts of memory become more common, that article suggest that this problem will become more common. While this bug is certainly worth being investigated, It's very unlikely I'll ever get at it. Let's face it. :( |