All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Wolfgang Grandegger <wg@domain.hid>
Cc: xenomai-help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Using Xenomai in early boot phase.
Date: Tue, 04 Nov 2008 11:21:10 +0100	[thread overview]
Message-ID: <49102216.9030207@domain.hid> (raw)
In-Reply-To: <49101EBE.9090007@domain.hid>

Wolfgang Grandegger wrote:
> Wolfgang Grandegger wrote:
>> Philippe Gerum wrote:
>>> Wolfgang Grandegger wrote:
>>>> Hello,
>>>>
>>>> I want to use a Xenomai task overtaking the duties of a watchdog running
>>>> under Linux as soon as the Xenomai layer is available during boot up. Is
>>>>   there a function or variable I could inspect? With 2.3.x, I called
>>>> rtdm_init_task() until it returned without error but with 2.4.x it
>>>> results in a kernel crash :-(.
>>>>
>>> What is the value of CONFIG_XENO_OPT_SYS_STACKPOOLSZ?
>>   #
>>   # Nucleus options
>>   #
>>   CONFIG_XENO_OPT_PERVASIVE=y
>>   CONFIG_XENO_OPT_SYS_STACKPOOLSZ=32
>>   # CONFIG_XENO_OPT_PRIOCPL is not set
>>   CONFIG_XENO_OPT_PIPE=y
> 
> Some more input on that issue. Here is the oops and the NIP location:
> 
> XLB Arb cnf: 8000a006
> mpc5xxx_ide: Setting up IDE interface ide0...
> Probing IDE interface ide0...
> Oops: kernel access of bad area, sig: 11
> NIP: C0113364 XER: 20000000 LR: C0113320 SP: C047DB30 REGS: c047da80 TRAP: 0300    Not tainted
> MSR: 00001032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
> DAR: 0000003C, DSISR: 20000000
> TASK = c047c000[1] 'swapper' Last syscall: 120
> last math 00000000 last altivec 00000000
> GPR00: 00000003 C047DB30 C047C000 00000009 FFFFFFF7 C01CF395 C0220000 00000000
> GPR08: 00000038 C01ECC00 C02445F4 00000000 00000000 100803B0 07FCF000 08099000
> GPR16: C0220000 FFFFFF7F C0230000 FFF75F97 C022B3C0 00000000 C01ECC0C C0230000
> GPR24: 00000000 00000000 00000010 C02446F4 3B9A0000 00000000 00000000 C0244590
> Call backtrace:
> C0113320 C0111F00 C010DD0C C013D810 C00DA48C C001EAB4 C001A70C
> C001A598 C001A254 C00079C0 C000D63C C0024C50 C00243AC C000D298
> C000D508 C0005CF4 0039FBC0 C00F0A4C C00F0EA0 C00F15C0 C00F210C
> C02149C8 C0214A14 C020A64C C00039A0 C0008678
> Kernel panic: Aiee, killing interrupt handler!
> In interrupt handler - not syncing
>  <0>Rebooting in 180 seconds..
> 
> $ ppc_6xx-gdb vmlinux:
> ...
> (gdb) l *0xC0113364
> 0xc0113364 is in __xntimer_init (queue.h:51).
> 46              holder->last = holder;
> 47              holder->next = holder;
> 48      }
> 49
> 50      static inline void ath(xnholder_t *head, xnholder_t *holder)
> 51      {
> 52              /* Inserts the new element right after the heading one  */
> 53              holder->last = head;
> 54              holder->next = head->next;
> 55              holder->next->last = holder;
> 
> Wolfgang.
> 

Thanks. Could you send me the full boot log until the oops occurs as well? TIA,

-- 
Philippe.


  reply	other threads:[~2008-11-04 10:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03 14:36 [Xenomai-help] Using Xenomai in early boot phase Wolfgang Grandegger
2008-11-03 14:39 ` Philippe Gerum
2008-11-04  8:16   ` Wolfgang Grandegger
2008-11-04 10:06     ` Wolfgang Grandegger
2008-11-04 10:21       ` Philippe Gerum [this message]
2008-11-04 12:05         ` Wolfgang Grandegger
2008-11-04 12:24           ` Philippe Gerum
2008-11-04 12:38             ` Wolfgang Grandegger
2008-11-04 14:04               ` Philippe Gerum
2008-11-05 18:52                 ` Wolfgang Grandegger
2008-11-05 18:58                   ` Jan Kiszka
2008-11-06  7:32                     ` Wolfgang Grandegger
2008-11-05 19:48                   ` Philippe Gerum
2008-11-05 19:49                     ` Philippe Gerum

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=49102216.9030207@domain.hid \
    --to=rpm@xenomai.org \
    --cc=wg@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.