Skip to contentSkip to conversation

Bad page state at prep_new_page

DISCUSSION Jay Roplekar 2 participants 2 messages Feb 26, 2005

lore
Share & tools
lore
#0 lore raw

I have been getting this error off and on with vendor kernel 2.6.8, I have posted about it on lkml 3/4 times before. Actually I had offered to provide a summary of similar reports from the web with no takers, I can still provide that to somebody if it is useful.

I had run memtest overnight with no errors, I use DRM etc.. The reason to
post this is that very first line in the syslog entries related to this error seems to be different than before. {It is typically is kernel BUG at mm/rmap.c or sth similar}. Thanks,

Jay

P.S. I am getting this error once in 3 days on an average (based on grep of moths worth syslog) so I might have dubious distinction of being more repeatable. May be it confirms Hugh's suspicion of hardware misbehaving but I am not ready to accept it yet :-)

####

Feb 26 09:37:03 localhost kernel: mm/memory.c:110: bad pmd 00000500.
Feb 26 09:39:58 localhost kernel: Bad page state at prep_new_page (in process 
'X', page c12678e0)
Feb 26 09:39:58 localhost kernel: flags:0x20000004 mapping:0000f700 mapcount:0 
count:0
Feb 26 09:39:58 localhost kernel: Backtrace:
Feb 26 09:39:58 localhost kernel:  [dump_stack+30/32] dump_stack+0x1e/0x20
Feb 26 09:39:58 localhost kernel:  [<c0107bfe>] dump_stack+0x1e/0x20
Feb 26 09:39:58 localhost kernel:  [bad_page+108/160] bad_page+0x6c/0xa0
Feb 26 09:39:58 localhost kernel:  [<c013d63c>] bad_page+0x6c/0xa0
Feb 26 09:39:58 localhost kernel:  [prep_new_page+40/112] 
prep_new_page+0x28/0x70
Feb 26 09:39:58 localhost kernel:  [<c013d968>] prep_new_page+0x28/0x70
Feb 26 09:39:58 localhost kernel:  [buffered_rmqueue+216/384] 
buffered_rmqueue+0xd8/0x180
Feb 26 09:39:58 localhost kernel:  [<c013de58>] buffered_rmqueue+0xd8/0x180
Feb 26 09:39:58 localhost kernel:  [__alloc_pages+161/752] 
__alloc_pages+0xa1/0x2f0
Feb 26 09:39:58 localhost kernel:  [<c013dfa1>] __alloc_pages+0xa1/0x2f0
Feb 26 09:39:58 localhost kernel:  [do_anonymous_page+102/368] 
do_anonymous_page+0x66/0x170
Feb 26 09:39:58 localhost kernel:  [<c0148796>] do_anonymous_page+0x66/0x170
Feb 26 09:39:58 localhost kernel:  [do_no_page+95/816] do_no_page+0x5f/0x330
Feb 26 09:39:58 localhost kernel:  [<c01488ff>] do_no_page+0x5f/0x330
Feb 26 09:39:58 localhost kernel:  [handle_mm_fault+341/416] 
handle_mm_fault+0x155/0x1a0
Feb 26 09:39:58 localhost kernel:  [<c0148e15>] handle_mm_fault+0x155/0x1a0
Feb 26 09:39:58 localhost kernel:  [do_page_fault+396/1456] 
do_page_fault+0x18c/0x5b0
Feb 26 09:39:58 localhost kernel:  [<c01198ec>] do_page_fault+0x18c/0x5b0
Feb 26 09:39:58 localhost kernel:  [error_code+45/56] error_code+0x2d/0x38
Feb 26 09:39:58 localhost kernel:  [<c0107849>] error_code+0x2d/0x38
Feb 26 09:39:58 localhost kernel: Trying to fix it up, but a reboot is needed
#1 lore raw
Quoted 4 lines · Jay Roplekar

I have been getting this error off and on with vendor kernel 2.6.8, I have posted about it on lkml 3/4 times before. Actually I had offered to provide a summary of similar reports from the web with no takers, I can still provide that to somebody if it is useful.

If I had had time to spare, I'd have taken you up on the offer. Some of those will be ones I've spent hours thinking about without success, some just gone away, some found guilty by memtest86, some I probably have overlooked.

Quoted 7 lines

I had run memtest overnight with no errors, I use DRM etc.. The reason to
post this is that very first line in the syslog entries related to this error seems to be different than before. {It is typically is kernel BUG at mm/rmap.c or sth similar}. Thanks,

Jay

Quoted 7 lines

P.S. I am getting this error once in 3 days on an average (based on grep of moths worth syslog) so I might have dubious distinction of being more repeatable. May be it confirms Hugh's suspicion of hardware misbehaving but I am not ready to accept it yet :-)

####

Feb 26 09:37:03 localhost kernel: mm/memory.c:110: bad pmd 00000500.

Wow. Just two days ago, in unrelated mail, I asked
"Has anyone _ever_ seen a p??_ERROR message?" and you now show us one! Thank you - but you do seem to have quite bad memory corruption.

Quoted 4 lines
Feb 26 09:39:58 localhost kernel: Bad page state at prep_new_page (in process 
'X', page c12678e0)
Feb 26 09:39:58 localhost kernel: flags:0x20000004 mapping:0000f700 mapcount:0 

count:0

Again you have a page mapping which should be NULL here anyway, and doesn't even look like a pointer which is what goes in there at other times.

I understand that you have a sentimental attachment to your setup. And the corruption you're seeing could as well be from software as hardware - but I don't think anyone else is seeing it on this scale, which does point to your particular hardware.

But I don't want to close down this thread: if someone else can suggest something useful to try, please go ahead.

Hugh