All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Kai Bollue <mlist1@bollue.de>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Sporadic freeze using RTnet
Date: Tue, 23 Apr 2013 16:05:03 +0200	[thread overview]
Message-ID: <5176950F.3040702@siemens.com> (raw)
In-Reply-To: <51769250.7050504@bollue.de>

On 2013-04-23 15:53, Kai Bollue wrote:
> Hello Jan,
> thank you for your reply.
> 
> On 23.04.2013 14:18, Jan Kiszka wrote:
>> Does sysrq still work then? sysrq-l would be interesting e.g.
> 
> No. It works before the freeze (so it's set up correctly), but not 
> afterwards.
> 
>>> - Either nothing at all, or
>>>
>>> -
>>> [  481.189349] INFO: rcu_bh detected stalls on CPUs/tasks: { 2}
>>> (detected by 0, t=60042 jiffies)
>>> [  481.291572] INFO: Stall ended before state dump start
>>> [  541.224383] INFO: rcu_preempt detected stalls on CPUs/tasks: { 2}
>>> (detected by 0, t=60002 jiffies)
>>> [  541.331818] INFO: Stall ended before state dump start
>>> (repeated), or
>>>
>>> -
>>> [ 2333.757994] Xenomai: Unbalanced lock/unlock
>> Ah, here's where the problem start.
>>
>> CONFIG_IPIPE_TRACE_PANIC may provide further information. Enable it via
>> the I-pipe tracer. Then, before triggering the lockup, increase the
>> backtrace points to, say, 2000:
>>
>> echo 2000 > /proc/ipipe/trace/back_trace_points
> 
> New console output attached.

Hmm, broken in several ways. First of all, backtraces aren't working
properly in your setup. Please enable CONFIG_FRAME_POINTER. You can
leave the ipipe tracer knob above at its default for the next run, and
no need for the sysrq-l to repeat.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux


  reply	other threads:[~2013-04-23 14:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-22 17:50 [Xenomai] Sporadic freeze using RTnet Kai Bollue
2013-04-23 12:18 ` Jan Kiszka
2013-04-23 13:53   ` Kai Bollue
2013-04-23 14:05     ` Jan Kiszka [this message]
     [not found]       ` <5176AB28.7000305@bollue.de>
2013-04-23 15:43         ` Jan Kiszka
2013-04-23 17:12           ` Kai Bollue
2013-04-23 17:18             ` Jan Kiszka
2013-04-23 19:28               ` Kai Bollue
2013-04-24  7:49                 ` Jan Kiszka
2013-04-24 12:41                   ` Kai Bollue
2013-04-25 16:16                     ` Jan Kiszka
2013-04-29 18:34                       ` Kai Bollue
2013-04-29 18:42                         ` Jan Kiszka
2013-05-02 17:05                           ` Kai Bollue
2013-05-09 10:47                             ` Jan Kiszka

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=5176950F.3040702@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=mlist1@bollue.de \
    --cc=xenomai@xenomai.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 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.