Thread: [RTnet-developers] ETH_P_ALL feature
Brought to you by:
bet-frogger,
kiszka
Menu
▾
▴
rtnet-developers
|
From: Jorge A. <j-a...@cr...> - 2006-09-28 16:41:29
|
Hello Jan I update today my rtnet svn to start a stress test in the ETH_P_ALL feature but there are some code changes. I've already find that you are changing the things for the secind list, the one for the ETH_P_ALL sockets. When do you think all the changes will be done? after that i will do some tests to see the robustness of the framework. I've already code it. Please let me know when the job is finnished. Thanks in advance. -- Jorge Almeida j-a...@cr... 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. |
|
From: Jan K. <jan...@we...> - 2006-09-28 17:14:42
Attachments:
signature.asc
|
Jorge Almeida wrote: > Hello Jan >=20 > I update today my rtnet svn to start a stress test in the ETH_P_ALL fea= ture but there are some code changes.=20 > I've already find that you are changing the things for the secind list,= the one for the ETH_P_ALL sockets. > When do you think all the changes will be done? > after that i will do some tests to see the robustness of the framework.= > I've already code it. >=20 > Please let me know when the job is finnished. >=20 ETH_P_ALL is already finished - except for replacing rtskb_clone with some rtskb-sharing mechanism /some day/. Go ahead with your tests! Jan |
|
From: Jorge A. <j-a...@cr...> - 2006-09-28 17:21:36
|
Did you do any test on that? I try to run some of the old tests and the receive using SOCKET RAW and ETH_P_ALL does not work. I will try to check waths going on. Thanks. Em Quinta, 28 de Setembro de 2006 18:14, o Jan Kiszka escreveu: > Jorge Almeida wrote: > > Hello Jan > > > > I update today my rtnet svn to start a stress test in the ETH_P_ALL feature but there are some code changes. > > I've already find that you are changing the things for the secind list, the one for the ETH_P_ALL sockets. > > When do you think all the changes will be done? > > after that i will do some tests to see the robustness of the framework. > > I've already code it. > > > > Please let me know when the job is finnished. > > > > ETH_P_ALL is already finished - except for replacing rtskb_clone with > some rtskb-sharing mechanism /some day/. > > Go ahead with your tests! > > Jan > > > > -- Jorge Almeida j-a...@cr... 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. |
|
From: Jan K. <jan...@we...> - 2006-09-28 17:24:45
Attachments:
signature.asc
|
Jorge Almeida wrote: > Did you do any test on that? Yes, see examples/xenomai/posix. > I try to run some of the old tests and the receive using SOCKET RAW and= ETH_P_ALL does not work. > I will try to check waths going on. Ok. Jan |
|
From: Jorge A. <j-a...@cr...> - 2006-09-28 18:14:49
|
Jan
With the changes in the stack managersomething happen to the trask that distribute the several messages.
It is not started when i load rtnet.
Me test machine has the following modules inserted:
Module Size Used by
rtpacket 5120 0
rtipv4 21664 0
rtcap 16384 0
rt_8139too 11904 6
rtnet 30092 4 rtpacket,rtipv4,rtcap,rt_8139too
rtai_rtdm 22176 4 rtpacket,rtipv4,rt_8139too,rtnet
rtai_shm 8832 0
rtai_sem 17664 2 rtnet,rtai_rtdm
rtai_lxrt 74904 7 rtipv4,rtcap,rt_8139too,rtnet,rtai_rtdm,rtai_shm,rtai_sem
rtai_hal 69840 8 rtcap,rt_8139too,rtnet,rtai_rtdm,rtai_shm,rtai_sem,rtai_lxrt
sis900 19840 0
and the /proc/rtai/names file has the following:
RTAI LXRT Information.
MAX_SLOTS = 150
Linux_Owner Parent PID
Slot Name ID Type RT_Handle Pointer Tsk_PID MEM_Sz USG Cnt
-------------------------------------------------------------------------------
190 RTGLBF 0x9ac6d9e5 SHMEM 0xe09f1000 0x00000000 0 2097152 1
tester1:/home/nfs_share/rtnet #
it should have several semaphores and at least a task for rtnet.
When i run the example that i send to you several days ago, just the sending part the file has
tester1:/home/nfs_share/rtnet # cat /proc/rtai/names
RTAI LXRT Information.
MAX_SLOTS = 150
Linux_Owner Parent PID
Slot Name ID Type RT_Handle Pointer Tsk_PID MEM_Sz USG Cnt
-------------------------------------------------------------------------------
142 TASK1 0x042da6bf TASK 0xe09f2220 0x00000000 0 20179 1
190 RTGLBF 0x9ac6d9e5 SHMEM 0xe09f1000 0x00000000 0 2097152 1
tester1:/home/nfs_share/rtnet #
only my task appears.
The receive part of the example blocks, and never return.
I've already use some printk and the task manager code never run.
Maybe is something related with the RTAI task. I'm using RTAI-3.4 stable release.
Any clues????
Jorge
Em Quinta, 28 de Setembro de 2006 18:24, o Jan Kiszka escreveu:
> Jorge Almeida wrote:
> > Did you do any test on that?
>
> Yes, see examples/xenomai/posix.
>
> > I try to run some of the old tests and the receive using SOCKET RAW and ETH_P_ALL does not work.
> > I will try to check waths going on.
>
> Ok.
>
> Jan
>
>
--
Jorge Almeida
j-a...@cr...
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.
|
|
From: Jan K. <jan...@we...> - 2006-09-28 18:25:21
Attachments:
signature.asc
|
Jorge Almeida wrote:
> Jan
>=20
> With the changes in the stack managersomething happen to the trask that=
distribute the several messages.
> It is not started when i load rtnet.
>=20
> Me test machine has the following modules inserted:
> Module Size Used by
> rtpacket 5120 0
> rtipv4 21664 0
> rtcap 16384 0
> rt_8139too 11904 6
> rtnet 30092 4 rtpacket,rtipv4,rtcap,rt_8139too
> rtai_rtdm 22176 4 rtpacket,rtipv4,rt_8139too,rtnet
> rtai_shm 8832 0
> rtai_sem 17664 2 rtnet,rtai_rtdm
> rtai_lxrt 74904 7 rtipv4,rtcap,rt_8139too,rtnet,rtai_rtdm=
,rtai_shm,rtai_sem
> rtai_hal 69840 8 rtcap,rt_8139too,rtnet,rtai_rtdm,rtai_s=
hm,rtai_sem,rtai_lxrt
> sis900 19840 0
>=20
> and the /proc/rtai/names file has the following:
>=20
> RTAI LXRT Information.
>=20
> MAX_SLOTS =3D 150
>=20
> Linux_Owner Parent PID=
> Slot Name ID Type RT_Handle Pointer Tsk_PID MEM_Sz =
USG Cnt
> -----------------------------------------------------------------------=
--------
> 190 RTGLBF 0x9ac6d9e5 SHMEM 0xe09f1000 0x00000000 0 2097152=
1
> tester1:/home/nfs_share/rtnet # =20
>=20
> it should have several semaphores and at least a task for rtnet.
> When i run the example that i send to you several days ago, just the se=
nding part the file has
> tester1:/home/nfs_share/rtnet # cat /proc/rtai/names
>=20
> RTAI LXRT Information.
>=20
> MAX_SLOTS =3D 150
>=20
> Linux_Owner Parent PID=
> Slot Name ID Type RT_Handle Pointer Tsk_PID MEM_Sz =
USG Cnt
> -----------------------------------------------------------------------=
--------
> 142 TASK1 0x042da6bf TASK 0xe09f2220 0x00000000 0 20179=
1
> 190 RTGLBF 0x9ac6d9e5 SHMEM 0xe09f1000 0x00000000 0 2097152=
1
> tester1:/home/nfs_share/rtnet # =20
>=20
> only my task appears.=20
> The receive part of the example blocks, and never return.
> I've already use some printk and the task manager code never run.
>=20
> Maybe is something related with the RTAI task. I'm using RTAI-3.4 stabl=
e release.
>=20
> Any clues????
Nope, specifically as I haven't changed anything related. I would
suggest to either vary the versions (older RTnet SVN that used to work,
older RTAI) or step into the rtdm_task creation of the stack manager.
Actually, that service should return some error code if anything went wro=
ng.
Jan
|
|
From: Jorge A. <j-a...@cr...> - 2006-09-28 18:24:34
|
Nothing appears in the messages file. Tomorrow i will debug the problem and say something. Jorge Em Quinta, 28 de Setembro de 2006 19:20, o Jan Kiszka escreveu: > Jorge Almeida wrote: > > Jan > > > > With the changes in the stack managersomething happen to the trask that distribute the several messages. > > It is not started when i load rtnet. > > > > Me test machine has the following modules inserted: > > Module Size Used by > > rtpacket 5120 0 > > rtipv4 21664 0 > > rtcap 16384 0 > > rt_8139too 11904 6 > > rtnet 30092 4 rtpacket,rtipv4,rtcap,rt_8139too > > rtai_rtdm 22176 4 rtpacket,rtipv4,rt_8139too,rtnet > > rtai_shm 8832 0 > > rtai_sem 17664 2 rtnet,rtai_rtdm > > rtai_lxrt 74904 7 rtipv4,rtcap,rt_8139too,rtnet,rtai_rtdm,rtai_shm,rtai_sem > > rtai_hal 69840 8 rtcap,rt_8139too,rtnet,rtai_rtdm,rtai_shm,rtai_sem,rtai_lxrt > > sis900 19840 0 > > > > and the /proc/rtai/names file has the following: > > > > RTAI LXRT Information. > > > > MAX_SLOTS = 150 > > > > Linux_Owner Parent PID > > Slot Name ID Type RT_Handle Pointer Tsk_PID MEM_Sz USG Cnt > > ------------------------------------------------------------------------------- > > 190 RTGLBF 0x9ac6d9e5 SHMEM 0xe09f1000 0x00000000 0 2097152 1 > > tester1:/home/nfs_share/rtnet # > > > > it should have several semaphores and at least a task for rtnet. > > When i run the example that i send to you several days ago, just the sending part the file has > > tester1:/home/nfs_share/rtnet # cat /proc/rtai/names > > > > RTAI LXRT Information. > > > > MAX_SLOTS = 150 > > > > Linux_Owner Parent PID > > Slot Name ID Type RT_Handle Pointer Tsk_PID MEM_Sz USG Cnt > > ------------------------------------------------------------------------------- > > 142 TASK1 0x042da6bf TASK 0xe09f2220 0x00000000 0 20179 1 > > 190 RTGLBF 0x9ac6d9e5 SHMEM 0xe09f1000 0x00000000 0 2097152 1 > > tester1:/home/nfs_share/rtnet # > > > > only my task appears. > > The receive part of the example blocks, and never return. > > I've already use some printk and the task manager code never run. > > > > Maybe is something related with the RTAI task. I'm using RTAI-3.4 stable release. > > > > Any clues???? > > Nope, specifically as I haven't changed anything related. I would > suggest to either vary the versions (older RTnet SVN that used to work, > older RTAI) or step into the rtdm_task creation of the stack manager. > Actually, that service should return some error code if anything went wrong. > > Jan > > -- Jorge Almeida j-a...@cr... 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. |
|
From: Jorge A. <j-a...@cr...> - 2006-09-29 12:26:15
|
I putthe following rtdm_printk functions in this function and the
rtdm_printk("\tEvent occured\n");
never is doner when a send messages to the receiveing network.
I don't know why.
static void rt_stack_mgr_task(void *arg)
{
rtdm_event_t *mgr_event = &((struct rtnet_mgr *)arg)->event;
struct rtskb *rtskb;
rtdm_printk("\tArrive to the rt_stack_mgr_task function\n");
while (rtdm_event_wait(mgr_event) == 0) {
/* we are the only reader => no locking required */
rtdm_printk("\tEvent occured\n");
while ((rtskb = __rtskb_fifo_remove(&rx.fifo)))
{
rtdm_printk("\trtskb removed from fifo\n");
rt_stack_deliver(rtskb);
rtdm_printk("\trtskb delivered\n");
}
}
rtdm_printk("\tGoing out from rt_stack_mgr_task function\n");
}
The first
rtdm_printk("\tArrive to the rt_stack_mgr_task function\n");
and the last
rtdm_printk("\tGoing out from rt_stack_mgr_task function\n");
are done in the starting and at the end of rtnet.
Any clues??
Jorge
Em Quinta, 28 de Setembro de 2006 19:31, o Jorge Almeida escreveu:
>
> Nothing appears in the messages file.
>
> Tomorrow i will debug the problem and say something.
>
> Jorge
>
> Em Quinta, 28 de Setembro de 2006 19:20, o Jan Kiszka escreveu:
> > Jorge Almeida wrote:
> > > Jan
> > >
> > > With the changes in the stack managersomething happen to the trask that distribute the several messages.
> > > It is not started when i load rtnet.
> > >
> > > Me test machine has the following modules inserted:
> > > Module Size Used by
> > > rtpacket 5120 0
> > > rtipv4 21664 0
> > > rtcap 16384 0
> > > rt_8139too 11904 6
> > > rtnet 30092 4 rtpacket,rtipv4,rtcap,rt_8139too
> > > rtai_rtdm 22176 4 rtpacket,rtipv4,rt_8139too,rtnet
> > > rtai_shm 8832 0
> > > rtai_sem 17664 2 rtnet,rtai_rtdm
> > > rtai_lxrt 74904 7 rtipv4,rtcap,rt_8139too,rtnet,rtai_rtdm,rtai_shm,rtai_sem
> > > rtai_hal 69840 8 rtcap,rt_8139too,rtnet,rtai_rtdm,rtai_shm,rtai_sem,rtai_lxrt
> > > sis900 19840 0
> > >
> > > and the /proc/rtai/names file has the following:
> > >
> > > RTAI LXRT Information.
> > >
> > > MAX_SLOTS = 150
> > >
> > > Linux_Owner Parent PID
> > > Slot Name ID Type RT_Handle Pointer Tsk_PID MEM_Sz USG Cnt
> > > -------------------------------------------------------------------------------
> > > 190 RTGLBF 0x9ac6d9e5 SHMEM 0xe09f1000 0x00000000 0 2097152 1
> > > tester1:/home/nfs_share/rtnet #
> > >
> > > it should have several semaphores and at least a task for rtnet.
> > > When i run the example that i send to you several days ago, just the sending part the file has
> > > tester1:/home/nfs_share/rtnet # cat /proc/rtai/names
> > >
> > > RTAI LXRT Information.
> > >
> > > MAX_SLOTS = 150
> > >
> > > Linux_Owner Parent PID
> > > Slot Name ID Type RT_Handle Pointer Tsk_PID MEM_Sz USG Cnt
> > > -------------------------------------------------------------------------------
> > > 142 TASK1 0x042da6bf TASK 0xe09f2220 0x00000000 0 20179 1
> > > 190 RTGLBF 0x9ac6d9e5 SHMEM 0xe09f1000 0x00000000 0 2097152 1
> > > tester1:/home/nfs_share/rtnet #
> > >
> > > only my task appears.
> > > The receive part of the example blocks, and never return.
> > > I've already use some printk and the task manager code never run.
> > >
> > > Maybe is something related with the RTAI task. I'm using RTAI-3.4 stable release.
> > >
> > > Any clues????
> >
> > Nope, specifically as I haven't changed anything related. I would
> > suggest to either vary the versions (older RTnet SVN that used to work,
> > older RTAI) or step into the rtdm_task creation of the stack manager.
> > Actually, that service should return some error code if anything went wrong.
> >
> > Jan
> >
> >
>
> --
> Jorge Almeida
> j-a...@cr...
> 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.
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> RTnet-developers mailing list
> RTn...@li...
> https://lists.sourceforge.net/lists/listinfo/rtnet-developers
>
--
Jorge Almeida
j-a...@cr...
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.
|
|
From: Jan K. <jan...@we...> - 2006-09-29 15:20:41
Attachments:
signature.asc
|
Jorge Almeida wrote:
> I putthe following rtdm_printk functions in this function and the=20
>=20
> rtdm_printk("\tEvent occured\n");
>=20
> never is doner when a send messages to the receiveing network.
Is rtdm_event_signal called appropriately?
>=20
> I don't know why.
>=20
> static void rt_stack_mgr_task(void *arg)
> {
> rtdm_event_t *mgr_event =3D &((struct rtnet_mgr *)arg)->=
event;
> struct rtskb *rtskb;
>=20
> rtdm_printk("\tArrive to the rt_stack_mgr_task function\n");
> while (rtdm_event_wait(mgr_event) =3D=3D 0) {
> /* we are the only reader =3D> no locking required */
> rtdm_printk("\tEvent occured\n");
> while ((rtskb =3D __rtskb_fifo_remove(&rx.fifo)))
> {
> rtdm_printk("\trtskb removed from fifo\n");
> rt_stack_deliver(rtskb);
> rtdm_printk("\trtskb delivered\n");
> }
> }
> rtdm_printk("\tGoing out from rt_stack_mgr_task function\n");
> }
>=20
> The first=20
>=20
> rtdm_printk("\tArrive to the rt_stack_mgr_task function\n");
>=20
> and the last
> rtdm_printk("\tGoing out from rt_stack_mgr_task function\n");
>=20
> are done in the starting and at the end of rtnet.
=2E..but there is no entry in the RTAI task list under /proc like it used=
to?
>=20
> Any clues??
Back to my other suggestion: try older versions of RTnet SVN and RTAI
until you find a working combination. Then try to narrow down the change
that causes this.
Jan
|
|
From: Jan K. <jan...@we...> - 2006-10-09 13:00:09
Attachments:
signature.asc
|
Jan Kiszka wrote:
> Jorge Almeida wrote:
>> I putthe following rtdm_printk functions in this function and the=20
>>
>> rtdm_printk("\tEvent occured\n");
>>
>> never is doner when a send messages to the receiveing network.
>=20
> Is rtdm_event_signal called appropriately?
>=20
>> I don't know why.
>>
>> static void rt_stack_mgr_task(void *arg)
>> {
>> rtdm_event_t *mgr_event =3D &((struct rtnet_mgr *)arg)-=
>event;
>> struct rtskb *rtskb;
>>
>> rtdm_printk("\tArrive to the rt_stack_mgr_task function\n");
>> while (rtdm_event_wait(mgr_event) =3D=3D 0) {
>> /* we are the only reader =3D> no locking required */
>> rtdm_printk("\tEvent occured\n");
>> while ((rtskb =3D __rtskb_fifo_remove(&rx.fifo)))
>> {
>> rtdm_printk("\trtskb removed from fifo\n");
>> rt_stack_deliver(rtskb);
>> rtdm_printk("\trtskb delivered\n");
>> }
>> }
>> rtdm_printk("\tGoing out from rt_stack_mgr_task function\n");
>> }
>>
>> The first=20
>>
>> rtdm_printk("\tArrive to the rt_stack_mgr_task function\n");
>>
>> and the last
>> rtdm_printk("\tGoing out from rt_stack_mgr_task function\n");
>>
>> are done in the starting and at the end of rtnet.
>=20
> ...but there is no entry in the RTAI task list under /proc like it used=
to?
>=20
>> Any clues??
>=20
> Back to my other suggestion: try older versions of RTnet SVN and RTAI
> until you find a working combination. Then try to narrow down the chang=
e
> that causes this.
>=20
Any news on this? I would like to nail down remaining issues in order to
roll out a new release within, say, a week.
Jan
|
|
From: Jorge A. <j-a...@cr...> - 2006-10-12 13:37:35
|
Hello Jan.
Regarding the problem we discuss some time ago, it still remains.
I have until now found the origin of the problem.
Theres no RX interruption handled in any of the boards that should receive the messages.
Thats why the stack_mgr_task never wakes up from the event.
I'm using the rt_8139too driver that cames with rtnet.
I've done some roll back in rtnet and RTAI and nothing:
Rtnet until version 1069
RTAI magma until RTAI-3.4-test1
Maybe can be anything related with RTDM and the interrupt handling.
Jorge
Em Segunda, 9 de Outubro de 2006 13:59, o Jan Kiszka escreveu:
> Jan Kiszka wrote:
> > Jorge Almeida wrote:
> >> I putthe following rtdm_printk functions in this function and the
> >>
> >> rtdm_printk("\tEvent occured\n");
> >>
> >> never is doner when a send messages to the receiveing network.
> >
> > Is rtdm_event_signal called appropriately?
> >
> >> I don't know why.
> >>
> >> static void rt_stack_mgr_task(void *arg)
> >> {
> >> rtdm_event_t *mgr_event = &((struct rtnet_mgr *)arg)->event;
> >> struct rtskb *rtskb;
> >>
> >> rtdm_printk("\tArrive to the rt_stack_mgr_task function\n");
> >> while (rtdm_event_wait(mgr_event) == 0) {
> >> /* we are the only reader => no locking required */
> >> rtdm_printk("\tEvent occured\n");
> >> while ((rtskb = __rtskb_fifo_remove(&rx.fifo)))
> >> {
> >> rtdm_printk("\trtskb removed from fifo\n");
> >> rt_stack_deliver(rtskb);
> >> rtdm_printk("\trtskb delivered\n");
> >> }
> >> }
> >> rtdm_printk("\tGoing out from rt_stack_mgr_task function\n");
> >> }
> >>
> >> The first
> >>
> >> rtdm_printk("\tArrive to the rt_stack_mgr_task function\n");
> >>
> >> and the last
> >> rtdm_printk("\tGoing out from rt_stack_mgr_task function\n");
> >>
> >> are done in the starting and at the end of rtnet.
> >
> > ...but there is no entry in the RTAI task list under /proc like it used to?
> >
> >> Any clues??
> >
> > Back to my other suggestion: try older versions of RTnet SVN and RTAI
> > until you find a working combination. Then try to narrow down the change
> > that causes this.
> >
>
> Any news on this? I would like to nail down remaining issues in order to
> roll out a new release within, say, a week.
>
> Jan
>
>
--
Jorge Almeida
j-a...@cr...
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.
|
|
From: Jan K. <jan...@we...> - 2006-10-12 13:52:14
Attachments:
signature.asc
|
Jorge Almeida wrote: > Hello Jan. >=20 > Regarding the problem we discuss some time ago, it still remains. >=20 > I have until now found the origin of the problem. >=20 > Theres no RX interruption handled in any of the boards that should rece= ive the messages. >=20 > Thats why the stack_mgr_task never wakes up from the event. >=20 > I'm using the rt_8139too driver that cames with rtnet. >=20 > I've done some roll back in rtnet and RTAI and nothing: > Rtnet until version 1069 > RTAI magma until RTAI-3.4-test1 >=20 > Maybe can be anything related with RTDM and the interrupt handling. Hmm, there were three significant checkins to that driver, see http://svn.sourceforge.net/viewvc/rtnet/trunk/rtnet/drivers/rt_8139too.c?= view=3Dlog Likely 1013 is worth a try, then 1055 and 1056. Jan |
Thanks for helping keep SourceForge clean.
X