linux crashes

linux crashes

[Tom Vavra]

In mid December I replaced my DOS based packetcluster system with a Linux
based DXSpider system.  Since that time I have had 5 system crashes.  I
think all are the same.  Enclosed at the end is the transcribed crash
screen.  I tried to proof it, but I would not bet too much that I got it
correct.

I am running RedHat 9.0 with a 2.4.20 kernel.  The netrom/ax25 packages are:

  ax25-apps-0.0.6
  ax25-tools-0.0.8
  libax25-0.0.11
  node-0.3.1

I am using three serial ports to drive tncs.  Two of the tncs are tapr-2
(MFJ-1270b) with BPQKISS eproms, and the other tnc is a two port KPC-9612,
using both ports.  So I am driving all three ports with mkiss, followed by
kissattach.  Two netrom ports are defined.  And I am running mheardd.

The cpu is a 450mhz pentium that idles at less than 2%, and there is 256Mb
of memory so swap is almost nonexistant.

Anyone have any ideas about what I need to do to eliminate the crashes?

             Tom  WB8ZRL

here is the crash screen

[<d08a8c04>] ax25_packet_type [ax25] 0x0 (0cx0341e60))
[<d089eca4>] ax25_kiss_rcv [ax25] 0x84 (0xc0341e68))
[<d08a8c04>] ax25_packtet_type [ax25] 0x0 (0xc0341e78))
[<c01ee677>] deliver_to_old_ones [kernel]] 0x77 (0xc0341e80))
[<d08a8c04>] ax25_packet_type [ax25] 0x0 (0xc0341e8c))
[<c01ee88b>] netif_receive_skb [kernel] 0x12b (0xc034e98))
[<d08a8c04>] ax25_packet_;type [ax25] 0x0 0xc0341e9c))
[<c01ee9dd>] process_backlog [kernel] 0x6d (0xc0341eb8))
[<c01eeaea>] net_rx_action [kernel] 0x6a (0xc0341ed0))
[<c0121555>] do_softirq [kernel] 0x95 (0xc0341eec))
[<c010ac8e>] do_IRQ [kernel] 0xbe (0xc0341f04))
[<c010d768>] call_do_IRQ [kernel] 0x5 (0xc0341f24))
[<c011569e>] apm_bios_call_simple [kernel] 0x6e (0xc0341f70))
[<c0115807>] amp_do_idle [kernel] 0x27 (0xc0341fa8))
[<c011595b>] amp_cpu_idle [kernel] 0xbb (0xc0341fc0))
[<c01158a0>] amp_cpu_idle [kernel] 0x0 (0xc0341fc4))
[<c0107040>] default_idle [kernel] 0x0 (0xc0341fd0))
[<c01070f2>] cpu_idle [kernel] 0x42 (0xc0341fd4))
[<c0105000>] stext [kernel] 0x0 (0xc0341fe0))

Code: 8b 53 fc 8b 02 85 c7 75 17 8b 1b 39 f3 75 f1 ff 75 f0 9d 83
 <0>Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing

Re: linux crashes

[Ian Haver]

On Sun, 9 Jan 2005 20:59:51 -0000, Tom Vavra <wb8zrl@avalon.net> wrote:

> In mid December I replaced my DOS based packetcluster system with a Linux
> based DXSpider system.  Since that time I have had 5 system crashes.  I
> think all are the same.  Enclosed at the end is the transcribed crash
> screen.  I tried to proof it, but I would not bet too much that I got it
> correct.
>
> I am running RedHat 9.0 with a 2.4.20 kernel.  The netrom/ax25 packages  
> are:
>
>   ax25-apps-0.0.6
>   ax25-tools-0.0.8
>   libax25-0.0.11
>   node-0.3.1
>
> I am using three serial ports to drive tncs.  Two of the tncs are tapr-2
> (MFJ-1270b) with BPQKISS eproms, and the other tnc is a two port  
> KPC-9612,
> using both ports.  So I am driving all three ports with mkiss, followed  
> by
> kissattach.  Two netrom ports are defined.  And I am running mheardd.
>
> The cpu is a 450mhz pentium that idles at less than 2%, and there is  
> 256Mb
> of memory so swap is almost nonexistant.
>
> Anyone have any ideas about what I need to do to eliminate the crashes?
>
>              Tom  WB8ZRL
>

