[Bug 878063] Re: Can't set memory maximum
Thomas Hood
878063 at bugs.launchpad.net
Thu Oct 20 13:21:32 UTC 2011
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.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to memtest86+ in Ubuntu.
https://bugs.launchpad.net/bugs/878063
Title:
Can't set memory maximum
Status in “memtest86+” package in Ubuntu:
New
Status in “memtest86+” package in Debian:
Unknown
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/878063/+subscriptions
More information about the foundations-bugs
mailing list