Debian Bug report logs - #319837
memtest86+: does not work: wouldn't fit into memory

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Paul Wise <pabs3@bonedaddy.net>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: memtest86+: does not work: wouldn't fit into memory

Date: Mon, 25 Jul 2005 12:49:04 +0800

[Message part 1 (text/plain, inline)]

Package: memtest86+
Version: 1.60-1
Severity: grave
Justification: renders package unusable

When I boot the memtest86+ entry, I get a message like this:

"Error 28: Selected item cannot fit into memory"

pabs@chianamo:~$ ls -lh /boot/
total 26M
-rw-r--r--   1 root root  44K 2005-05-16 16:17 config-2.4.27-2-k7
-rw-r--r--   1 root root  59K 2005-06-21 11:22 config-2.6.11-1-k7
-rw-r--r--   1 root root  60K 2005-07-21 07:13 config-2.6.12-1-k7
-rw-r--r--   1 root root  55K 2005-05-19 17:01 config-2.6.8-2-k7
drwxr-xr-x   3 root root  448 2005-07-22 13:19 grub/
-rw-r--r--   1 root root 3.9M 2005-05-26 09:38 initrd.img-2.4.27-2-k7
-rw-r--r--   1 root root 4.5M 2005-07-04 19:29 initrd.img-2.6.11-1-k7
-rw-r--r--   1 root root 4.7M 2005-07-22 13:19 initrd.img-2.6.12-1-k7
-rw-r--r--   1 root root 4.4M 2005-05-25 15:13 initrd.img-2.6.8-2-k7
-rw-r--r--   1 root root  97K 2005-06-28 05:29 memtest86+.bin
-rw-r--r--   1 root root 520K 2005-05-16 16:45 System.map-2.4.27-2-k7
-rw-r--r--   1 root root 819K 2005-06-21 13:07 System.map-2.6.11-1-k7
-rw-r--r--   1 root root 850K 2005-07-21 08:40 System.map-2.6.12-1-k7
-rw-r--r--   1 root root 824K 2005-05-19 17:28 System.map-2.6.8-2-k7
-rw-r--r--   1 root root 844K 2005-05-16 16:45 vmlinuz-2.4.27-2-k7
-rw-r--r--   1 root root 1.2M 2005-06-21 13:07 vmlinuz-2.6.11-1-k7
-rw-r--r--   1 root root 1.3M 2005-07-21 08:39 vmlinuz-2.6.12-1-k7
-rw-r--r--   1 root root 1.1M 2005-05-19 17:28 vmlinuz-2.6.8-2-k7

pabs@chianamo:~$ cat /proc/cpuinfo
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 8
model name      : AMD Athlon(TM) XP 1700+
stepping        : 1
cpu MHz         : 1469.921
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow
bogomips        : 2908.16

I presume the error comes from grub. I'm using grub with the debian
automagical stuff. My filesystem is reiserfs. Please let me know if
there is any other info you need. I attached my /boot/grub/menu.lst

-- System Information:
Debian Release: unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

-- no debconf information

[menu.lst (text/plain, inline)]

# menu.lst - See: grub(8), info grub, update-grub(8)
#            grub-install(8), grub-floppy(8),
#            grub-md5-crypt, /usr/share/doc/grub
#            and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.           
default		0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout		2

# Pretty colours
color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line)  and entries protected by the
# command 'lock'
# e.g. password topsecret
#      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title		Windows 95/98/NT/2000
# root		(hd0,0)
# makeactive
# chainloader	+1
#
# title		Linux
# root		(hd0,1)
# kernel	/vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

kopt=root=/dev/hda5 ro vga=792
splashimage=(hd0,4)/boot/grub/splashimages/gentleblue.xpm.gz

title Windows XP
	rootnoverify (hd0,0)
	makeactive
	chainloader +1

title OpenBSD
	rootnoverify (hd0,2)
	makeactive
	chainloader +1

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specifiv kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/hda5 ro vga=792

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,4)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
##      alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
##      lockalternative=false
# lockalternative=false

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
##      altoptions=(recovery mode) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
##      howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
##      memtest86=false
# memtest86=true

## ## End Default Options ##

