Re: SCC causes kernel crash

From: Paul Lewis (terhi.victor@logonet.com)
Date: Wed Jun 07 2000 - 15:06:02 EEST

  • Next message: Tomi Manninen OH2BNS: "Re: SCC causes kernel crash"

    Hello Tomi,

    Thanks for taking an interest.

    gb7cip:root /var/log # date
    Wed Jun 7 12:48:18 BST 2000

    gb7cip:root /var/log # cat /proc/net/ax25

    Segmentation fault

    gb7cip:root /var/log # tail syslog
    Jun 7 12:48:28 gb7cip kernel: Unable to handle kernel NULL pointer
    dereference
    Jun 7 12:48:28 gb7cip kernel: current->tss.cr3 = 00a06000, %cr3 =
    00a06000
    Jun 7 12:48:28 gb7cip kernel: *pde = 00000000

    gb7cip:root /var/log # date
    Wed Jun 7 12:48:54 BST 2000

    gb7cip:root /var/log # netstat --ax25

    Active AX.25 sockets
    Dest Source Device State Vr/Vs Send-Q Recv-Q
    Segmentation fault
    gb7cip:root /var/log # tail syslog
    Jun 7 12:49:01 gb7cip kernel: Unable to handle kernel NULL pointer
    dereference
    Jun 7 12:49:01 gb7cip kernel: current->tss.cr3 = 00a06000, %cr3 =
    00a06000
    Jun 7 12:49:01 gb7cip kernel: *pde = 00000000
    gb7cip:root /var/log #

    On the console screen I get the memory dump related to the segmention.
    Can not seem to save that to a file. Other than write out the screen to
    paper for input on my internet connect PC.

    ##########
    The only other thing that I have JUST noticed another problem, when I
    telnet in from my LAN connected PC, Which I will try and find the
    related module
    Jun 7 12:54:49 gb7cip in.telnetd[7165]: connect from 44.131.244.61
    Jun 7 12:54:50 gb7cip modprobe: can't locate module char-major-5
    Jun 7 12:54:59 gb7cip login[7167]: ROOT LOGIN on `ttyp1' from
    `g4apl.ampr.org

    Have just checked back through some of my back up logs for the past few
    days. Seem to be consistent
    ##########

    In message <xoeq@atlantech.net
    a.com>, Tomi Manninen OH2BNS <hjspz@trasys.be> writes
    >On Wed, 7 Jun 2000, Paul Lewis wrote:
    >
    >> Like others, I have been suffering with a problem since December 1999
    >> when I switched from 2.0.35 kernel +ax25 to the new 2.2.13, 2.2.14 to
    >> the current 2.2.15.
    >>
    >> The problem I have is with the Ax25 code. (maybe nothing wrong with the
    >> code - I still have a problem to solve)
    >>
    >> The AX25 interface(s) normally one of the very busy ax25 interfaces.
    >> (they all run TCP/IP,AX25,NetROm over them) stop working decoding for
    >> AX25 data, yet the TCP/IP stack continues to work over the interface.
    >
    >Next time this happens, could you try "cat /proc/net/ax25" and if it
    >succeeds send the output here. Also do you see anything strange in the
    >system logs?
    > 

    -- 
ujbaz.hesvwlq@rapiddsl.net

    This archive was generated by hypermail 2b29 : Wed Jun 07 2000 - 16:09:08 EEST