All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Niels Wellens <niels.wellens@triphase.com>,
	"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] xeno3_rc3 - Watchdog detected hard LOCKUP
Date: Fri, 13 Mar 2015 17:25:28 +0100	[thread overview]
Message-ID: <55030F78.3040300@siemens.com> (raw)
In-Reply-To: <5501FC89.2040205@siemens.com>

On 2015-03-12 21:52, Jan Kiszka wrote:
> I finally started some tests here as well with your config, but I don't
> expect results soon (if at all), given your long times to reproduce
> things. 

As expected, the issue refuses to show up here so far.

> I will also make some new patches available soon that target
> very specific corner cases in kernel exception handling. However, these
> patches will apply to both 3.16 and 3.14, so nothing that could easily
> explain your issues.

Those patches are now available at
http://git.xenomai.org/ipipe-jki.git/log/?h=for-upstream/master. Maybe
we are lucky and the change something on your side. Please give them a try.

Jan

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


  reply	other threads:[~2015-03-13 16:25 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26 10:08 [Xenomai] xeno3_rc3 - Watchdog detected hard LOCKUP Niels Wellens
2015-02-26 10:20 ` Gilles Chanteperdrix
     [not found]   ` <54EF0790.3040607@triphase.com>
2015-02-27 14:10     ` Niels Wellens
2015-02-27 20:32       ` Jan Kiszka
2015-02-27 20:36         ` Gilles Chanteperdrix
2015-02-27 20:39           ` Jan Kiszka
2015-03-03  8:11         ` Jan Kiszka
2015-03-04 20:35           ` Jeroen Van den Keybus
2015-03-09 14:56             ` Niels Wellens
2015-03-12 20:52               ` Jan Kiszka
2015-03-13 16:25                 ` Jan Kiszka [this message]
2015-03-13 16:34                 ` Gilles Chanteperdrix
2015-03-13 17:09                   ` Jan Kiszka
2015-03-13 17:12                     ` Gilles Chanteperdrix
2015-04-02 18:47                       ` Jeroen Van den Keybus
2015-04-02 19:15                         ` Gilles Chanteperdrix
2015-04-02 19:29                           ` Jeroen Van den Keybus
2015-04-02 20:41                             ` Gilles Chanteperdrix
2015-04-08 21:02                               ` Jeroen Van den Keybus
2015-04-09  9:04                                 ` Jan Kiszka
2015-04-09  9:14                                   ` Jan Kiszka
2015-04-09  9:26                                     ` Jan Kiszka
2015-04-09 12:41                                     ` Gilles Chanteperdrix
2015-04-09 12:49                                       ` Jan Kiszka
2015-04-09 12:56                                         ` Gilles Chanteperdrix
2015-04-09 12:58                                         ` Gilles Chanteperdrix
2015-04-09 13:01                                           ` Jan Kiszka
2015-04-21 21:14                                             ` Jeroen Van den Keybus
2015-04-22  5:14                                               ` Jan Kiszka
2015-04-22 19:22                                                 ` Jeroen Van den Keybus
2015-04-28 19:12                                                   ` Jeroen Van den Keybus
2015-04-29  6:36                                                     ` 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=55030F78.3040300@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=niels.wellens@triphase.com \
    --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.