Re: [PATCH 0/7] ROSE: Misc fixes

[f6bvp <f6bvp@free.fr>]

Hello Ralf,

Since my last post my two ROSE/FPAC nodes have been running flawlessly 
with last ROSE patches for nearly 17 days.
Situation remains the same, i.e. from time to time use can still be 
negative.

Here is a /proc/net/rose/neigh dump from the machine running dual core 
CPU with SMP kernel :

/proc/net/rose_neigh
addr  callsign  dev  count use mode restart  t0  tf digipeaters
00005 F6BVP-5   ax2      1   0  DTE      no   0   0
00004 F8COJ-11  ax2      2  -1  DTE      yes   0   0
00003 F6BVP-11  ax1     11   0  DTE      no   0   0
00002 K4GBB-12  ax2      9   0  DCE     yes   0   0
00001 RSLOOP-0  ???      1   2  DCE     yes   0   0

For the present time "use" parameter has returned to 0 for F8COJ-11 node 
neighbor on the other system without
manual change.
Thus I guess some situations can reinitialize "use" counter.
I will then investigate if use can also become negative on this second 
system if I do not switch to UMP
mode at boot (removing maxcpus=1 boot option).

/proc/net/rose_neigh
addr  callsign  dev  count use mode restart  t0  tf digipeaters
00020 F6BVP-5   ax0      1   0  DTE      no   0   0
00019 F6BVP-7   ax0      2   0  DTE      no   0   0
00018 F6BVP-9   ax2      2   0  DTE      no   0   0
00017 F3KT-11   ax0      3   0  DCE     yes   0   0
00016 F8COJ-11  ax0      2   0  DCE     yes   0   0
00015 F6GGY-9   ax0      3   0  DTE      no   0   0
....
00002 TI2HAS-9  ax0      5   0  DTE      no   0   0
00001 RSLOOP-0  ???      1   0  DCE     yes   0   0


Bernard



Le 30/07/2011 00:32, f6bvp a écrit :
> Le 22/07/2011 12:56, Ralf Baechle DL5RB a écrit :
>> Most excellent! Take your time for testing - unfortunately we missed
>> the v3.0 train already but it would be great if we could backport these
>> fixes to -stable after some more positive testing.
>>
>> Is the system that was having these issues btw. running a preemptable 
>> kernel
>> or does it have multiple cores or hyperthreading?
>>
>> Thanks,
>>
>>    Ralf
> My two ROSE-FPAC nodes have been running for 8 days and 12 hours without
> disruption.
>
> Tonight I noticed that "use" parameter was negative (-1) while remote 
> node
> station F8COJ-11 was not connected (restart = "no" and tf counting).
>
> Later, F8COJ-11 node got connected again (restart = "yes") and "use" = 1.
> Then "use"  returned to 0 after a few minutes.
>
> This system is the one with SMP kernel and Voluntary Kernel Preemption 
> (Desktop).
>
> /proc/net/rose_neigh
>
> addr  callsign  dev  count use mode restart  t0  tf digipeaters
>
> 00005 F6BVP-5   ax2      1   0  DTE      no   0  99
>
> 00004 F8COJ-11  ax2      2  -1  DTE      no   0  87
>
> 00003 F6BVP-11  ax1     11   0  DTE      no   0   0
>
> 00002 K4GBB-12  ax2      9   0  DCE     yes   0   0
>
> 00001 RSLOOP-0  ???      1   2  DCE     yes   0   0
>
> /proc/net/rose_neigh
>
> addr  callsign  dev  count use mode restart  t0  tf digipeaters
>
> 00005 F6BVP-5   ax2      1   0  DTE      no   0   0
>
> 00004 F8COJ-11  ax2      2   1  DCE     yes   0   0
>
> 00003 F6BVP-11  ax1     11   0  DTE      no   0   0
>
> 00002 K4GBB-12  ax2      9   0  DCE     yes   0   0
>
> 00001 RSLOOP-0  ???      1   2  DCE     yes   0   0
>
>
>
> /proc/net/rose_neigh
>
> addr  callsign  dev  count use mode restart  t0  tf digipeaters
>
> 00005 F6BVP-5   ax2      1   0  DTE      no   0   0
>
> 00004 F8COJ-11  ax2      2   0  DCE     yes   0   0
>
> 00003 F6BVP-11  ax1     11   0  DTE      no   0   0
>
> 00002 K4GBB-12  ax2      9   0  DCE     yes   0   0
>
> 00001 RSLOOP-0  ???      1   2  DCE     yes   0   0
>
>
> At the same times, on my second Linux system (with maxcpus=1 boot 
> kernel parameter),
> use was 0 when not connected and it keeps displaying use=1 since ROSE 
> neighbour F8COJ has been connected again.
>
> However, both nodes are performing well and are able to route ROSE 
> frames to F8COJ-11.
>
> Bernard
>
>

--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html