Re: memmap exclude boot command: how to check if it was indeed applied

2013-07-02 Thread Eric Valette
On 01/07/2013 20:40, Eric Valette wrote: Hi, After hunting an unreproducible bug, I decided to run memtest86+ and found that only 8 byte of memory refuse to write the last two digit on the last 4GB memory stick. Memory is at 0x31db357558 So I decided to add a memmap=4K@0x00031db35000

Re: memmap exclude boot command: how to check if it was indeed applied

2013-07-02 Thread Eric Valette
On 01/07/2013 20:40, Eric Valette wrote: Hi, After hunting an unreproducible bug, I decided to run memtest86+ and found that only 8 byte of memory refuse to write the last two digit on the last 4GB memory stick. Memory is at 0x31db357558 So I decided to add a memmap=4K@0x00031db35000

memmap exclude boot command: how to check if it was indeed applied

2013-07-01 Thread Eric Valette
Hi, After hunting an unreproducible bug, I decided to run memtest86+ and found that only 8 byte of memory refuse to write the last two digit on the last 4GB memory stick. Memory is at 0x31db357558 So I decided to add a memmap=4K@0x00031db35000 boot options in GRUB_CMDLINE_LINUX. But

memmap exclude boot command: how to check if it was indeed applied

2013-07-01 Thread Eric Valette
Hi, After hunting an unreproducible bug, I decided to run memtest86+ and found that only 8 byte of memory refuse to write the last two digit on the last 4GB memory stick. Memory is at 0x31db357558 So I decided to add a memmap=4K@0x00031db35000 boot options in GRUB_CMDLINE_LINUX. But