HI Tom
I had similar problem with my suse distro.
I had to download a new kernel and patch it up.
The files can be found on my server here at YFS but i dont have the  
fastest ADSL link.
You are more than welcome to download them.
they can be found at:
http://gb7yfs.org.uk/public/linux/new_kernel_bits/

also in that directory is all the ax25 bits i used here.
When i was running 2.4.20 i could average around 10 days uptime, since i  
upgraded it runs and runs and runs till i reboot it. LOL

Hope this helps a little

Best Regards
Ian
G6VEY
SYSOP GB7YFS
Author Xarpm Plus


-- 
Using Linux M2, Opera's revolutionary e-mail client:  
http://www.opera.com/m2/

Re: linux crashes

[Kjell Jarl]

Hi, is this the netrom-bug?
Since I applied 9a4gl patch to my 2.4.21 kernel it has been fine.
73
Kjell, sm7gvf


Ian Haver wrote:
> On Sun, 9 Jan 2005 20:59:51 -0000, Tom Vavra <wb8zrl@avalon.net> wrote:
> 
>> In mid December I replaced my DOS based packetcluster system with a Linux
>> based DXSpider system.  Since that time I have had 5 system crashes.  I
>> think all are the same.  Enclosed at the end is the transcribed crash
>> screen.  I tried to proof it, but I would not bet too much that I got it
>> correct.
>>
>> I am running RedHat 9.0 with a 2.4.20 kernel.  The netrom/ax25 
>> packages  are:
>>
>>   ax25-apps-0.0.6
>>   ax25-tools-0.0.8
>>   libax25-0.0.11
>>   node-0.3.1
>>
>> I am using three serial ports to drive tncs.  Two of the tncs are tapr-2
>> (MFJ-1270b) with BPQKISS eproms, and the other tnc is a two port  
>> KPC-9612,
>> using both ports.  So I am driving all three ports with mkiss, 
>> followed  by
>> kissattach.  Two netrom ports are defined.  And I am running mheardd.
>>
>> The cpu is a 450mhz pentium that idles at less than 2%, and there is  
>> 256Mb
>> of memory so swap is almost nonexistant.
>>
>> Anyone have any ideas about what I need to do to eliminate the crashes?
>>
>>              Tom  WB8ZRL
>>
> 
> HI Tom
> I had similar problem with my suse distro.
> I had to download a new kernel and patch it up.
> The files can be found on my server here at YFS but i dont have the  
> fastest ADSL link.
> You are more than welcome to download them.
> they can be found at:
> http://gb7yfs.org.uk/public/linux/new_kernel_bits/
> 
> also in that directory is all the ax25 bits i used here.
> When i was running 2.4.20 i could average around 10 days uptime, since 
> i  upgraded it runs and runs and runs till i reboot it. LOL
> 
> Hope this helps a little
> 
> Best Regards
> Ian
> G6VEY
> SYSOP GB7YFS
> Author Xarpm Plus
> 
> 

Re: linux crashes

[Rodolfo Brasnarof]

On Sun, 09 Jan 2005 23:23:28 -0000
Ian Haver wrote:

> On Sun, 9 Jan 2005 20:59:51 -0000, Tom Vavra <wb8zrl@avalon.net>
> wrote:
> 
> > In mid December I replaced my DOS based packetcluster system with a
> > Linux based DXSpider system.  Since that time I have had 5 system
> > crashes.  I think all are the same.  Enclosed at the end is the
> > transcribed crash screen.  I tried to proof it, but I would not bet
> > too much that I got it correct.
> >
> > I am running RedHat 9.0 with a 2.4.20 kernel.  The netrom/ax25
> > packages  are:
> >
> >   ax25-apps-0.0.6
> >   ax25-tools-0.0.8
> >   libax25-0.0.11
> >   node-0.3.1
> >
> > I am using three serial ports to drive tncs.  Two of the tncs are
> > tapr-2(MFJ-1270b) with BPQKISS eproms, and the other tnc is a two
> > port  KPC-9612,
> > using both ports.  So I am driving all three ports with mkiss,
> > followed  by
> > kissattach.  Two netrom ports are defined.  And I am running
> > mheardd.
> >
> > The cpu is a 450mhz pentium that idles at less than 2%, and there is
> >  
> > 256Mb
> > of memory so swap is almost nonexistant.
> >
> > Anyone have any ideas about what I need to do to eliminate the
> > crashes?
> >
> >              Tom  WB8ZRL
> >
> 
> HI Tom
> I had similar problem with my suse distro.
> I had to download a new kernel and patch it up.
> The files can be found on my server here at YFS but i dont have the  
> fastest ADSL link.
> You are more than welcome to download them.
> they can be found at:
> http://gb7yfs.org.uk/public/linux/new_kernel_bits/
> 
> also in that directory is all the ax25 bits i used here.
> When i was running 2.4.20 i could average around 10 days uptime, since
> i  upgraded it runs and runs and runs till i reboot it. LOL
> 
> Hope this helps a little

