From: Stephen Boyd <sboyd@codeaurora.org>
To: "Bedia, Vaibhav" <vaibhav.bedia@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: BUG: spinlock bad magic on CPU#0 on BeagleBone
Date: Wed, 19 Dec 2012 23:07:57 -0800 [thread overview]
Message-ID: <50D2B94D.10309@codeaurora.org> (raw)
In-Reply-To: <B5906170F1614E41A8A28DE3B8D121433EC9B964@DBDE01.ent.ti.com>
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@ti.com>
Thanks. I was thrown off by the author date of this patch which
introduced your problem
commit 8823c079ba7136dc1948d6f6dcb5f8022bde438e
Author: Eric W. Biederman <ebiederm@xmission.com>
AuthorDate: Sun Mar 7 18:49:36 2010 -0800
Commit: Eric W. Biederman <ebiederm@xmission.com>
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
next prev parent reply other threads:[~2012-12-20 7:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B5906170F1614E41A8A28DE3B8D121433EC9A69C@DBDE01.ent.ti.com>
[not found] ` <alpine.DEB.2.00.1212191650430.16873@utopia.booyaka.com>
2012-12-19 20:23 ` BUG: spinlock bad magic on CPU#0 on BeagleBone Stephen Boyd
2012-12-20 4:48 ` Bedia, Vaibhav
2012-12-20 6:25 ` Stephen Boyd
2012-12-20 6:44 ` Bedia, Vaibhav
2012-12-20 7:07 ` Stephen Boyd [this message]
2012-12-20 7:39 ` [PATCH] lib: atomic64: Initialize locks statically to fix early users Stephen Boyd
2012-12-20 19:06 ` Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50D2B94D.10309@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=ebiederm@xmission.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=vaibhav.bedia@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).