Can't set memory maximum
Bug #878063 reported by
Thomas Hood
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| memtest86+ (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
Bug Description
When I run memtest86+ on a ThinkPad X61 with 4 GiB memory, memtest reports failures at locations starting with "4096M". Makes sense, since there is no memory above 4096 MiB.
Printing out all the errors slows down the program a lot. I would like to skip testing the non-existent memory.
However (and this is the bug), pressing "c", "2", "2" (i.e., Test Address Range | Set Upper Limit) and attempting to change the memory range reveals bugs. It seems to be impossible to enter 4096 MiB as the maximum. I tried various strings such as "4096m" (can't enter capital letters) and "4294967296" but the program didn't interpret these correctly.
memtest86+ v.40 run immediately after upgrade to oneiric
Revision history for this message
| Thomas Hood (jdthood) wrote | #1 |
| Changed in memtest86+ (Debian): | |
| status: | Unknown → New |
| no longer affects: | memtest86+ (Debian) |
| Changed in memtest86+ (Ubuntu): | |
| status: | New → Incomplete |
To post a comment you must log in.
After further research I realized that memtest86+ is probably testing real memory at "4096M": the highest installed geeg has presumably been mapped at 4MiB - 5MiB. So the errors being found are probably real in some sense.
So I shouldn't have linked this report to Debian report #503860.
But this doesn't change the fact that I'd like to exclude this range and "c | Address Range | Set Upper Limit" doesn't work. Or I don't know how it is supposed to work.