From: M Taylor <mctylr@privacy.nb.ca>
To: bernard pidoux <pidoux@ccr.jussieu.fr>
Cc: linux-hams@vger.kernel.org
Subject: Re: Problem...
Date: Wed, 26 Mar 2003 00:46:33 +0000 [thread overview]
Message-ID: <20030326004633.A5531@pull.privacy.nb.ca> (raw)
In-Reply-To: <3E8086E6.3000709@ccr.jussieu.fr>; from pidoux@ccr.jussieu.fr on Tue, Mar 25, 2003 at 05:42:14PM +0100
On Tue, Mar 25, 2003 at 05:42:14PM +0100, bernard pidoux wrote:
>
> I was not able to achieve a normal functionning of Linux as soon as AX25
> was set up with mkiss connexions with any of 2.4.xx kernels. And I tried
> with different PCs.
> In 2.4 kernel, there are major problems with interruptions (and kernel
> panics after a few minutes or hours) that should be corrected in kernel
> version under development (actually around 2.5.65) leading to a possible
> return to correct functionning (I hope) in [2.6.x -ve1mct] kernel.
Bugs can only be fixed if people take the time to make a bug report.
There are developers here willing to help you if you need assistance
with finding the cause of the problem. (Myself included, though I am
not a kernel developer)
One thing I would really like to know is if certain protocols cause
problems, i.e. does plain AX.25 cause problem, or NetRom traffic,
what about AXIP traffic? Did you have a large route table (that is,
are your an AMPRnet gateway)? Any idea of the CPU load when the kernel
panic occured? Was there multiple connections/traffic on different or
same RF ports? Error messages in the syslog or messages file relating
to networking or amateur radio stuff?
The problems that exist in the 2.4 kernel also exist in the 2.2 kernel,
it is just that there are harder to trigger. They will become worst in
2.5/2.6 unless they are fixed, so the best time is now, while 2.5 is
still a development kernel.
Thank you,
ve1mct
prev parent reply other threads:[~2003-03-26 0:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 21:07 Problem Pontus Falk
2003-03-17 21:43 ` Problem pa3gcu
2003-03-17 22:09 ` Problem Pontus Falk
2003-03-17 23:12 ` Problem Shane Deering
2003-03-18 15:50 ` Problem pa3gcu
2003-03-25 6:41 ` Problem Henk Remijn
2003-03-25 16:42 ` Problem bernard pidoux
2003-03-25 17:25 ` Problem Jarmo
2003-03-27 12:01 ` Problem bernard pidoux
2003-03-25 20:45 ` Problem pa3gcu
2003-03-26 0:46 ` M Taylor [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=20030326004633.A5531@pull.privacy.nb.ca \
--to=mctylr@privacy.nb.ca \
--cc=linux-hams@vger.kernel.org \
--cc=pidoux@ccr.jussieu.fr \
/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