All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Roman Pisl <rpisl@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Freeze on SMP x86-64
Date: Tue, 06 Oct 2009 17:59:43 +0200	[thread overview]
Message-ID: <4ACB696F.3080907@domain.hid> (raw)
In-Reply-To: <4ACB6626.6020707@domain.hid>

Roman Pisl wrote:
> On 6.10.2009 15:56, Jan Kiszka wrote:
>> Roman Pisl wrote:
>>> ...
>>>> Is there a chance to grab the panic log via serial line? The first of
>>>> your two screenshots indicate that there might have happened something
>>>> interesting before the NMI triggered, but it's scrolled out of sight.
>>>>
>>>> Jan
>>>>
>>> Hello,
>>> here I send kernel panic (triggered by rt_task_sleep and latency test)
>>> grabbed via serial line.
>> Hmm, still only NMI alarms...
>>
>>> I'm ready to help with resolving this issue.
>> Could you try enabling the I-pipe tracer with function tracing? It
>> should dump a trace of the functions that were executed before the
>> watchdog triggered. You may need to extend the number of tracepoints a
>> bit, try "echo 1000>  /proc/ipipe/trace/back_trace_points".
>>
>> Jan
>>
> 
> Then I had I/O activity on the background and got this.
> 

Try without CONFIG_IPIPE_DEBUG_INTERNAL (it triggers when we printk from
NMI context). Please also raise the NMI threshold
(CONFIG_XENO_HW_NMI_DEBUG_LATENCY_MAX) to 1 ms or so. It may otherwise
trigger too early if there are hardware related delays + the tracing
overhead.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux


  reply	other threads:[~2009-10-06 15:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02 11:48 [Xenomai-help] Freeze on SMP x86-64 Roman Pisl
2009-10-02 12:39 ` Gilles Chanteperdrix
2009-10-02 13:22   ` Roman Pisl
2009-10-02 13:25     ` Gilles Chanteperdrix
2009-10-02 13:34     ` Philippe Gerum
2009-10-02 13:36       ` Philippe Gerum
2009-10-03 16:01     ` Jan Kiszka
     [not found]       ` <4AC9E655.5090006@domain.hid>
     [not found]         ` <4AC9ED6B.4050004@domain.hid>
     [not found]           ` <4AC9F4FA.5070409@domain.hid>
     [not found]             ` <4ACA013F.8040602@domain.hid>
2009-10-06 13:18               ` Roman Pisl
2009-10-06 13:56                 ` Jan Kiszka
2009-10-06 14:50                   ` Roman Pisl
2009-10-06 15:33                   ` Roman Pisl
2009-10-06 15:45                   ` Roman Pisl
2009-10-06 15:59                     ` Jan Kiszka [this message]
2009-10-02 12:45 ` Peter Soetens
2009-10-02 12:58   ` Roman Pisl
2009-10-02 13:40 ` Philippe Gerum
2009-10-02 14:14   ` Roman Pisl
2009-10-02 16:40     ` Gilles Chanteperdrix
2009-10-02 14:21 ` 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=4ACB696F.3080907@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=rpisl@domain.hid \
    --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.