On 12/19/2012 10:44 PM, Bedia, Vaibhav wrote: > On Thu, Dec 20, 2012 at 11:55:24, Stephen Boyd wrote: >> On 12/19/2012 8:48 PM, Bedia, Vaibhav wrote: >>> I tried out 3 variants of AM335x boards - 2 of these (BeagleBone and EVM) have DDR2 >>> and 1 has DDR3 (EVM-SK). The BUG is triggered on all of these at the same point. >>> >>> With Stephen's change I don't see this on any of the board variants :) >>> New bootlog below. >> Great! Can I have your Tested-by then? I'll wrap it up into a patch. Is >> this is a new regression? From a glance at the code it looks to have >> existed for quite a while now. > I went back to a branch based off 3.7-rc4 and don't see the issue there. Not sure > what is triggering this now. > > Tested-by: Vaibhav Bedia <vaibhav.bedia@xxxxxx> Thanks. I was thrown off by the author date of this patch which introduced your problem commit 8823c079ba7136dc1948d6f6dcb5f8022bde438e Author: Eric W. Biederman <ebiederm@xxxxxxxxxxxx> AuthorDate: Sun Mar 7 18:49:36 2010 -0800 Commit: Eric W. Biederman <ebiederm@xxxxxxxxxxxx> CommitDate: Mon Nov 19 05:59:18 2012 -0800 vfs: Add setns support for the mount namespace It seems to have a 2 year gap between commit date and author date. Either way, it looks to be isolated to the 3.8 merge window but affects quite a few architectures. Patch to follow shortly. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html