On Sat, Dec 15, 2012 at 11:41 AM, H. Peter Anvin <hpa@zytor.com> wrote:>> Matt is on vacation, and I'm partly offline for the weekend, but that> definitely seems suspicious. Do we have a memory map of the affected> machine(s)?

but as mentioned, there's bound to be some particular kernel layoutthat triggers this, because I definitely ran a few kernels with thatcommit in it without problems (and clearly other people are too).Looking at my boot log, I had successful boots with both 6a57d104c8cband c2714334b944, which contains that commit.

It might also be that it causes some massive corruption at boot time,but it then requires that that particular memory is actually used. Somaybe it's not so much about the memory map except indirectly.

But that commit *does* look a lot more likely than the things I looked at.

Markus, how did you happen to pinpoint that particular commit? Is itentirely repeatable for you?