From: Andrew Morton <akpm@linux-foundation.org>
To: Axel Lin <axel.lin@ingics.com>
Cc: linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
Brian Norris <computersforpeace@gmail.com>,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: BUG: sleeping function called from invalid context at kernel/locking/mutex.c:616
Date: Wed, 4 Dec 2013 23:22:51 -0800 [thread overview]
Message-ID: <20131204232251.73cc62c6.akpm@linux-foundation.org> (raw)
In-Reply-To: <1386227524.4806.7.camel@phoenix>
On Thu, 05 Dec 2013 15:12:04 +0800 Axel Lin <axel.lin@ingics.com> wrote:
> >
> > blam. spin_unlock_irq(&mapping->tree_lock) failed to decrement
> > preempt_count(). What the heck.
> >
> > What architecture is this? Please send the full .config.
> >
> > And exactly which kernel version is in use?
>
> It's a arm7tdmi SoC (GeneralPlus gpl32700 SoC).
> The code is: current Linus' tree + patches for this SoC.
> The patches for this SoC includes:
> irqchip, clocksource, pinctrl, gpio, uart, spi, sd/mmc host drivers.
> I also apply a out-of-tree sdio wifi driver for mt5931 wifi module.
Beats me, sorry - I don't see anything which could cause this in the
arm spinlock implementation, even if the spinlock's storage got
corrupted.
> I can successfully boot and running busybox if using ext2 as root.
> Thus I don't hit "spin_unlock_irq decrement preempt_count failure" if using ext2 as root.
> The storage is a spi nor flash, so I prefer to use jffs2 but then I got
> the hangup.
>
> BTW, I got below panic today:
>
> 467: 0
> 470: 0
> 475: 1
> 485: 1
> 487: 2
> 489: 2
> 491: 1
> 494: 1
> 496: 1
> 498: 1
> BUG: spinlock bad magic on CPU#0, spi0/30
Which is what appears to have happened here.
I assume earlier kernels worked OK with this config?
If so, all I can suggest is a git bisection search :(
prev parent reply other threads:[~2013-12-05 7:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-01 10:53 BUG: sleeping function called from invalid context at kernel/locking/mutex.c:616 Axel Lin
2013-12-04 8:13 ` Axel Lin
2013-12-04 8:31 ` Andrew Morton
2013-12-04 8:59 ` Axel Lin
2013-12-04 21:32 ` Andrew Morton
2013-12-05 7:12 ` Axel Lin
2013-12-05 7:22 ` Andrew Morton [this message]
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=20131204232251.73cc62c6.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=artem.bityutskiy@linux.intel.com \
--cc=axel.lin@ingics.com \
--cc=computersforpeace@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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