All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Petr Cervenka <grugh@domain.hid>
Cc: xenomai-help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Kernel panic: not syncing - part 2
Date: Mon, 08 Dec 2008 17:58:49 +0100	[thread overview]
Message-ID: <493D5249.8030909@domain.hid> (raw)
In-Reply-To: <200812081718.8273@domain.hid>

Petr Cervenka wrote:
> Hello again,
> I have though, that all my troubles with this kernel panic (see https://mail.gna.org/public/xenomai-help/2008-07/msg00054.html) are over, but suddenly it reappeared.
> The full log is in attachment. I used snapshot of screen, OCR program and manual correction, so expect possible errors in log.
> I haven't seen the error for months, I was believed that it was caused the combination of other two problems (hopefully already solved or evaded). But this kernel panic emerged  during the weekend test, when we tested usability of a new motherboard for our purposes.
> It's perhaps not critical for me, but if you have any advices or questions, I'm listening.

Due to the interrupt deferral the I-pipe enforces, it may well happen that we
log and postpone a timer IRQ while the root stage is stalled during a task
switch, which gets eventually played right after the context switch has taken
place, after a different memory context for the next task is reinstated. The
profiler code then tries to dereference a memory address obtained from the IRQ
stack frame that does not exist in the new context. Too bad.

Ok, we need to think about this.

> Thanks
> Petr
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help


-- 
Philippe.


      reply	other threads:[~2008-12-08 16:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200812081707.22246@domain.hid>
     [not found] ` <200812081708.3537@domain.hid>
     [not found]   ` <200812081709.17083@domain.hid>
     [not found]     ` <200812081710.4784@domain.hid>
     [not found]       ` <200812081711.32480@domain.hid>
     [not found]         ` <200812081712.4953@domain.hid>
     [not found]           ` <200812081713.10238@domain.hid>
     [not found]             ` <200812081714.30317@domain.hid>
2008-12-08 16:18               ` [Xenomai-help] Kernel panic: not syncing - part 2 Petr Cervenka
2008-12-08 16:58                 ` Philippe Gerum [this message]

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=493D5249.8030909@domain.hid \
    --to=rpm@xenomai.org \
    --cc=grugh@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.