From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: BUG: spinlock recursion (sys_chdir, user_path_at, do_path_lookup ...)
Date: Wed, 12 Jan 2011 11:57:50 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1101121153370.12146@localhost6.localdomain6> (raw)
In-Reply-To: <20110112075229.GZ24920@pengutronix.de>
On Wed, 12 Jan 2011, Uwe Kleine-K?nig wrote:
> > [ 75.280000] r5:be961ee4 r4:00063015
> >
> > I started to bisect, but already the first test case showed a different
> > error (my getty dying every few seconds).
> I bisected this one now, the first bad commit is
>
> 9c0729d (x86: Eliminate bp argument from the stack tracing routines)
>
> . It made a x86 specific change to include/linux/stacktrace.h.
As I said on IRC already, that's complete nonsense. The commit changes
a function prototype which is only relevant for x86. So how should
that affect ARM ?
> According to tglx the lockup above "is related to nicks scalability
> stuff". I havn't researched yet the offending commit. Is that
> necessary?
Only if you are interested that the problem gets fixed.
Thanks,
tglx
next prev parent reply other threads:[~2011-01-12 10:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 11:05 BUG: spinlock recursion (sys_chdir, user_path_at, do_path_lookup ...) Uwe Kleine-König
2011-01-12 7:52 ` Uwe Kleine-König
2011-01-12 10:57 ` Thomas Gleixner [this message]
2011-01-12 12:03 ` Uwe Kleine-König
2011-01-12 12:35 ` Russell King - ARM Linux
2011-01-12 12:48 ` Russell King - ARM Linux
2011-01-12 12:56 ` Thomas Gleixner
2011-01-18 16:59 ` Maciej Rutecki
2011-01-18 22:19 ` Nick Piggin
2011-01-19 7:43 ` Uwe Kleine-König
-- strict thread matches above, loose matches on Subject: below --
2011-01-12 20:59 Ramirez Luna, Omar
2011-01-12 21:02 ` Uwe Kleine-König
2011-01-12 21:16 ` Ramirez Luna, Omar
2011-01-12 22:52 ` Thomas Gleixner
2011-01-13 8:09 ` Uwe Kleine-König
2011-01-13 11:01 ` Peter Zijlstra
2011-01-13 11:17 ` Peter Zijlstra
2011-01-13 11:21 ` Thomas Gleixner
2011-01-13 11:37 ` Peter Zijlstra
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=alpine.LFD.2.00.1101121153370.12146@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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