From: Ralf Baechle <ralf@linux-mips.org>
To: f6bvp <f6bvp@free.fr>
Cc: linux-hams@vger.kernel.org
Subject: Re: [PATCH 0/7] ROSE: Misc fixes
Date: Mon, 8 Aug 2011 15:06:14 +0100 [thread overview]
Message-ID: <20110808140614.GB2120@linux-mips.org> (raw)
In-Reply-To: <4E3FE760.1050909@free.fr>
On Mon, Aug 08, 2011 at 03:40:48PM +0200, f6bvp wrote:
> 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
This at least means there should be no regressions by my patch series and
it's getting time to send it upstream in a few days when I sorted out my
b0rked DSL line and new workstation. With these holes plugged finding
what's actually causing the use counters to go negative should also have
gotten a little easier.
Thanks,
Ralf
next prev parent reply other threads:[~2011-08-08 14:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 9:00 [PATCH 0/7] ROSE: Misc fixes Ralf Baechle
2011-07-20 0:21 ` [PATCH 1/7] NET: ROSE: Fix race in SIOCRSSL2CALL ioctl accessing userspace Ralf Baechle
2011-07-20 0:21 ` [PATCH 2/7] NET: ROSE: Factor our common code from functions Ralf Baechle
2011-07-20 0:37 ` [PATCH 3/7] NET: ROSE: Protect rose_callsign with a spinlock Ralf Baechle
2013-08-06 17:57 ` [PATCH] ax25tools mheard : don't display empty records f6bvp@free
2013-08-07 8:17 ` Thomas Osterried
2013-08-07 10:06 ` f6bvp@free
2013-08-09 8:10 ` Thomas Osterried
2011-07-20 8:11 ` [PATCH 4/7] NET: ROSE: Make neighbour->use atomic Ralf Baechle
2011-07-20 8:11 ` [PATCH 5/7] NET: ROSE: Make rose_neigh_no atomic Ralf Baechle
2011-07-20 18:09 ` [PATCH v2 " Ralf Baechle
2011-07-20 8:11 ` [PATCH 6/7] NET: ROSE: Move return statements hidden behind an if to their own line Ralf Baechle
2011-07-20 8:11 ` [PATCH 7/7] NET: ROSE: Fix formatting Ralf Baechle
2011-07-20 17:15 ` [PATCH 0/7] ROSE: Misc fixes Bernard, f6bvp
2011-07-20 17:59 ` Ralf Baechle DL5RB
2011-07-22 9:10 ` Bernard, f6bvp
2011-07-22 10:56 ` Ralf Baechle DL5RB
2011-07-22 16:12 ` f6bvp
2011-07-23 13:28 ` Ralf Baechle DL5RB
2011-07-29 22:32 ` f6bvp
2011-08-08 13:40 ` f6bvp
2011-08-08 14:06 ` Ralf Baechle [this message]
2011-08-08 15:33 ` f6bvp
2011-08-19 13:07 ` f6bvp
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=20110808140614.GB2120@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=f6bvp@free.fr \
--cc=linux-hams@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox