From: Kjell Jarl <K-Jarl@algonet.se>
To: Colin Harris <charis.g3orh@virgin.net>
Cc: Linux Hams <linux-hams@vger.kernel.org>
Subject: Re: Netrom disconnects
Date: Thu, 27 Mar 2003 18:25:56 +0100 [thread overview]
Message-ID: <3E833424.2080904@algonet.se> (raw)
In-Reply-To: 000501c2f453$9c3e80c0$14000a0a@p75
Since I switched to 2.4.19 under redhat 7.1, I have seen less, if any,
faults regarding this.
I have been posting similar results on earlier kernels, suspecting
netrom disconnects, maybe the problmes was solved in 2.4.19?
73
Kjell
Colin Harris wrote:
> Hi all,
> Our system here in s / west uk consists of two
> linuxnodes running DX Spider netrom linked on a 100 km path
> via two intermediate netrom nodes. My co-sysop at the other
> end reports frequent system crashes when a netrom disconnect
> occurs. This is not 100% certain but a "best guess" from
> observation and log checking. Has anyone experienced
> anything similar ?
>
> At this end I use kernel 2.2.12-20 and the other end uses
> something later ( perhaps 2.2.20 or thereabouts ). (I do not
> have any crashes due to netrom disconnects from my incoming
> netrom circuits here ).
>
> He uses Node-0.3.0 and allied ax25 stuff and I use
> node-0.3.1 plus updates but this problem has existed for
> some months before any of my updates.
> Any pointers or help/advice would be much
> appreciated ( BTW we both run Redhat versions ). Is there
> any way we can positively capture such an event conclusively
> ?
>
>
> - Regards Colin
>
>
> -
> 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
>
>
>
prev parent reply other threads:[~2003-03-27 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 11:24 Netrom disconnects Colin Harris
2003-03-27 17:25 ` Kjell Jarl [this message]
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=3E833424.2080904@algonet.se \
--to=k-jarl@algonet.se \
--cc=charis.g3orh@virgin.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.