RAM Mapping Script

[Jim Kuzdrall]

On Monday 03 March 2008 11:28, Coleman Kane wrote: This was my point,
> that this memory would never be used by the Linux kernel or any
> applications during normal operation. However, when vm86 mode is set
> up, this first 1MB of RAM is typically copied from the first 1MB of
> system RAM to populate the "virtual 1MB" in your vm86 process. So my
> point with the vm86 mode talk was that if the memory at 64h were the
> *only* memory that was actually bad, then this problem should affect
> your system except during cases where the kernel is attempting to set
> up a VM86 process.
>
> My guess is that more RAM is also bad, just less obviously bad. Have
> you tried running memtest86 with some of the more exhaustive tests on
> this system?

    The memory test ran for 95 hours.  It gave 5 errors, all in the same 
byte.  I think the test type and specific data were the same.

    I am tempted to put it in an environmental chamber I have to see if 
35C brings out more errors.  If not, it is definitely a one bit 
failure.  There are several types of physical defects and different 
locations where they may be.  This one seems like a bit storage 
capacitor that leaks a little too fast for the refresh rate.  
Temperature would nail that down.  We keep the house and lab at a cool 
18C during the heating months.

    The idea of /dev/mem is new for me and I am looking forward to 
checking it out.  Right now, I better get some work done or I will be 
holding people up.

    I have a controllable urge to recompile a kernel with some of my own 
assembly language code included.

Jim Kuzdrall

Would the 2.6 kernel necessarily  
>
> --
> Coleman Kane
>
> _______________________________________________
> gnhlug-discuss mailing list
> gnhlug-discuss at mail.gnhlug.org
> http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/