Messages in this thread | | | Date | Thu, 17 Oct 2013 12:39:02 -0700 | From | "H. Peter Anvin" <> | Subject | Re: Corrupted low memory in v3.9+ |
| |
On 10/17/2013 11:57 AM, Olof Johansson wrote: > > And the low memory checker never even ran before, since it had nothing > to check. Earlier the lower reserved region would be included in the > e820-reserved area if I read the code correctly, and now it's just > marked reserved by the memblock code. > > I guess it could be argued either way whether this is a regression or > not; but at the end of the day we now have systems where this warning > pops when it didn't use to. :( >
I'm wondering if this is a problem with the low memory checker (the residual value of which I have to admit to being skeptical of) or something else.
Could you boot the box with "debug memblock=debug" and earlyprintk turned on and send the boot output?
-hpa
| |