2.6.14-r4 crashing

2.6.14-r4 crashing

[aa6qn]

I could use some guidence here to stabelize the system. It crashes
serveral times a day and it looks like a IRQ syncing problem. This only
happens when I load ax25 and its associated modules. I am not sure if I
missed something in the kernel configuration so I am grasping at straws at
the moment.
The system loads just fine and does what its supposed to do for the most
part. I do run jnos attached via slattach.

What would be a good place to start in correcting this problem?

Thank you in advance, JohnF

Re: 2.6.14-r4 crashing

[jarmo]

aa6qn@aa6qn.sytes.net wrote (lähetysaika lauantai 22 lokakuu 2005 04:18):
> I could use some guidence here to stabelize the system. It crashes
> serveral times a day and it looks like a IRQ syncing problem. This only
> happens when I load ax25 and its associated modules. I am not sure if I
> missed something in the kernel configuration so I am grasping at straws at
> the moment.

Hi Ralf
Remember my similar problems with earlier kernels?
I haven't tested 14 series yet in RBF. Waiting stable.

Jarmo

-- 
Linux is the answer.
What was your question?
(Brian Lane)
-
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

Re: 2.6.14-r4 crashing

[Ralf Baechle DL5RB]

On Sat, Oct 22, 2005 at 11:52:22AM +0300, jarmo wrote:

> aa6qn@aa6qn.sytes.net wrote (lähetysaika lauantai 22 lokakuu 2005 04:18):
> > I could use some guidence here to stabelize the system. It crashes
> > serveral times a day and it looks like a IRQ syncing problem. This only
> > happens when I load ax25 and its associated modules. I am not sure if I
> > missed something in the kernel configuration so I am grasping at straws at
> > the moment.
> 
> Hi Ralf
> Remember my similar problems with earlier kernels?
> I haven't tested 14 series yet in RBF. Waiting stable.

I believe your problems are actually related to NET/ROM.  Pure AX.25,
IP-over-AX.25, mkiss and 6pack running the usual Linux AX.25 apps and
Wampes has turned out to be reasonably solid:

[ralf@dea ~]$ ssh db0fhn.efi.fh-nuernberg.de "uptime; uname -a"
 14:50:55 up 25 days, 23:12, 11 users,  load average: 0.40, 0.31, 0.35
Linux db0fhn 2.6.13 #8 Mon Sep 26 15:04:42 CEST 2005 i686 GNU/Linux
[ralf@dea ~]$

This is running a 2.6.13 kernel including all the patches which I also
put into the 2.6.14-rc.

  Ralf
-
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

Re: 2.6.14-r4 crashing

[Ralf Baechle DL5RB]

On Fri, Oct 21, 2005 at 06:18:07PM -0700, aa6qn@aa6qn.sytes.net wrote:

> I could use some guidence here to stabelize the system. It crashes
> serveral times a day and it looks like a IRQ syncing problem. This only
> happens when I load ax25 and its associated modules. I am not sure if I
> missed something in the kernel configuration so I am grasping at straws at
> the moment.

Care to add any details?  "Looks like" isn't a useful bugreport, sorry ...
AX.25 doesn't run any code in interrupts btw. - except maybe a bunch of
the more esotheric devices, so I'm interested in your setup.

  Ralf

Re: 2.6.14-r4 crashing

[aa6qn]

My apologies for the the short discription on my errors.

I did a "divide and conquer" and cut out the jnos application that was
linked via slip attach and things seem to be working. I replaced the jnos
with xfbb for my pbbs and it seems to be doing the job.

My setup is fairly simple. Solar powered server running Gentoo 2.6 profile
with uDev. AX25 setup is a single Kantronics Data Engine running in kiss
mode with one port on 2m at 1200bd and the other on 70cm at 9k6. ax25ipd
link north via iproute2 ipip (ip tunnel) over a dynamic dsl connection.
Running Conversd and DX-Spider of the same box as well. Thats it in a
nutshell aside from my other network and security applications.

