badmem-users — User-related issues for the badmem system

[Badmem-users] specific memory range pattern

[Thamer Al-H. <tm...@wh...>]

Hi,

I recently installed a DDR module and it caught on fire. I later
placed it on another slot and it worked fine. Obviously the fire
broke it in several ways.

I went ahead and ran memtest86, and got a _lot_ of badmem patterns.
These specifically happen between the 312-320MB range (it's 512mb
total). The problem is the patterns are too many. I believe I cannot
give the kernel all of them on the boot command line.

Is there a way to simply specify a pattern that ignores memory
between 312 to 320MB? Is there a way to scan the memory from within
Linux and generate patterns there? Simply far too many to copy down.

I'm using the old patch for the 2.2 kernel series. I'd be willing to
upgrade and use the newer bad-mem patches if they have a capability
of simply ignoring a specific chunk of memory i specify by range.

--
Thamer Al-Harbash            http://www.whitefang.com/
"We must never forget that we are geeks, and as geeks
 we dream, and when we dream we dream of code." -- anon.

[Badmem-users] user experience with memtest86 v2.8

[Nico S. <ni...@wr...>]

Hi everybody outside,

with the new release I ran into some trouble on generation of the badmem patterns during the testing process of memtest86 
v2.8. Version 2.7 works fine, but v2.8 is broken here; the pattern are not printed at all, although the error mode is set to 
"BadRAM pattern". Does anyone have a similar behaviour?

73
  Nico

EMail: ni...@wr...
PGP-fingerprint: 5DDB 09E4 3FF3 CD09 7559  1117 9C03 46E3 38FC 9E03
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d- s-:-- a-- C++ UL++ P L+++ E- W++ N+ o- K- w
O- M- V- PS PE Y+ PGP++ t+ 5++ X R tv- b- DI- D
G e h-- r- y+
------END GEEK CODE BLOCK------

[Badmem-users] Patterns

[Nico S. <ni...@wr...>]

Hi Users!

I am pleased to anounce that many of you already sent me their real-life patterns for testing. Hopefully the next few weeks will 
spent some spare time so that I can have a closer look on badmem again. In any case, the todo list is full. Among other things, 
the following items are listed:

* some strange configure problem I still do not know where it comes from [bug fix, high priority]
* a memtest mdf expansion (this requires a some really deep, hard work on the combine/hash algorithm of the library)
* an integrated kernel patch so that you can compile the kernel without the need of the utilities

If there are other topics [like bug fixes or small features desires] that you really want to be implemented in the next release, 
please email me at ea...@us...!

73
  Nico

EMail: ni...@wr...
PGP-fingerprint: 5DDB 09E4 3FF3 CD09 7559  1117 9C03 46E3 38FC 9E03
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d- s-:-- a-- C++ UL++ P L+++ E- W++ N+ o- K- w
O- M- V- PS PE Y+ PGP++ t+ 5++ X R tv- b- DI- D
G e h-- r- y+
------END GEEK CODE BLOCK------