Kernel bug: mm/rmap.c:483 and related {now 2.6.8}
Quoted 2 lines
Thanks for giving that a thorough run, memory seems exonerated... yet I don't trust this machine at all: have you tried manufacturer diagnostics?
Ouch, that hurts. This is a machine I built myself over three years ago. Ran very stably with 2.4.*. may be it is the age of the machine. The recent hardware changes are additions of a dvd writer, a hdd and a pci wireless card. Which seem to work ok until recently. What other diagnostics would make sense?
Quoted 7 lines
Quoted 2 lines
Jan 29 08:25:02 Bad page state at prep_new_page ('X', page c1251ae0) Jan 29 08:25:02 flags:0x20000004 mapping:00006a00 mapcount:0 count:0Again, something I've not seen reported before: mapping:00006a00, when mapping should be NULL (or at least a pointer into kernel memory). You say message reappeared twice with identical addresses: was that mapping the same each time?
Hmm, it is different one time, as shown below.. I guess should have looked carefully. Although it means nothing to me.. FWIW, please note that in all these cases ndiswrapper (windows driver loader) is being used. Thanks, Jay
Jan 29 08:27:03 localhost kernel: Bad page state at prep_new_page (in process 'X', page c1253a60) Jan 29 08:27:03 localhost kernel: flags:0x20000004 mapping:00006a00 mapcount:0
count:0
Jan 29 08:27:08 localhost kernel: Bad page state at prep_new_page (in process 'X', page c12965e0) Jan 29 08:27:08 localhost kernel: flags:0x20000004 mapping:00006600 mapcount:0
count:0