Problem inserting rtai_hal in dual core Centrino

Wed Jun 28 17:07:16 CEST 2006

Ok.

But that is not the cause to the described behaviour. Or is?

If is, why i can't rmmod any scheduler module i insert in the kernel?

Jorge

Em Wednesday 28 June 2006 17:58, o Paolo Mantegazza escreveu:
> I forgot to tell you that I disable all of the kernel debugging. The 
> only thing I use are 4K stacks (in place of 8K), as working well with 
> them at the high frequencies we use is a good way to prove we can flood 
> interrupts without stack overflows. The downside with it is caring of 
> not using large sized buffer whe wroking with RTAI hardened kernel 
> thread, but it is juts a matter of staticalising data.
> 
> Paolo.
> 
> Jorge Almeida wrote:
> > Hello to all.
> > 
> > Several days ago i start this thread with the specified subject.
> > The Vulcano branch was update and i update also my system, but now another 
> > problem arises.
> > 
> > 
> > When i insert the rtai_hal.ko module the following errors appears in 
> > the /var/log/messages file 
> > 
> > Jun 28 10:23:47 main kernel: BUG: using smp_processor_id() in preemptible 
> > [00000001] code: insmod/7051
> > Jun 28 10:23:47 main kernel: caller is send_IPI_allbutself+0x10/0x2c
> > Jun 28 10:23:47 main kernel:  [<c01c4fa0>] 
debug_smp_processor_id+0xb0/0xd8
> > Jun 28 10:23:47 main kernel:  [<c0101219>] send_IPI_allbutself+0x10/0x2c
> > Jun 28 10:23:47 main kernel:  [<c0101219>] send_IPI_allbutself+0x10/0x2c
> > Jun 28 10:23:47 main kernel:  [<c0116a99>] ipipe_critical_enter+0x78/0x9d
> > Jun 28 10:23:47 main kernel:  [<f9328bad>] rtai_critical_enter+0xc/0x3d 
> > [rtai_hal]
> > Jun 28 10:23:47 main kernel:  [<f93295f4>] __rtai_hal_init+0xdf/0x2c2 
> > [rtai_hal]
> > Jun 28 10:23:47 main kernel:  [<f9329102>] rtai_lsrq_dispatcher+0x0/0x62 
> > [rtai_hal]
> > Jun 28 10:23:47 main kernel:  [<c013a4e6>] sys_init_module+0xad/0x2a1
> > Jun 28 10:23:47 main kernel:  [<c013a506>] sys_init_module+0xcd/0x2a1
> > Jun 28 10:23:47 main kernel:  [<c01040ac>] syscall_call+0x7/0xb
> > Jun 28 10:23:47 main kernel: BUG: using smp_processor_id() in preemptible 
> > [00000001] code: insmod/7051
> > Jun 28 10:23:47 main kernel: caller is send_IPI_allbutself+0x10/0x2c
> > Jun 28 10:23:47 main kernel:  [<c01c4fa0>] 
debug_smp_processor_id+0xb0/0xd8
> > Jun 28 10:23:47 main kernel:  [<c0101219>] send_IPI_allbutself+0x10/0x2c
> > Jun 28 10:23:47 main kernel:  [<c0101219>] send_IPI_allbutself+0x10/0x2c
> > Jun 28 10:23:47 main kernel:  [<c0116a99>] ipipe_critical_enter+0x78/0x9d
> > Jun 28 10:23:47 main kernel:  [<c0145352>] 
ipipe_register_domain+0x37/0x178
> > Jun 28 10:23:47 main kernel:  [<f932971e>] __rtai_hal_init+0x209/0x2c2 
> > [rtai_hal]
> > Jun 28 10:23:47 main kernel:  [<c0108e00>] 
> > dma_declare_coherent_memory+0xfd/0x139
> > Jun 28 10:23:47 main kernel:  [<f93285d8>] rtai_domain_entry+0x0/0x2c 
> > [rtai_hal]
> > Jun 28 10:23:47 main kernel:  [<c013a506>] sys_init_module+0xcd/0x2a1
> > Jun 28 10:23:47 main kernel:  [<c01040ac>] syscall_call+0x7/0xb
> > Jun 28 10:23:47 main kernel: BUG: using smp_processor_id() in preemptible 
> > [00000001] code: insmod/7051
> > Jun 28 10:23:47 main kernel: caller is send_IPI_allbutself+0x10/0x2c
> > Jun 28 10:23:47 main kernel:  [<c01c4fa0>] 
debug_smp_processor_id+0xb0/0xd8
> > Jun 28 10:23:47 main kernel:  [<c0101219>] send_IPI_allbutself+0x10/0x2c
> > Jun 28 10:23:47 main kernel:  [<c0101219>] send_IPI_allbutself+0x10/0x2c
> > Jun 28 10:23:47 main kernel:  [<c0116a99>] ipipe_critical_enter+0x78/0x9d
> > Jun 28 10:23:47 main kernel:  [<c014547e>] 
ipipe_register_domain+0x163/0x178
> > Jun 28 10:23:47 main kernel:  [<f932971e>] __rtai_hal_init+0x209/0x2c2 
> > [rtai_hal]
> > Jun 28 10:23:47 main kernel:  [<c0108e00>] 
> > dma_declare_coherent_memory+0xfd/0x139
> > Jun 28 10:23:47 main kernel:  [<f93285d8>] rtai_domain_entry+0x0/0x2c 
> > [rtai_hal]
> > Jun 28 10:23:47 main kernel:  [<c013a506>] sys_init_module+0xcd/0x2a1
> > Jun 28 10:23:47 main kernel:  [<c01040ac>] syscall_call+0x7/0xb
> > Jun 28 10:23:47 main kernel: I-pipe: Domain RTAI registered.
> > Jun 28 10:23:47 main kernel: RTAI[hal]: <3.4> mounted over IPIPE-NOTHREADS 
> > 1.3-00.
> > Jun 28 10:23:47 main kernel: RTAI[hal]: compiled with gcc version 4.1.0 
(SUSE 
> > Linux).
> > Jun 28 10:23:47 main kernel: RTAI[hal]: mounted (IPIPE-NOTHREADS, 
IMMEDIATE 
> > (INTERNAL IRQs VECTORED), ISOL_CPUS_MASK: 0).
> > Jun 28 10:23:47 main kernel: PIPELINE layers:
> > Jun 28 10:23:47 main kernel: f932f100 9ac15d93 RTAI 200
> > Jun 28 10:23:47 main kernel: c02f0100 0 Linux 100
> >  
> > And after i insert another scheduler module, lxrt or sched, i cannot 
remove it 
> > anymore. The rmmod command hangs and don't return anymore.
> > 
> > Does anyone have a clue for wath is appening?
> > 
> > Thanks in advance.
> > 
> > 
> > 
> > Em Wednesday 21 June 2006 16:58, o Jorge Almeida escreveu:
> > 
> >>Thanks for the quick reply.
> >>I check the patch ad it seems to be only for one PARAMETER.
> >>
> >>Please inform the list when vulcano have all the changes.
> >>
> >>Thanks again.
> >>
> >>
> >>Em Wednesday 21 June 2006 16:41, o Paolo Mantegazza escreveu:
> >>
> >>>Jorge Almeida wrote:
> >>>
> >>>>Hello to all.
> >>>>
> >>>>I'm trying to install RTAI magma (17-16-2006) in my new laptop ( dual 
> > 
> > core 
> > 
> >>>>Centrino) using kernel 2.6.16.20.
> >>>>
> >>>>I compile everything correctly but when i try to "insmod rtai_hal.ko" 
> > 
> > the 
> > 
> >>>>following error appears:
> >>>>
> >>>>Jun 21 15:40:40 main kernel: rtai_hal: falsely claims to have parameter 
> >>>>IsolCpusMask
> >>>>
> >>>>I've already read something about this parameter but until now i can't 
> >>
> >>insmod 
> >>
> >>>>it correctly. I know that i need to insmod the module with some kind of 
> >>
> >>mask 
> >>
> >>>>in that parameter, i've already tryed "insmod rtai_hal.ko 
> >>>>IsolCpusMask=00000000000000000000000000000010", but nothing appens, the 
> >>
> >>same 
> >>
> >>>>error appears.
> >>>>
> >>>>Anyone already had this problem?  Wath is the mask to use with the 
> >>>>IsolCpusMask parameter or where can i get information on that mask.
> >>>
> >>>You are on one of today threads. It seems that 2.16.20 already forbids 
> >>>using the old MODULE_PARM declaration. An old "obsolete" warning in 
> >>>2.6.xx I did not care of till it became compulsory. It seems it is now.
> >>>A patch has just been  posted  by "paul_c at tuxcnc.org" and the related 
> >>>changes will be in vulcano ASAP.
> >>>
> >>>Paolo
> >>>
> >>>
> >>>_______________________________________________
> >>>RTAI mailing list
> >>>RTAI at rtai.org
> >>>https://mail.rtai.org/cgi-bin/mailman/listinfo/rtai
> >>>DISCLAIMER: This message may contain confidential information or 
> > 
> > privileged 
> > 
> >>material and is intended only for the individual(s) named. If you are not 
a 
> >>named addressee and mistakenly received this message you should not copy 
or 
> >>otherwise disseminate it: please delete this e-mail from your system and 
> >>notify the sender immediately. E-mail transmissions are not guaranteed to 
be 
> >>secure or error-free as information could be intercepted, corrupted, lost, 
> >>destroyed, arrive late or incomplete or contain viruses. Therefore, the 
> >>sender does not accept liability for any errors or omissions in the 
contents 
> >>of this message that arise as a result of e-mail transmissions. Please 
> >>request a hard copy version if verification is required. Critical 
Software, 
> >>SA.
> >>
> >>-- 
> >>Jorge Almeida
> >>j-almeida at criticalsoftware.com
> >>DISCLAIMER: This message may contain confidential information or 
privileged 
> > 
> > material and is intended only for the individual(s) named. If you are not 
a 
> > named addressee and mistakenly received this message you should not copy 
or 
> > otherwise disseminate it: please delete this e-mail from your system and 
> > notify the sender immediately. E-mail transmissions are not guaranteed to 
be 
> > secure or error-free as information could be intercepted, corrupted, lost, 
> > destroyed, arrive late or incomplete or contain viruses. Therefore, the 
> > sender does not accept liability for any errors or omissions in the 
contents 
> > of this message that arise as a result of e-mail transmissions. Please 
> > request a hard copy version if verification is required. Critical 
Software, 
> > SA.
> > 
> >>_______________________________________________
> >>RTAI mailing list
> >>RTAI at rtai.org
> >>https://mail.rtai.org/cgi-bin/mailman/listinfo/rtai
> >>DISCLAIMER: This message may contain confidential information or 
privileged 
> > 
> > material and is intended only for the individual(s) named. If you are not 
a 
> > named addressee and mistakenly received this message you should not copy 
or 
> > otherwise disseminate it: please delete this e-mail from your system and 
> > notify the sender immediately. E-mail transmissions are not guaranteed to 
be 
> > secure or error-free as information could be intercepted, corrupted, lost, 
> > destroyed, arrive late or incomplete or contain viruses. Therefore, the 
> > sender does not accept liability for any errors or omissions in the 
contents 
> > of this message that arise as a result of e-mail transmissions. Please 
> > request a hard copy version if verification is required. Critical 
Software, 
> > SA.
> > 
> > 
> 
> 
> DISCLAIMER: This message may contain confidential information or privileged 
material and is intended only for the individual(s) named. If you are not a 
named addressee and mistakenly received this message you should not copy or 
otherwise disseminate it: please delete this e-mail from your system and 
notify the sender immediately. E-mail transmissions are not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete or contain viruses. Therefore, the 
sender does not accept liability for any errors or omissions in the contents 
of this message that arise as a result of e-mail transmissions. Please 
request a hard copy version if verification is required. Critical Software, 
SA.
> 

-- 
Jorge Almeida
j-almeida at criticalsoftware.com
DISCLAIMER: This message may contain confidential information or privileged material and is intended only for the individual(s) named. If you are not a named addressee and mistakenly received this message you should not copy or otherwise disseminate it: please delete this e-mail from your system and notify the sender immediately. E-mail transmissions are not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. Therefore, the sender does not accept liability for any errors or omissions in the contents of this message that arise as a result of e-mail transmissions. Please request a hard copy version if verification is required. Critical Software, SA.