All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: "Alessio Margan @ IIT" <alessio.margan@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] kernel panic unload xeno_nucleus module
Date: Wed, 11 Apr 2012 11:28:49 +0200	[thread overview]
Message-ID: <4F854ED1.8010102@domain.hid> (raw)
In-Reply-To: <4F854D1E.7010200@domain.hid>

On 04/11/2012 11:21 AM, Alessio Margan @ IIT wrote:
> On 04/11/2012 11:14 AM, Philippe Gerum wrote:
>> On 04/11/2012 10:58 AM, Alessio Margan @ IIT wrote:
>>> Hi all,
>>>
>>> when I try to unload xeno_nucleus module I get a kernel panic and on the
>>> next power on the bios system date is reset.
>>> when configure xenomai nucleus built into the kernel I can reboot correctly.
>>>
>> Kernel panic log would help.
>>
> I'll try to get it
>>> In the bios I disabled HPET and most of the things regarding PM and ACPI.
>>>
>>> Here attached same info about system and kernel config.
>>>
>>> If possible, I prefer have xenomai configured as modules, is there
>>> anything wrong about my system configuration ?
>>>
>> This should not be a configuration issue. Either some kernel-based
>> Xenomai threads (e.g. RTDM driver thread) are still running when
>> attempting to unload the nucleus, or a real-time IRQ is still hooked to
>> a handler being unmapped, or there is a nucleus bug.
>>
> after boot the only thing I do is load nucleus and unload it, no other
> xenomai modules are loaded

Ok, so this must be a Xenomai bug.

>>
> Thanks
> Alessio
>
> --
>
> ISTITUTO ITALIANO
> DI TECNOLOGIA
>
> Alessio Margan
> /Senior Technician/
> mail me <mailto:alessio.margan@domain.hid>
>
> Via Morego, 30 16163 Genova
> <http://maps.google.com/maps?f=q&hl=en&geocode=&q=via+morego,+30+genova&sll=37.0625,-95.677068&sspn=85.420533,191.601563&ie=UTF8&ll=44.474913,8.907037&spn=0.004685,0.011652&t=h&z=17&iwloc=addr>
>
> www.iit.it <http://www.iit.it>
>
> *Legal Disclaimer*
> This electronic message contains information that is confidential. The
> information is intended for the use of the addressee only. If you are
> not the addressee we would appreciate your notification in this respect.
> Please note that any disclosure, copy, distribution or use of the
> contents of this message is prohibited and may be unlawful. We have
> taken every reasonable precaution to ensure that any kind of attachment
> to this e-mail has been swept for viruses. However, we cannot accept
> liability for any damage sustained as a result of software viruses and
> would advise you to carry out your own virus checks before opening any
> attachment.
> *Avvertenza legale*
> Questo messaggio Email contiene informazioni confidenziali riservate ai
> soli destinatari. Qualora  veniate in possesso di tali informazioni
> senza essere definito come destinatario vi reghiamo di leggere le
> seguenti note. Ogni apertura, copia, distribuzione del contenuto del
> messaggio e dei suoi allegati è proibito e potrebbe violare le presenti
> leggi. Abbiamo attivato ogni possibile e ragionevole precauzione per
> assicurare che gli allegati non contengano virus. Comunque non
> assumeremo alcuna responsabilità per ogni eventuale danno causato da
> virus software e simili in quanto è onere del destinatario verificarne
> l’assenza in ogni allegato attuando propri indipendenti controlli.
>
>
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help


-- 
Philippe.


  reply	other threads:[~2012-04-11  9:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11  8:58 [Xenomai-help] kernel panic unload xeno_nucleus module Alessio Margan @ IIT
2012-04-11  9:14 ` Philippe Gerum
2012-04-11  9:21   ` Alessio Margan @ IIT
2012-04-11  9:28     ` Philippe Gerum [this message]
2012-04-11  9:30     ` 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=4F854ED1.8010102@domain.hid \
    --to=rpm@xenomai.org \
    --cc=alessio.margan@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.