title		Debian GNU/Linux, kernel 2.6.12-1-k7 
root		(hd0,4)
kernel		/boot/vmlinuz-2.6.12-1-k7 root=/dev/hda5 ro vga=792 
initrd		/boot/initrd.img-2.6.12-1-k7
savedefault
boot

title		Debian GNU/Linux, kernel 2.6.12-1-k7 (recovery mode)
root		(hd0,4)
kernel		/boot/vmlinuz-2.6.12-1-k7 root=/dev/hda5 ro vga=792 single
initrd		/boot/initrd.img-2.6.12-1-k7
savedefault
boot

title		Debian GNU/Linux, kernel 2.6.11-1-k7 
root		(hd0,4)
kernel		/boot/vmlinuz-2.6.11-1-k7 root=/dev/hda5 ro vga=792 
initrd		/boot/initrd.img-2.6.11-1-k7
savedefault
boot

title		Debian GNU/Linux, kernel 2.6.11-1-k7 (recovery mode)
root		(hd0,4)
kernel		/boot/vmlinuz-2.6.11-1-k7 root=/dev/hda5 ro vga=792 single
initrd		/boot/initrd.img-2.6.11-1-k7
savedefault
boot

title		Debian GNU/Linux, kernel 2.6.8-2-k7 
root		(hd0,4)
kernel		/boot/vmlinuz-2.6.8-2-k7 root=/dev/hda5 ro vga=792 
initrd		/boot/initrd.img-2.6.8-2-k7
savedefault
boot

title		Debian GNU/Linux, kernel 2.6.8-2-k7 (recovery mode)
root		(hd0,4)
kernel		/boot/vmlinuz-2.6.8-2-k7 root=/dev/hda5 ro vga=792 single
initrd		/boot/initrd.img-2.6.8-2-k7
savedefault
boot

title		Debian GNU/Linux, kernel 2.4.27-2-k7 
root		(hd0,4)
kernel		/boot/vmlinuz-2.4.27-2-k7 root=/dev/hda5 ro vga=792 
initrd		/boot/initrd.img-2.4.27-2-k7
savedefault
boot

title		Debian GNU/Linux, kernel 2.4.27-2-k7 (recovery mode)
root		(hd0,4)
kernel		/boot/vmlinuz-2.4.27-2-k7 root=/dev/hda5 ro vga=792 single
initrd		/boot/initrd.img-2.4.27-2-k7
savedefault
boot

title		Debian GNU/Linux, kernel memtest86+ 
root		(hd0,4)
kernel		/boot/memtest86+.bin  
boot

### END DEBIAN AUTOMAGIC KERNELS LIST

[signature.asc (application/pgp-signature, inline)]

Message #12 received at 319837@bugs.debian.org (full text, mbox, reply):

From: Paul Wise <pabs3@bonedaddy.net>

To: 319837@bugs.debian.org

Cc: control@bugs.debian.org

Subject: memtest86+: 319837: forwarded upstream

Date: Sun, 04 Jun 2006 13:14:20 +0800

[Message part 1 (text/plain, inline)]

found 319837 1.65-1
forwarded 319837 http://forum.x86-secret.com/showthread.php?p=91223#post91223
thanks

This bug still occurs in the latest version in sid/etch. It would be
nice if it could be fixed for the etch release. Also, I forwarded this
bug upstream for you.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise

[signature.asc (application/pgp-signature, inline)]

Message #21 received at 319837@bugs.debian.org (full text, mbox, reply):

From: Paolo Ornati <ornati@fastwebnet.it>

To: 319837@bugs.debian.org

Subject: Not really a BUG...

Date: Mon, 1 Jan 2007 13:55:05 +0100

This is not really a BUG of GRUB... it's just that BIOS tables are
getting bigger!

Memtest86(+) uses the "standard" linux kernel image format, so it it can
be loaded easily by boot loaders such as Lilo and Grub...

The format is:
	512 byte of boot sector
	512 * X bytes of setup (where X is usually 4)
	Y bytes of kernel image

A zImage kernel will be loaded at address 0x10000 (64k) while a bzImage
will be loaded at 0x10000 (1MB).

