From: Roger Harris (tjcvt.sqllnbibu@kase.fi)
Date: Tue Oct 02 2001 - 01:50:09 EEST
Hi Tomi
Thanks for the reply. I tried reading /proc/net/nr_neigh and it looked OK
and didn't cause an error.
Anyway, the problem has now been solved, simply by rebooting without
reading my routes config file (the file which my system updates once an
hour with nodesave). This gave me an empty routes table and the node worked
OK. I then read in just the routes (not the nodes) from my saved config
file, and let it re-learn the nodes. The node is now functioning perfectly.
I've kept a copy of my old routes config file. It must have an entry in
which upsets the node. At first sight, it looks OK, but I'll take a closer
look.
Thanks again
Roger
At 15:27 01/10/01 +0300, Tomi Manninen wrote:
>On Sun, 30 Sep 2001, Roger Harris wrote:
>
> > After several months of trouble-free operation, my Linux node has suddenly
> > started behaving rather strangely. This problem started after there was a
> > couple of power failures (caused by the Electricity Board). After this, the
> > PC appeared to reboot OK and everything appears to work except the "routes"
> > command in the node. Can anyone suggest which files may have been
> > corrupted? I have checked the "node" binary and several others against
> > known working copies and they seem to be OK.
> >
> > Only the "R" (routes) command is affected. Other node commands such as "S",
> > "U", "N" work OK. If users connect to the node (via Netrom, AX25 or Telnet)
> > and issue the "R" command, they are immediately disconnected and the
> > following kernel errors appear in /var/log/messages.
>
>The routes command reads /proc/net/nr_neigh to get the info from kernel.
>You should be able to verify that this indeed causes the problem by
>reading it with eg. cat: cat /proc/net/nr_neigh
>
>This should cause a segmentation fault and the kernel oops as well.
>
> > Note the reference to the 3c503 module. I'm not sure of the significance of
> > this message, but the 3c503 ethernet card appears to be working OK.
> >
> > I am using SuSe Linux 7.0 with Kernel 2.2.16 and LinuxNode v0.3.0.
> >
> > Can anyone offer any clues or advice, other than rebuilding the system?
>
>This is really strange. I can't think of anything else but recompiling and
>installing the kernel + modules. Maybe one of the modules or the kernel
>binary itself is corrupted?
>
>--
>Tomi Manninen Internet: terhi.victor@logonet.com
>OH2BNS AX.25: gfejg@cccredit.hu
>KP20ME04 Amprnet: terhi.victor@logonet.com
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-hams" in
>the body of a message to mmdsd.fvyqzjwagh@herter.de
>More majordomo info at http://vger.kernel.org/majordomo-info.html
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to terhi.victor@logonet.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
This archive was generated by hypermail 2b30 : Tue Oct 02 2001 - 01:47:55 EEST