I had a feeling something was astray with the jnos application as I could
not route to any other destination other than my local interfaces.

I do remember from some time ago a facility to collect dump data for
forensics but can not remember what that was. In any case, it seems to be
holding so far.

I did just emerged the latest uDev update and that may have helped some as
well. I will keep an eye on the system and keep my fingers crossed as
well.
Thank you for your assistance.
JohnF

Re: 2.6.14-r4 crashing

[aa6qn]

Ok, this time I captured the dump screen. It did stay up longer..

At the kernel panic screen:
-------------
call trace
_spin_lock_irqsave
lock_timer_
del timer
ax25_destroy_socket
ax25_heartbeat_expiry
run_timer_softirq
__do_softirq
do_softirq
=====================
irq_exit
apic_timer
mwait_idle
mwait_idle
cpu_idle
start_kernel

kernel panic -not syncing: fatal exception in interupt

------------------------
Thats it.

I am also having a small bit of growing pains with iproute2 ipip
configuration and routing. I am getting a tunnel up with the remote
destination using:
>ip tunnel add (callsign of remote end) mode ipip remote (far end tunnel
ip) local (my secondary 44 address for eth0) dev tunl0

Some things I have set and tried:
-I do not have to add the far end 44 address routing.
-I have tried both tunl0 and eth0 for connection dev's
-For my tunl0, I configured it with a local 44 domain IP address
-I have attached ax25ipd via the ax5 device and it does allow me to
exchange netrom data with the far end using the far ends 44 domain IP.
-I am not doing IPv6 just IPv4

I picked up pointer from this site:
http://www.deepspace6.net/docs/iproute2tunnel-en.html

Hope I am doing it right!

JohnF

Re: 2.6.14-r4 crashing

[Ralf Baechle DL5RB]

On Sun, Oct 23, 2005 at 04:49:04AM -0700, aa6qn@aa6qn.sytes.net wrote:

> Ok, this time I captured the dump screen. It did stay up longer..

It may not be the perfect method but screenshots with digital cameras
have provent to be very useful in the past where crash messages don't
get caught in syslog.

Or serial console, clearly the best thing since sliced brear ;-)

> At the kernel panic screen:
> -------------
> call trace
> _spin_lock_irqsave
> lock_timer_
> del timer
> ax25_destroy_socket
> ax25_heartbeat_expiry
> run_timer_softirq
> __do_softirq
> do_softirq

Delayed socket destruction code.  That's giving me some idea.  I tried to
cleanup that code earlier in the hope to come up with something that can
obviously shown to be correct but it turned out to be a non-trivial
project.

> Some things I have set and tried:
> -I do not have to add the far end 44 address routing.

Linux will automatically establish a route for every interface, that's
why you don't have to.

> -I have tried both tunl0 and eth0 for connection dev's
> -For my tunl0, I configured it with a local 44 domain IP address
> -I have attached ax25ipd via the ax5 device and it does allow me to
> exchange netrom data with the far end using the far ends 44 domain IP.

NET/ROM.  I guess that is the common factor between you and OH1MRR who
is experiencing a problem that's looking vaguely similar.  Time to turn
NET/ROM upside down; the code is certainly incorrect on any system
running a SMP or preemptible kernel.

> -I am not doing IPv6 just IPv4

That just oldfashioned but not wrong :-)

> I picked up pointer from this site:
> http://www.deepspace6.net/docs/iproute2tunnel-en.html
> 
> Hope I am doing it right!

Missconfiguration is not an acceptable cause for a crash, so yes.

Btw, you may want to switch to GRE tunneling; GRE is a superior tunneling
technology compared to IP-over-IP.

73 de DL5RB op Ralf

--
Loc. JN47BS / CQ 14 / ITU 28 / DOK A21

Re: 2.6.14-r4 crashing

[aa6qn]

 I changed the freq selection per earlier email to 1000hz and that seemed
to help (at least from a tnc timing perspective). The system did have a
kernel panic after a couple of netrom non-connections.