Memtest uses the old format.

The boot loader also loads a copy of boot sector and setup sectors at
0x90000 (and then execute the setup code):

        |                        |
0A0000  +------------------------+
        |  Reserved for BIOS     |      Do not use.  Reserved for BIOS EBDA.
09A000  +------------------------+
        |  Stack/heap/cmdline    |      For use by the kernel real-mode code.
098000  +------------------------+
        |  Kernel setup          |      The kernel real-mode code.
090200  +------------------------+
        |  Kernel boot sector    |      The kernel legacy boot sector.
090000  +------------------------+
        |  Protected-mode kernel |      The bulk of the kernel image.
010000  +------------------------+
        |  Boot loader           |      <- Boot sector entry point 0000:7C00
001000  +------------------------+
        |  Reserved for MBR/BIOS |
000800  +------------------------+
        |  Typically used by MBR |
000600  +------------------------+
        |  BIOS use only         |
000000  +------------------------+

For the details read this:
	http://lxr.linux.no/source/Documentation/i386/boot.txt

So, basically, this layout assumes that memory up to address 0x9A000 can be used.


The problem is that the newer BIOSes are reserving more and more space
in the top addresses below 640k (low memory), so this layout got
broken... and GRUB cannot do anything about it.

I hit this problem a few days ago switching from an "old" Athlon64
based system to a Core2Duo base one.


If you have an x86_64 system you shold have something like this in the
"dmesg" (it's not printed on x86 if I rember correctly, you can look at
"/proc/iomem" anyway):

[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  BIOS-e820: 0000000000000000 - 000000000008f000 (usable)
[    0.000000]  BIOS-e820: 000000000008f000 - 00000000000a0000 (reserved)
[    0.000000]  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
[    0.000000]  BIOS-e820: 0000000000100000 - 000000003e599000 (usable)
[    0.000000]  BIOS-e820: 000000003e599000 - 000000003e5a6000 (reserved)
[    0.000000]  BIOS-e820: 000000003e5a6000 - 000000003e655000 (usable)
[    0.000000]  BIOS-e820: 000000003e655000 - 000000003e6a6000 (ACPI NVS)
[    0.000000]  BIOS-e820: 000000003e6a6000 - 000000003e6ab000 (ACPI data)
[    0.000000]  BIOS-e820: 000000003e6ab000 - 000000003e6ac000 (usable)
[    0.000000]  BIOS-e820: 000000003e6ac000 - 000000003e6f2000 (ACPI NVS)
[    0.000000]  BIOS-e820: 000000003e6f2000 - 000000003e6ff000 (ACPI data)
[    0.000000]  BIOS-e820: 000000003e6ff000 - 000000003e700000 (usable)
[    0.000000]  BIOS-e820: 000000003e700000 - 000000003f000000 (reserved)
[    0.000000]  BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)


This table is provided by the BIOS and basically tells what memory
regions can or can't be used by the system (because reserved by BIOS,
for example).

The first line tells that, on my system, the limit of usable low memory
is 8f000, which breaks the above layout assumption...

On my Athlon64 based machine (ASUS K8VSE Deluxe) it was 9FC00, and in
fact it worked.


Conclusion: memtest86 should use some other method of loading...


PS: it's a bit odd to have 1GB of memory and read that a <100k thing
"cannot fit into memory" ;)

-- 
	Paolo Ornati
	Linux 2.6.20-rc2 on x86_64

Message #26 received at 319837@bugs.debian.org (full text, mbox, reply):

From: Paolo Ornati <ornati@fastwebnet.it>

To: 319837@bugs.debian.org

Subject: Workaround

Date: Mon, 1 Jan 2007 14:35:38 +0100

As a workaround for the memory-testers that cannot wait, just boot it
from a floppy:

1) insert a Floppy
2) cat /boot/memtest86/memtest.bin > /dev/fd0
3) boot from floppy

This will bypass GRUB and overwrite a bit of these "reserved" memory
regions... I don't think this is a problem (it isn't on my machine).

Another source that tells that some of these regions can be overwritten
without problems is the memtest86 README:
	zless /usr/share/doc/memtest86-3.2/README.gz