You can still set your system to automatically reboot in case of a
kernel panic. Of course is better to fix the problem, but for an
unattended system this setting can be useful.

You can do this by adding a line

	echo 1 > /proc/sys/kernel/panic

to your startup scripts (maybe rc.local)

or adding a line

	kernel.panic = 1

to sysctl.conf

The 1 means the number of seconds to wait for reboot after a kernel
panic. 0 means no reboot.

[ANN] qle-0.0.3 GUI logger/log editor released.

[Wilbert Knol]

GPL 2 or later applies. Download the 82 kbyte archive from:

    http://www.qsl.net/zl2arn/qle-0.0.3.tar.gz

Copy to your home directory, and unzip as a non-root user with:

    tar xvzf qle-0.0.3.tar.gz

Read the README.

Requirements:
--------------------

    Perl/Tk
    Hamlib 1.2.3 (highly recommended)
    cwdaemon (optional)
    A reasonably quick machine with a 1024x768 px (or better) screen.

A clipping from the README follows - use a fixed font. Have fun.

Wilbert, ZL2BSJ

----- cut here ------

1. Introduction.
----------------

The qle-package contains the program qle.pl: a graphic QSO log viewer,
log editor and QSO logger for amateur radio operators.

"qle.pl" stands for QSO Logger and Editor. It is a Perl/Tk script that
logs and modifies QSOs directly to a fast and light-weight SQLite
database.

Intended use: casual logging of rag-chew and contest QSOs. The logger
caters for CW operators. See 'Features' list below.

Table headings, fonts, colours and other attributes are set in a
user-editable configuration file. The SQLite log schema supplied may
be altered to suit your taste, provided the configuration file is
updated accordingly (untested).

If you are looking for a performance contest logger, consider using
TLF by PA0R. Similarly,  XLOG (PG4I) and KLOG (EA4TV) are very good
general-purpose loggers that are more intuitive to configure and use.


2. Features.
------------

1. Hamlib rig control. A Hamlib-interfaced radio is higly recommended,
   unless you are fond of manually keeping track of band and mode info.

2. For contesters: computer-generated CW with 'cwdaemon'.

3. The provided (and recommended) database schema logs the following
   items:

   day, month, year, UTC, call, RST sent, serial number sent, RST
   received, serial number received, frequency, mode, operator, QTH,
   my power, his power, QSL sent, QSL received, comment

4. On-the-fly dupe checking by band/mode for contesters.

5. Real-time and delayed (post-QSO) data entry.

6. Built-in log searching and log editing.

7. Complete lack of documentation other than the README and the
   commented configuration file.

8. The logger does not track scores and has no band-map or DX-cluster
   support. There is no voice keyer support. Casual logging and DX-ing
   only.

<EOF>


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

Re: [ANN] qle-0.0.3 GUI logger/log editor released.

[Wilbert Knol]

On Friday 14 January 2005 09:16, Wilbert Knol wrote:
> GPL 2 or later applies. Download the 82 kbyte archive from:
>
>     http://www.qsl.net/zl2arn/qle-0.0.3.tar.gz

New URL:

     http://zl2arn.ath.cx/zl2bsj/qle-0.0.3.tar.gz

Thanks to Gordon ZL2ARN for hosting the archive.


Wilbert, ZL2BSJ