Donate Share

BadMEM patches/utils for Linux Kernel

Tracker: Bugs

5 2.6.15 - patch doesn't work :( - ID: 1455675
Last Update: Tracker Item Submitted ( nobody )

Hi;

I've problem with 2.6.15 kernel and badmem patch;
kernel seems to recognize and mark bad areas:

DEBUG BadMEM: init_begin=0xc047c000,
init_end=0xc04a1000, max_low_pfn=81904
DEBUG BadMEM: code_begin=0xc0100000,
code_end=0xc0386269
DEBUG BadMEM: data_begin=0xc0386269,
data_end=0xc0478654
DEBUG BadMEM: virtual page offset=0xc0000000
Memory: 320196k/327616k available (2584k kernel code,
6888k reserved, 968k data,
148k init, 0k highmem, 36864k badram)

but when I e.g. unpack large archive kernel print error
messages, gzip exit whit integrity error;
KDE exit whith signal 11, etc.
I've also testing 2.6.14 - with the same results;

I've been using badmem patch for about 2 years with no
problem, on 2.4.26 (same machine and configuration):

DEBUG BadMEM: init_begin=0xc036a000,
init_end=0xc0381000,
max_low_pfn=81904
DEBUG BadMEM: code_begin=0xc0100000,
code_end=0xc02cddd5
DEBUG BadMEM: data_begin=0xc02cddd5,
data_end=0xc0367ce4
DEBUG BadMEM: virtual page offset=0xc0000000
Memory: 284040k/290752k available (1847k kernel code,
6324k reserved, 615k
data, 92k init, 0k highmem, 36864k badram)

There are differences beetween init_begin on 2.6 and 2.
4 kernels, but i've use the same lilo.conf:

(...)
append="badmem=0x08201710,0x08201710,0x0d003990,
0x0d003990,0x09a01e30,0x09a01e30"
(...)

Best regards.



Nobody/Anonymous ( nobody ) - 2006-03-21 21:32

5

Open

None

Nobody/Anonymous

BadMEM kernel patch

None

Public


Comments




Log in to comment.

No follow-up comments have been posted.

Attached File

No Files Currently Attached

Change

No changes have been made to this artifact.