From: Stanislav Meduna <stano@meduna.org>
To: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
triplesquarednine@gmail.com
Cc: Linux ARM Kernel <linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
bigeasy@linutronix.de, Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: BUG: spinlock trylock failure on UP - reverting timer patches helps
Date: Fri, 18 Apr 2014 00:55:19 +0200 [thread overview]
Message-ID: <53505BD7.9050004@meduna.org> (raw)
In-Reply-To: <53500184.4050309@meduna.org>
On 17.04.2014 18:29, Stanislav Meduna wrote:
> Note: the bug goes away reverting the very same patches that are
> helping the Jordan's problms. I did follow
>
> http://www.spinics.net/lists/linux-rt-users/msg11639.html
>
> and no BUG while booting anymore. I'll try to let it run some
> more time.
Erm.. nope
# (cat /proc/meminfo ; cat /proc/meminfo) | grep KernelStack
KernelStack: 5920 kB
KernelStack: 5928 kB
# (cat /proc/meminfo ; cat /proc/meminfo) | grep KernelStack
KernelStack: 5952 kB
KernelStack: 5960 kB
maybe interrupt nesting ad nauseum? How does one debug
such issues?
It is possible that my previous posting was also caused by this -
disregard, I'll post again if the problem persists.
Jordan, could you check whether your kernel stack remains
stable with only the 3 patches reverted?
Thanks
--
Stano
WARNING: multiple messages have this Message-ID (diff)
From: stano@meduna.org (Stanislav Meduna)
To: linux-arm-kernel@lists.infradead.org
Subject: BUG: spinlock trylock failure on UP - reverting timer patches helps
Date: Fri, 18 Apr 2014 00:55:19 +0200 [thread overview]
Message-ID: <53505BD7.9050004@meduna.org> (raw)
In-Reply-To: <53500184.4050309@meduna.org>
On 17.04.2014 18:29, Stanislav Meduna wrote:
> Note: the bug goes away reverting the very same patches that are
> helping the Jordan's problms. I did follow
>
> http://www.spinics.net/lists/linux-rt-users/msg11639.html
>
> and no BUG while booting anymore. I'll try to let it run some
> more time.
Erm.. nope
# (cat /proc/meminfo ; cat /proc/meminfo) | grep KernelStack
KernelStack: 5920 kB
KernelStack: 5928 kB
# (cat /proc/meminfo ; cat /proc/meminfo) | grep KernelStack
KernelStack: 5952 kB
KernelStack: 5960 kB
maybe interrupt nesting ad nauseum? How does one debug
such issues?
It is possible that my previous posting was also caused by this -
disregard, I'll post again if the problem persists.
Jordan, could you check whether your kernel stack remains
stable with only the 3 patches reverted?
Thanks
--
Stano
next prev parent reply other threads:[~2014-04-17 22:55 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 19:24 BUG: spinlock trylock failure on UP, i.MX28 3.12.15-rt25 Stanislav Meduna
2014-04-14 23:45 ` Stanislav Meduna
2014-04-14 23:45 ` Stanislav Meduna
2014-04-15 22:08 ` Stanislav Meduna
2014-04-15 22:08 ` Stanislav Meduna
2014-04-17 16:29 ` BUG: spinlock trylock failure on UP - reverting timer patches helps Stanislav Meduna
2014-04-17 16:29 ` Stanislav Meduna
2014-04-17 22:55 ` Stanislav Meduna [this message]
2014-04-17 22:55 ` Stanislav Meduna
2014-04-17 23:10 ` jordan
2014-04-17 23:10 ` jordan
2014-04-18 1:15 ` jordan
2014-04-18 1:15 ` jordan
2014-04-18 1:15 ` jordan
2014-04-18 14:45 ` Stanislav Meduna
2014-04-18 14:45 ` Stanislav Meduna
2014-04-18 15:09 ` jordan
2014-04-18 15:09 ` jordan
2014-04-22 11:54 ` BUG: spinlock trylock failure on UP, i.MX28 3.12.15-rt25 Sebastian Andrzej Siewior
2014-04-22 11:54 ` Sebastian Andrzej Siewior
2014-04-22 13:46 ` Steven Rostedt
2014-04-22 13:46 ` Steven Rostedt
2014-04-22 14:09 ` Peter Zijlstra
2014-04-22 14:09 ` Peter Zijlstra
2014-04-23 8:10 ` Sebastian Andrzej Siewior
2014-04-23 8:10 ` Sebastian Andrzej Siewior
2014-04-23 8:50 ` Peter Zijlstra
2014-04-23 8:50 ` Peter Zijlstra
2014-04-22 16:51 ` Sebastian Andrzej Siewior
2014-04-22 16:51 ` Sebastian Andrzej Siewior
2014-04-22 17:48 ` Steven Rostedt
2014-04-22 17:48 ` Steven Rostedt
2014-04-22 18:16 ` Steven Rostedt
2014-04-22 18:16 ` Steven Rostedt
2014-04-23 7:14 ` Sebastian Andrzej Siewior
2014-04-23 7:14 ` Sebastian Andrzej Siewior
2014-04-23 8:49 ` Peter Zijlstra
2014-04-23 8:49 ` Peter Zijlstra
2014-04-23 12:15 ` Steven Rostedt
2014-04-23 12:15 ` Steven Rostedt
2014-05-02 18:38 ` Sebastian Andrzej Siewior
2014-05-02 18:38 ` Sebastian Andrzej Siewior
2014-05-02 19:01 ` Thomas Gleixner
2014-05-02 19:01 ` Thomas Gleixner
2014-05-02 19:36 ` Thomas Gleixner
2014-05-02 19:36 ` Thomas Gleixner
2014-05-02 19:37 ` Sebastian Andrzej Siewior
2014-05-02 19:37 ` Sebastian Andrzej Siewior
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=53505BD7.9050004@meduna.org \
--to=stano@meduna.org \
--cc=bigeasy@linutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=triplesquarednine@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.