Brian Kroth wrote: > Remy Bosch wrote: >> Brian Kroth wrote: >>> I started getting these messages after an upgrade from >>> hardened-sources-2.6.20-r10 to 2.6.22.r8. Nothing changed from the >>> old config. I just did "make oldconfig" and answered N to everything >>> since they weren't relevant. In particular, nothing in PAX or GrSec >>> menus were changed, though whenever I get big nasty messages like this >>> I suspect one of them. Can anyone give me some direction as to how to >>> fix this or what might be causing it? I can post the full configs if >>> need be. >>> >>> Thanks, >>> Brian >> >> I had bad-page errors as well. What I did was wait to see if the adres >> stayed the same. In my case it was, and I can only conclude it was bad >> ram. And with 2GB for only desktop useage, I didnot get the massage >> often. Besides, in my case memtest did not get the faulty page. Even >> after 8+ runs. atm I add the badram-patch to my kernel, so i can pass >> the faulty page address to the kernel, in order to have it ignored. >> >> I got this page broken: >> page:c1b1fdc0 flags:0x80000000 mapping:00000001 mapcount:0 count:0 >> >> >> Goodluck! >> >> Remy >> >> > > Where's this badram-patch and who supports it? memtest also didn't > report any errors for me. I let it run for 9 passes and decided to > try again. This is a server with ECC ram, so I would think it would > catch it, but I can't say for certain since I don't know the details > well enough (at least at the moment). A quick grep/sed of kern.log > shows the output below, so
http://rick.vanrein.org/linux/badram/ Remy -- [EMAIL PROTECTED] mailing list
