All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai@xenomai.org, "Brian L." <bluczkie@domain.hid>
Subject: Re: [Xenomai-help] Panic in rt_queue_create: bug or misuse?
Date: Tue, 04 Apr 2006 14:56:31 +0200	[thread overview]
Message-ID: <44326CFF.6070700@domain.hid> (raw)
In-Reply-To: <44322BDD.8010706@domain.hid>

Jan Kiszka wrote:
> Philippe Gerum wrote:
> 
>>Brian L. wrote:
>>
>>>I apologize for not including the panic here. I will be obtaining a
>>>serial cable tomorrow and accessing panic text should become much
>>>simpler. Since the panic is several screen-fulls long, even if I were
>>>to painstakingly type it in, it would be missing vital information.
>>>
>>>I'm posting this now in case this is a known issue with a simple fix.
>>>Newsgroup history doesn't turn up any messages with rt_queue_create
>>>and panic in the past few months. I am running xenomai 2.1.0 on linux
>>>2.6.15 with APIC disabled in kernel config on a celeron 566/440bx.
>>>
>>>Code:
>>>======
>>>int main() {
>>>RT_TASK main_task;
>>>RT_QUEUE queue;
>>>RT_MUTEX lock;
>>>
>>
>>   mlockall(MCL_CURRENT|...) ?
> 
> 
> Would this excuse the panic?
> 

I would expect the thread to be relaxed by Xeno so that the fixup and 
later paging in happen properly, but given the few bits given here, I'm 
trying to rule out unexpected page faulting issues.

> 
>>>if (0 != rt_task_shadow(&main_task,"MAIN",1,T_FPU)) {
>>>   die("Couldn't Shadow Main Task\n");
>>>}
>>>
>>>rt_mutex_create(&lock,0);
>>>rt_queue_create(&queue,"log_queue",8192,100,Q_FIFO);
>>>...
>>>}
>>>======
>>>
>>>The kernel panics and freezes the test machine in rt_queue_create. I
>>>will post panic text as soon as it is accessible to me. The panic
>>>occurs whether or not I shadow the main task and whether or not the
>>>mutex is named. Am I misusing an API or am I possibly looking at a
>>>bug?
>>>
>>>The bottom 25 lines of the panic seem to involve a call to the ipipe
>>>exception handler every 6-8 lines. It doesn't look like endless
>>>recursion, though, so we could just be walking up an exception tree.
>>>I'm missing the top of the trace and the panic type because it doesn't
>>>get logged and I can't scroll a frozen machine.
>>>
>>>Thanks,
>>>
>>>Brian
>>>
>>>_______________________________________________
>>>Xenomai-help mailing list
>>>Xenomai-help@domain.hid
>>>https://mail.gna.org/listinfo/xenomai-help
>>>
>>
>>
> 
> 


-- 

Philippe.


  parent reply	other threads:[~2006-04-04 12:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04  6:04 [Xenomai-help] Panic in rt_queue_create: bug or misuse? Brian L.
2006-04-04  7:53 ` Philippe Gerum
2006-04-04  8:18   ` Jan Kiszka
2006-04-04 12:53     ` Brian L.
2006-04-04 13:08       ` Jan Kiszka
2006-04-04 13:52         ` [Xenomai-core] " Philippe Gerum
2006-04-04 12:56     ` Philippe Gerum [this message]
2006-04-04 13:06 ` 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=44326CFF.6070700@domain.hid \
    --to=rpm@xenomai.org \
    --cc=bluczkie@domain.hid \
    --cc=jan.kiszka@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.