From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: nando@ccrma.Stanford.EDU,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
John Kacur <jkacur@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3.12.9-rt13: BUG: soft lockup
Date: Fri, 14 Feb 2014 10:54:57 -0800 [thread overview]
Message-ID: <52FE6681.8090807@ccrma.stanford.edu> (raw)
In-Reply-To: <alpine.DEB.2.02.1402141040460.21991@ionos.tec.linutronix.de>
On 02/14/2014 02:43 AM, Thomas Gleixner wrote:
> On Thu, 13 Feb 2014, Fernando Lopez-Lezcano wrote:
>> On 02/13/2014 03:55 PM, Thomas Gleixner wrote:
>>> On Thu, 13 Feb 2014, Fernando Lopez-Lezcano wrote:
>>>
>>>> On 02/13/2014 02:25 PM, Thomas Gleixner wrote:
>>>>> On Wed, 12 Feb 2014, Fernando Lopez-Lezcano wrote:
>>>>>> [771508.546449] RIP: 0010:[<ffffffff810dc60a>] [<ffffffff810dc60a>]
>>>>>> smp_call_function_many+0x2ca/0x330
>>>>>
>>>>> Can you decode the exact location inside of smp_call_function_many via
>>>>> addr2line please ?
>>
>> # addr2line -e
>> /usr/lib/debug/lib/modules/3.12.9-301.rt13.1.fc20.ccrma.x86_64+rt/vmlinux
>> ffffffff810dc60e
>> /usr/src/debug/kernel-3.12.fc20.ccrma/linux-3.12.9-301.rt13.1.fc20.ccrma.x86_64/kernel/smp.c:108
>
> So it's stuck in csd_lock_wait(), which means that the csd of the
> target cpu is not free.
>
> Is the machine completely dead or can you still retrieve information
> from it?
After migrating to fc20/3.12.x-rtyy I started experiencing freezes in
some workstations. This coincided with one of our students running high
cpu load multi-core computations in them (he had been doing that before
under 3.10.x-rtyy with no problems). In the morning I would find
workstations unresponsive and catatonic. Probably his software was still
eating up cpu as the machines were warm (ie: still under load). No pings
back or keyboard/mouse/display response.
This was the only time I could get information from a machine while it
was in the process of freezing up - but this might have been a different
issue. I was ssh'd in and that terminal became unresponsive. I managed
to ssh in again and looked at the logs. The machine was not completely
frozen but it eventually became completely catatonic. For all I know
this might be different from the locked machines syndrome as it left
traces in the logs (I could forward you all the log entries if you want).
I could try to boot one of the machines into 3.12.xrtyy, replicate the
conditions and wait. What should I look for if I can catch this in the act?
-- Fernando
next prev parent reply other threads:[~2014-02-14 18:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 22:17 3.12.9-rt13: BUG: soft lockup Fernando Lopez-Lezcano
2014-02-13 22:25 ` Thomas Gleixner
2014-02-13 22:56 ` Fernando Lopez-Lezcano
2014-02-13 23:55 ` Thomas Gleixner
2014-02-14 6:26 ` Fernando Lopez-Lezcano
2014-02-14 10:43 ` Thomas Gleixner
2014-02-14 18:54 ` Fernando Lopez-Lezcano [this message]
2014-02-19 9:50 ` Thomas Gleixner
2014-03-07 13:15 ` Sebastian Andrzej Siewior
2014-03-07 13:13 ` 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=52FE6681.8090807@ccrma.stanford.edu \
--to=nando@ccrma.stanford.edu \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).