ax25/baycom/kernel(?) problem.

[Gunnar Widell (ESE)]

A couple of weeks ago a described a DCD problem with my Baycom ser12 modem.
Got several answers (thanks) and I was able to solve the problem by adjusting the TCM3105 modem, the "2.6 volt something" on one of the pins.
I used the sethdlc -d command to debug on RX signals... and was able to get the DCD much more stable.

BUT!
Now I have problems with my modem not responding or send any ax25 packets after acouple of hours, up to a day, of operation.
I can see incoming calls (listen -cart) on the channel to my station, but no answer. If I try to make a call myself (call -r bcsf0 sl0zs) the modem does not send anything.

If I then try to unload the baycom driver and start it again all seams to be ok again.
Sometimes when I try to unload it, I get a KERNEL PANIC (something with interupt) and I need to power off my computer.

I have tried several things, thinking this is a kernel problem, tried to compile a 2.4.20 kernel, instead of the 2.4.18-3 I have been running.
I see the same thing... I have tried to load ax25 as module but same result.

My setup is a Pentium 500MHZ with 128 MB and 2.4.18-3 kernel. Rigth now 2.4.20 kernel with same problem.
Will try to compile a 2.4.10 kernel today and see if I get the same problem. Also running IPTables with NAT...

Baycom_ser_fdx 1200 bd modem. DX-spider. NO NODE or IP over radio yet...

Where to continue? No I need to go to a 2.2 kernel or could it still be a configuration problem?
What else can I print to see status of my ax25? The printouts below does not give ME any useful information, but maybe to someone else.
During this printouts I do not see any call attempts on my "listen -cart".

[sm3sgp@c213-100-160-63 sm3sgp]$ call -r bcsf0 sl0zs
GW4PTS AX.25 Connect v1.11
Trying...

[root@c213-100-160-63 linux-2.4.10]# cat /proc/net/ax25
c40ba5e0 bcsf0 SM3SGP-0 SL0ZS-0 1 0 0 0 3 10 0 4 0 3000 0 0 5 15 5 4 256 0 0 13394
c7f97760 bcsf0 SM3SGP-10 * 0 0 0 0 0 10 0 4 0 3000 0 0 0 15 5 4 256 0 0 937
c7f97b60 bcsf0 SM3SGP-6 * 0 0 0 0 0 10 0 4 0 3000 0 0 0 15 5 4 256 0 0 935
[root@c213-100-160-63 linux-2.4.10]#

netstat
Dest Source Device State Vr/Vs Send-Q Recv-Q
SL0ZS-0 SM3SGP-0 bcsf0 SABM SENT 000/000 0 0
* SM3SGP-10 bcsf0 LISTENING 000/000 0 0
* SM3SGP-6 bcsf0 LISTENING 000/000 0 0
[root@c213-100-160-63 linux-2.4.10]#

73 de Gus, SM3SGP

telnet sk3w.shacknet.nu 8000 DX-spider

-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

[Shane Deering]

On Mon, 24 Mar 2003 20:22, Gunnar Widell (ESE) wrote:

> Now I have problems with my modem not responding or send any ax25 packets
> after acouple of hours, up to a day, of operation. I can see incoming calls
> (listen -cart) on the channel to my station, but no answer. If I try to
> make a call myself (call -r bcsf0 sl0zs) the modem does not send anything.

My ax25 box would go for an hour or two up to a day or so and then kernel
panic when I used a 2.4 kernel. Once it went for 4 or 5 days.

>
> If I then try to unload the baycom driver and start it again all seams to
> be ok again. Sometimes when I try to unload it, I get a KERNEL PANIC
> (something with interupt) and I need to power off my computer.

Something like this-
<0>Kernel panic: Aiee, killing interupt handler!
In interrupt handler - not syncing

>
> I have tried several things, thinking this is a kernel problem, tried to
> compile a 2.4.20 kernel, instead of the 2.4.18-3 I have been running. I see
> the same thing... I have tried to load ax25 as module but same result.
>
> My setup is a Pentium 500MHZ with 128 MB and 2.4.18-3 kernel. Rigth now
> 2.4.20 kernel with same problem. Will try to compile a 2.4.10 kernel today
> and see if I get the same problem. Also running IPTables with NAT...
>
> Baycom_ser_fdx 1200 bd modem. DX-spider. NO NODE or IP over radio yet...

Node is easy enough to set up if you follow the howto.
I don't use a Baycom modem though.

>
> Where to continue? No I need to go to a 2.2 kernel or could it still be a
> configuration problem? What else can I print to see status of my ax25? The
> printouts below does not give ME any useful information, but maybe to
> someone else. During this printouts I do not see any call attempts on my
> "listen -cart".

I went back to using a 2.2 kernel after many frustrating attempts to use 2.4
kernels. That was about 23 days, 15 hours and 18 minutes ago :-)
Haven't rebooted since the first test boot after copying the new kernel across
to that box. It was worth the couple of hours spent to get a 2.2 kernel going
here.

--
Shane Deering Sent using Kmail v1.4.3
vk3...@qsl.net on Mandrake Linux, the Desktop OS
vk3bvp@vk3bvp.#sev.vic.aus.oc MDK9.0 Up 4 hours and 58 minutes
http://www.qsl.net/vk3bvp/ RH7.2 Up 23 days, 15 hours and 18 minutes

[Bob Nielsen]

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

--
Bob Nielsen, N7XY n7...@n7xy.net
Bainbridge Island, WA http://www.n7xy.net
IOTA NA-065, USI WA-028S

[Andrew Bates]

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
> vk3...@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

[M Taylor]

On Tue, Mar 25, 2003 at 08:34:59AM +0100, Gunnar Widell (ESE) wrote:
> > Something like this-
> > <0>Kernel panic: Aiee, killing interupt handler!
> > In interrupt handler - not syncing
>

> Yes, this is what I get.
> At the last stop last nigth it happened when I did:
>
> ifconfig bcsf0 down
>
> So, why are some 2.4.19 or 2.4.20 kernels working fine?
> Maybe I have too much junk compiled into it...

Unfortunately only your computer knows, and unless you can help
us by giving us more details, all we can do is guess.

Excerpt from the linux kernel mailing list FAQ
<http://www.tux.org/lkml/#s4-3> read
"# How do I post an Oops?"
"I think I found a bug, how do I report it?"
and "What information should go in a bug report?"
and in your linux kernel source:
Documentation/oops-tracing.txt
REPORTING-BUGS

You should also test your system, by running that linux kernel
withOUT AX.25 loaded for a period of time under normal use
conditions, so that you are confident that the problem is AX.25 related
and not a) bad hardware, b) other kernel/userland software problems.

I hope this helps
ve1mct