All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Xenomai-core@domain.hid
Subject: [Xenomai-core] Re: soft lockup detected on AT91RM9200
Date: Fri, 23 Feb 2007 12:17:38 +0100	[thread overview]
Message-ID: <45DECD52.5010305@domain.hid> (raw)
In-Reply-To: <45DEC477.2070901@domain.hid>

Gilles,

>> When starting latency with 100µs period I get
>>
>> ~ # latency
>> == Sampling period: 100 us
>> == Test mode: periodic user-mode task
>> == All results in microseconds
>> warming up...
>> BUG: soft lockup detected on CPU#0!
>> ...
>>
>> Ideas? How can I help with debugging this?
> 
> 100us is too small, as I already told you here:
> 
> https://mail.gna.org/public/xenomai-core/2007-02/msg00019.html

No. That's probably a different thing. I am going to write a mail soon.

> The latency process spend 100% of its time handling the timer ticks, and
> the kernel detects a soft lockup.
> 
> The difference between I-pipe patch 1.6-01 and 1.6-02 is that the return
> from exception is correctly handled. Maybe it is what allows the kernel
> to print a clean message. Maybe it is because you now have enabled the
> soft lockup detector whereas you previously did not.
Ok. Maybe.

I don't care about missing deadlines. That's fine iff I overload the system.

But I still would have expected printout on the serial console. But ok,
maybe the print in latency is done in a non-realtime task. So fair enough.

Steven


  reply	other threads:[~2007-02-23 11:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23 10:17 [Xenomai-core] soft lockup detected on AT91RM9200 Steven Scholz
2007-02-23 10:39 ` [Xenomai-core] " Gilles Chanteperdrix
2007-02-23 11:17   ` Steven Scholz [this message]
2007-02-23 10:40 ` [Xenomai-core] " 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=45DECD52.5010305@domain.hid \
    --to=steven.scholz@domain.hid \
    --cc=Xenomai-core@domain.hid \
    --cc=gilles.chanteperdrix@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.