From: Andrew Bates <abates@omeganetserv.com>
To: vk3bvp@qsl.net
Cc: linux-hams@vger.kernel.org
Subject: Re: ax25/baycom/kernel(?) problem.
Date: Mon, 24 Mar 2003 20:09:01 -0700 [thread overview]
Message-ID: <3E7FC84D.5AECD540@omeganetserv.com> (raw)
In-Reply-To: 200303251354.53711.vk3bvp@qsl.net
2.4.18 had severe problems.... I would get kernel panics all the time... running
fine for months on 2.4.19
Andrew KB0LND
Shane Deering wrote:
> On Tue, 25 Mar 2003 12:58, Bob Nielsen wrote:
> > What 2.4 kernel version were you running? I recall that some of the
> > early ones had problems, but have yet to see a kernel panic running
> > ax25 with 2.4.20 (stock Debian 2.4.20-686 kernel with mkiss driver as a
> > module).
> >
> > Bob, N7XY
>
> Up to 2.4.18. I use ax25 on this box with 2.4.19 without it crashing, but it
> doesn't get the work load and is only switched on when I'm around.
> Had a look at the 2.4.20 kernel. I couldn't get it to compile in the brief
> time I tried. So I took the easy/safe option and went back to using a 2.2
> kernel.
>
> --
> Shane Deering Sent using Kmail v1.4.3
> vk3bvp@qsl.net on Mandrake Linux, the Desktop OS
> vk3bvp@vk3bvp.#sev.vic.aus.oc MDK9.0 Up 6 hours and 29 minutes
> http://www.qsl.net/vk3bvp/ RH7.2 Up 23 days, 16 hours and 50 minutes
>
> -
> 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
next prev parent reply other threads:[~2003-03-25 3:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 9:22 ax25/baycom/kernel(?) problem Gunnar Widell (ESE)
2003-03-25 1:35 ` Shane Deering
2003-03-25 1:58 ` Bob Nielsen
2003-03-25 2:54 ` Shane Deering
2003-03-25 3:09 ` Andrew Bates [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-25 7:34 Gunnar Widell (ESE)
2003-03-25 14:12 ` M Taylor
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=3E7FC84D.5AECD540@omeganetserv.com \
--to=abates@omeganetserv.com \
--cc=linux-hams@vger.kernel.org \
--cc=vk3bvp@qsl.net \
/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