On Tue, Jul 24, 2012 at 08:26:36AM +0100, Lee Jones wrote: > Yes, I am inclined to agree with you. I just thought it was > uncharacteristic of a memory corruption error, as can reliably reproduce > the bootlog above. What's even more strange is that the issue only > arises on one of my two _identical_ development boards.
It's not that unusual depending on where the cause is - for example, copying an initialised struct to the wrong place, and things like the DAPM graph which are big and pointer driven are often affected. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
