All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Demetre Valaris" <sv1uy@sv1uy.ampr.org>
To: Jorge Matias <martin@andorinha.ist.utl.pt>
Cc: linux-hams <linux-hams@vger.kernel.org>
Subject: Re: Protocol error
Date: Mon, 18 Nov 2002 11:53:35 +0200	[thread overview]
Message-ID: <3DD8D4BF.27441.288F6F3@localhost> (raw)
In-Reply-To: <Pine.LNX.4.33.0211180032490.25179-100000@andorinha.ist.utl.pt>



On 18 Nov 2002 at 0:40, Jorge Matias wrote:

> On Sun, 17 Nov 2002, Demetre Valaris wrote:
> 
>   Hi Demetre,
> 
>   I have the same problem for a loooong time. I also have lots af messages like
> this one in my /var/log/messages:
> 
> Nov 18 00:34:36 hamradio kernel: NET: 8 messages suppressed.
> 
>   These messages arrive with a pace of 1 message every +-4 secs.
>   I suppose that the fact that I have all the traffic passing trough
> linuxnet makes this messages lots of times. (about one error for each
> frame received/sent).
> 
> 73,
> Jorge Matias
> CT2HBZ

Hi Jorge Matias,

Thanks for reply. I wonder if this causes any problems. At this end when I had 
a P133 AMD with 32MB RAm, sometimes my radio would key the TNC and TX nothing. 
Now I am not sure whether this is a TNC or computer problem. Eversince I 
upgraded my hardware to a faster PC (P433 Celeron with 128MB RAM) I have not 
observed this problem although the "protocol 0000 is buggy, dev ax0) is still 
there. I am not sure what caused the problem though, although it seems that 
the old slower PC with the 32MB RAM was at fault, but this problem was not 
persistent!!

73 de Demetre SV1UY
e-mail sv1uy@sv1uy.ampr.org
http://www.athnet.ampr.org/~sv1uy


  reply	other threads:[~2002-11-18  9:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-17 16:29 Protocol error Demetre Valaris
2002-11-18  0:40 ` Jorge Matias
2002-11-18  9:53   ` Demetre Valaris [this message]
2002-11-18 10:52     ` Sandor Dibuz
2002-11-18 11:31       ` Jorge Matias
2002-11-18 11:27     ` Jorge Matias
2002-11-18 11:58     ` jarmo

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=3DD8D4BF.27441.288F6F3@localhost \
    --to=sv1uy@sv1uy.ampr.org \
    --cc=linux-hams@vger.kernel.org \
    --cc=martin@andorinha.ist.utl.pt \
    /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.