Probably these tables (etc) are only used by an OS... but since we only
run memtest there's no problem at all.

-- 
	Paolo Ornati
	Linux 2.6.20-rc2 on x86_64

Message #33 received at 319837@bugs.debian.org (full text, mbox, reply):

From: "Rajeev V. Pillai" <rajeev_v_pillai@yahoo.com>

To: 319837@bugs.debian.org

Subject: memtest86+: does not work: wouldn't fit into memory [PATCH]

Date: Mon, 5 Feb 2007 16:41:14 -0800 (PST)

I've managed to boot both memtest86 (v3.2) and memtest86+
(v1.65 and v1.70) using grub by following the steps below:

1. Use the ELF executable version of memtest (file memtest)
   instead of the zImage i.e. directly bootable version
   (file memtest.bin).

2. Apply the patch below which changes the load address of
   the ELF executable from 0x10000 to 0x100000. Otherwise,
   grub complains: "Error 7: Loading below 1MB is not supported"

3. Make the binaries as usual by typing `make'.

4. Load the ELF executable memtest like this:

   title Memtest86+ v1.70
       root (hd0,2)     # Change this for your setup
       kernel --type=netbsd /boot/memtest


Cheers,
Rajeev

------ Start of Patch ------
diff -urN memtest86+-1.70.orig/memtest.lds memtest86+-1.70/memtest.lds
--- memtest86+-1.70.orig/memtest.lds 2005-09-11 23:47:15.000000000
+0530
+++ memtest86+-1.70/memtest.lds 2006-04-06 11:16:22.089703648 +0530
@@ -3,7 +3,7 @@
 
 ENTRY(_start); 
 SECTIONS {
-       . = 0x10000;
+       . = 0x100000;
        _start = . ;
        .data : {
                *(.data)
------ End of Patch ------


 
____________________________________________________________________________________
Looking for earth-friendly autos? 
Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.
http://autos.yahoo.com/green_center/

Message #40 received at 319837@bugs.debian.org (full text, mbox, reply):

From: Paul Wise <pabs@debian.org>

To: control <control@bugs.debian.org>, 319837@bugs.debian.org

Subject: memtest86+: also present in memtest86, patch works

Date: Wed, 14 Mar 2007 02:31:04 +0900

[Message part 1 (text/plain, inline)]

clone 319837 -1 
reassign -1 memtest86
retitle -1 memtest86: does not work: wouldn't fit into memory
thanks

This bug is also present in memtest86. I've also confirmed that the
patch works for memtest86+, the patch submitter says it is working for
memtest86 too.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise

[signature.asc (application/pgp-signature, inline)]

Message #47 received at 319837@bugs.debian.org (full text, mbox, reply):

From: "Andrew Brampton" <a.brampton@lancs.ac.uk>

To: 319837@bugs.debian.org

Date: Fri, 20 Jun 2008 14:43:33 +0100

This problem still occurs on version 2.01. However the patch suggested
a year ago still works. Perhaps the patch can be taken on by the
memtest86+ developers.

Message #52 received at 319837-done@bugs.debian.org (full text, mbox, reply):

From: Paul Wise <pabs@debian.org>

To: 319837-done@bugs.debian.org

Subject: memtest86+: works again

Date: Sat, 27 Sep 2008 11:58:44 +0800

[Message part 1 (text/plain, inline)]

Version: 2.01-1

Both memtest86 and memtest86+ in sid work for me now.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise

[signature.asc (application/pgp-signature, inline)]

Message #57 received at 319837@bugs.debian.org (full text, mbox, reply):

From: egallego@babel.ls.fi.upm.es (Emilio Jesús Gallego Arias)

To: 319837@bugs.debian.org

Cc: control@bugs.debian.org

Subject: Not fixed for me.

Date: Mon, 13 Oct 2008 19:29:03 +0200

reopen 319837
thanks

Hi all!

I'm afraid this bug is not fixed for me, as I keep getting the 

"Error 28: Selected item cannot fit into memory"

both with stock memtest86+ and with patched one (lds patch).

I'm running Lenny.

Versions:

ii  memtest86+             2.01-1                 thorough real-mode memory tester
ii  grub                   0.97-47                GRand Unified Bootloader (Legacy version)

Hardware: HP xw6400

iomem:

00000000-00097fff : System RAM
00098000-0009ffff : reserved
000a0000-000bffff : Video RAM area
000c0000-000cddff : Video ROM
000d0800-000d51ff : Adapter ROM
000e8000-000effff : pnp 00:0f
000f0000-000fffff : System ROM
00100000-7ffc2e3f : System RAM
  00100000-002ba032 : Kernel code
  002ba033-0037561f : Kernel data
  003ba000-0041d57f : Kernel bss
7ffc2e40-7fffffff : reserved
e0000000-efffffff : reserved
  e0000000-e7ffffff : PCI MMCONFIG 0
f0000000-f81fffff : PCI Bus 0000:40
  f0000000-f7ffffff : 0000:40:00.0
  f8000000-f801ffff : 0000:40:00.0
f8400000-f8403fff : 0000:00:1b.0
  f8400000-f8403fff : ICH HD audio
f8404000-f84043ff : 0000:00:1d.7
  f8404000-f84043ff : ehci_hcd
f8404400-f84047ff : 0000:00:1f.2
  f8404400-f84047ff : ahci
f9000000-fb1fffff : PCI Bus 0000:40
  f9000000-f9ffffff : 0000:40:00.0
    f9000000-f9ffffff : nvidia
  fa000000-faffffff : 0000:40:00.0
fb200000-fd6fffff : PCI Bus 0000:10
  fb200000-fb9fffff : PCI Bus 0000:1e
    fb400000-fb6fffff : PCI Bus 0000:1f
      fb600000-fb60ffff : 0000:1f:00.0
        fb600000-fb60ffff : tg3
  fd601000-fd601fff : 0000:10:00.3
    fd601000-fd601027 : shpchp
fe000000-fe01ffff : pnp 00:0e
fe600000-fe6fffff : pnp 00:0e
fe700000-fe7003ff : pnp 00:0e
fec00000-ffffffff : reserved
  fed00000-fed003ff : HPET 0

Message #66 received at 319837@bugs.debian.org (full text, mbox, reply):

From: Adrian Bridgett <adrian@smop.co.uk>

To: 319837@bugs.debian.org

Subject: memtest86+: does not work: wouldn't fit into memory

Date: Sun, 4 Jan 2009 12:27:43 +0000

Not sure why this has been automatically marked as closed - the
changelog mentions nothing.

I had the same issue when I upgraded my PC from 2GB to 4GB.

I followed the workaround and that worked fine.  I think this is
worthy of a package with tweaked memtest ELF file and preferably also
a grub entry.  I fear that more and more people will be hitting this
problem as they upgrade old boxes to 4GB (pretty sure that's the cause
for me).

Adrian
-- 
Email: adrian@smop.co.uk  -*-  GPG key available on public key servers
Debian GNU/Linux - the maintainable distribution   -*-  www.debian.org

Message #71 received at 319837@bugs.debian.org (full text, mbox, reply):

From: Adrian Bridgett <adrian@smop.co.uk>

To: 319837@bugs.debian.org

Subject: Re: memtest86+: does not work: wouldn't fit into memory

Date: Wed, 16 Dec 2009 20:15:49 +0000

FYI I've just tested the new 4.00-2.1 packages and neither the .bin
nor the elf work for me.

bin fails with error: too small lower memory (0x99100 > 0x97c00)
elf (booting as knetbsd) fails with error: Address 0x0 is out of range

elf patched as per Rajeev's notes fails in the same way.

currently I'm running v2 patched as per Rajeev's notes.

4GB core2 duo desktop box FWIW.

Adrian
-- 
bitcube.co.uk - Expert Linux infrastructure consultancy
Puppet, Debian, Red Hat, Ubuntu, CentOS

Message #76 received at 319837@bugs.debian.org (full text, mbox, reply):

From: "Rajeev V. Pillai" <rajeevvp@gmail.com>

To: 319837@bugs.debian.org

Subject: Re: memtest86+: does not work: wouldn't fit into memory

Date: Sat, 26 Dec 2009 07:30:28 +0530 (IST)

Seeing that this bug is still troubling people, I thought I would
chime in on what does work.

Memtest86+ v4.00 loads and works just fine with GRUB 0.97 on my
machine which is an Asus A7M266-VM motherboard with an Athlon 2 GHz
CPU and 1.2GB RAM. I had to change the load address as described in my
workaround email, though. That original workaround, I posted to the
forum on memtest.org and then to the Debian bug tracker. The forum
was reorganized and the original thread lost. So it looks like
the Debian bug tracker is now the primary source for new information.

Adrian, can you tell me if memtest86+ v4.00 will load with grub 0.97
and/or will load if you reduce the amount of memory on your system?
Both memtest86 and memtest86+ have to be fixed to boot normally with 
GRUB, but, we can try to see until then, if workarounds are possible.

BTW, Chris Brady's memtest v3.5 will load on my system with the same 
workaround, but it will hang soon after. That might be an unrelated
problem.

gcc-4.x used to be a problem when it came to building from source, as the 
memtest.org website said, but it is no longer so with memtest86+ v4.0. 
This version I compile using gcc-4.4.2 and it runs all the tests just
fine.

Rajeev

Message #81 received at 319837@bugs.debian.org (full text, mbox, reply):

From: The Anarcat <anarcat@anarcat.ath.cx>

To: 319837@bugs.debian.org

Subject: what works here

Date: Thu, 8 Apr 2010 20:23:31 -0400

[Message part 1 (text/plain, inline)]

Here, memtest86+ 2.01-1.1 fails with the described error message. This
is on two separate boxes, one has:

Intel Xeon X3210 2.13GHz + 8GB of ram, on a Intel E7230 memory
controler.

The other has a P4 3Ghz with 6GB of ram, with a similar Intel chipset.

I had to apply the hack described in #33 above. My recommendation is to
include the non-.bin file in the binary package *and* apply the patch so
that people can try the other method if the regular one fails.

Thanks,

-- 
Advertisers, not governments, are the primary censors of media content 
in the United States today.
                        - C. Edwin Baker
                        http://www.ad-mad.co.uk/quotes/freespeech.htm

[signature.asc (application/pgp-signature, inline)]

Message #86 received at 319837@bugs.debian.org (full text, mbox, reply):

From: Marc Haber <mh+debian-bugs@zugschlus.de>

To: "Rajeev V. Pillai" <rajeevvp@gmail.com>, 319837@bugs.debian.org, 319837-submitter@bugs.debian.org

Cc: Marc Haber <mh+debian-bugs@zugschlus.de>

Subject: Re: Bug#319837: memtest86+: does not work: wouldn't fit into memory

Date: Sat, 5 Jun 2010 09:39:00 +0200

Hi,

On Sat, Dec 26, 2009 at 07:30:28AM +0530, Rajeev V. Pillai wrote:
> Seeing that this bug is still troubling people, I thought I would
> chime in on what does work.

I have one box with a KT 266 A chipset (the machine dates back to
2001) and 512 MB RAM. On this box, memtest86 doesn't run with the "too
small lower memory" error, while memtest86+ does run, but only sees
640 _K_ and reports thousands of errors on these 640K of memory.
However, Linux runs just fine.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 72739835

Message #94 received at 319837@bugs.debian.org (full text, mbox, reply):

From: Bryce Nesbitt <bryce2@obviously.com>

To: 319837@bugs.debian.org

Subject: Fix

Date: Mon, 13 Jun 2011 00:10:30 -0700

See fix over at:
http://bitcube.co.uk/content/memtest-failures-0

Message #99 received at 319837@bugs.debian.org (full text, mbox, reply):

From: Bryce Nesbitt <bryce2@obviously.com>

To: 319837@bugs.debian.org

Date: Tue, 14 Jun 2011 21:37:01 -0700

Current upstream thread is:
http://forum.canardpc.com/threads/51181-error-too-small-lower-memory?p=4384622#post4384622

Message #104 received at 319837@bugs.debian.org (full text, mbox, reply):

From: Kirill Smelkov <kirr@mns.spb.ru>

To: 319837@bugs.debian.org

Subject: memtest86+: does not work: wouldn't fit into memory

Date: Mon, 6 Feb 2012 18:45:32 +0400

Hello up there,

I'm having the same problem (wouldn't fit into memory) with
memtest_4.10-1.1 and iEi PCISA-945GSE. Multiboot version boots, but then
freezes.

Booting to rebased-as-shown in #33 ELF image works, and to shipped
/usr/lib/memtest86+/memtest86+.elf doesn't (address 0x5000 is out of
range).

Maybe after 5 years it's finally time to just include the patch into
this package? Or are there any drawbacks?


Thanks,
Kirill

Message #109 received at 319837@bugs.debian.org (full text, mbox, reply):

From: Amministrativo <ac.777444@gmail.com>

To: undisclosed-recipients:;

Subject: Avviso

Date: Sat, 19 Dec 2015 02:36:16 +0100

[Message part 1 (text/plain, inline)]

Attualmente stiamo aggiornando i nostri server di database ed e-mail Admin
per ridurre lo spam e le email spazzatura,
siamo quindi l'eliminazione di tutti account inutilizzato per creare spazi
per i nuovi account. Dovete inviare il vostro account di posta
informazioni che sono i seguenti:

Nome utente:
Password:
Conferma password:

Il mancato rispetto di questo ci renda immediatamente il vostro indirizzo
e-mail
disattivati dal nostro database.

centro servizi Admin

[Message part 2 (text/html, inline)]

Message #114 received at 319837@bugs.debian.org (full text, mbox, reply):

From: hisa@host2.web4appio.mx

To: 319837@bugs.debian.org

Subject: Please recheck your delivery address (UPS parcel 003338699)

Date: Fri, 24 Feb 2017 23:17:35 +0000

[Message part 1 (text/plain, inline)]

Dear Customer,

Your item has arrived at the UPS Post Office at February 24, but the courier was unable to deliver parcel to you.

Please review delivery label in attachment!

With many thanks,
Vernon Tipton,
UPS Operation Manager.

[UPS-Delivery-Details-003338699.zip (application/zip, attachment)]

Message #119 received at 319837@bugs.debian.org (full text, mbox, reply):

From: Fabio Fantoni <fantonifabio@tiscali.it>

To: 319837@bugs.debian.org, pabs3@bonedaddy.net, ornati@fastwebnet.it, rajeev_v_pillai@yahoo.com, rajeevvp@gmail.com, anarcat@anarcat.ath.cx, mh+debian-bugs@zugschlus.de, bryce2@obviously.com, kirr@mns.spb.ru, pabs@debian.org

Subject: Re: memtest86+: does not work: wouldn't fit into memory

Date: Fri, 11 Feb 2022 20:05:25 +0100

[Message part 1 (text/plain, inline)]

Hi, this should be solved in 5.31b+dfsg-1 if I remember good.

Can someone tell me if this issue still reproducible on latest version 
of memtest86+ please? (5.31b+dfsg-4)

[OpenPGP_signature (application/pgp-signature, attachment)]

Message #124 received at 319837-done@bugs.debian.org (full text, mbox, reply):

From: Felix Zielcke <fzielcke@z-51.de>

To: 319837-done@bugs.debian.org

Cc: ornati@fastwebnet.it, rajeev_v_pillai@yahoo.com, rajeevvp@gmail.com, anarcat@anarcat.ath.cx, mh+debian-bugs@zugschlus.de, bryce2@obviously.com, kirr@mns.spb.ru

Subject: Re: memtest86+: does not work: wouldn't fit into memory

Date: Sat, 11 Feb 2023 11:03:05 +0100

On Fri, 11 Feb 2022 20:05:25 +0100 Fabio Fantoni
<fantonifabio@tiscali.it> wrote:
> Hi, this should be solved in 5.31b+dfsg-1 if I remember good.
> 
> Can someone tell me if this issue still reproducible on latest
version 
> of memtest86+ please? (5.31b+dfsg-4)
> 

1 year has now passed without getting an answer if this still happens.
Now we have version 6.10 and a lot of rewritten code.

So if that still makes problems, please reopen the bug.

Send a report that this bug log contains spam.