I really believe you hit the nail on the head that most of my problems
present and past where netrom based. When I loaded ax25 excluding the
netrom application the platform did very well.( I ran netrom from jnos
vice the ax25 utils).

Whenever I load the ax25 netrom it seems that when I try a netrom connect
and it fails a kernel panic results soon there after.

So, for the moment I have removed the ax25 utils and am just running Jnos
2.0d via a slip link ( I can not get the tun device working with uDev).
The system is quite solid.

I am curious where the "ip route add (network) via (gateway) dev tunl0
static onlink" command loads but does not route anymore whereas "ip tunnel
add (name) remote (remote gw) local (local ip) dev tunl0" does work. Did
something change with IPROUTE2 ? The ip route add worked for me before and
allowed ax25ipd links.

I would be more than happy to try any other ideas/patches that may relieve
the ax25 kernel challanges.

very best wishes, JohnF

Re: 2.6.14-r4 crashing

[John Ronan]

Hi,

I had unending difficulties when trying netrom and kernel 2.6... in  
the end I gave up and am running 2.4 now for stability.

Linux version 2.4.29 (root@ei3rcw) (gcc version 3.3.5 (Debian  
1:3.3.5-8)) #5 Fri Apr 15 13:37:45 IST 2005

to be exact.

Regards
John

On 25 Oct 2005, at 17:09, aa6qn@aa6qn.sytes.net wrote:

>  I changed the freq selection per earlier email to 1000hz and that  
> seemed
> to help (at least from a tnc timing perspective). The system did  
> have a
> kernel panic after a couple of netrom non-connections.
>
> I really believe you hit the nail on the head that most of my problems
> present and past where netrom based. When I loaded ax25 excluding the
> netrom application the platform did very well.( I ran netrom from jnos
> vice the ax25 utils).
>
> Whenever I load the ax25 netrom it seems that when I try a netrom  
> connect
> and it fails a kernel panic results soon there after.
>
> So, for the moment I have removed the ax25 utils and am just  
> running Jnos
> 2.0d via a slip link ( I can not get the tun device working with  
> uDev).
> The system is quite solid.
>
> I am curious where the "ip route add (network) via (gateway) dev tunl0
> static onlink" command loads but does not route anymore whereas "ip  
> tunnel
> add (name) remote (remote gw) local (local ip) dev tunl0" does  
> work. Did
> something change with IPROUTE2 ? The ip route add worked for me  
> before and
> allowed ax25ipd links.
>
> I would be more than happy to try any other ideas/patches that may  
> relieve
> the ax25 kernel challanges.
>
> very best wishes, JohnF
> -
> 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
>

--
John Ronan <jronan@tssg.org>, +353-51-302938
Telecommunications Software &  Systems Group,  http://www.tssg.org

Re: 2.6.14-r4 crashing

[Ralf Baechle DL5RB]

On Tue, Oct 25, 2005 at 09:46:25PM +0100, John Ronan wrote:

> I had unending difficulties when trying netrom and kernel 2.6... in  
> the end I gave up and am running 2.4 now for stability.
> 
> Linux version 2.4.29 (root@ei3rcw) (gcc version 3.3.5 (Debian  
> 1:3.3.5-8)) #5 Fri Apr 15 13:37:45 IST 2005
> 
> to be exact.

AX.25 in 2.4 isn't stable without extra patches either.  There's a
patchset known as 9a4gl floating around which most users are quite happy
with - without 2.4 for serious use such as a mailbox or digipeater is
a no go.

At this late stage in the software lifecycle of 2.4 I won't try to
polish these patches into a shape that would make them acceptable for
kernel.org anymore - but if anybody else is interested I'd certainly give
my maintainer's approval.

Oh, and I've declared NET/ROM my next victim for a code overhaul now
that pure AX.25 in 2.6 seems stable enough for month of uptime and all
the important driver work except support for the PR-430 in the 6pack
driver has been submitted and accepted upstream.

73,

  Ralf