Re: SCC causes kernel crash

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

  • Next message: Stordeur Franck 785966045: "Serial communication with TNC2 using minicom"

    Hi Tomi,

    Thanks for pointer to the syslog config file... Learn something new every day :-))

    Here's the dump from netstat --ax25 and cat /proc/net/ax25

    Linux 2.2.15.
    Last login: Wed Jun 7 12:54:59 +0100 2000 on ttyp1 from g4apl.ampr.org.

    This is the result of netstat --ax25

    gb7cip:root /var/log # cat kernel
    Jun 7 14:38:03 gb7cip kernel: Unable to handle kernel NULL pointer dereference
    Jun 7 14:38:03 gb7cip kernel: current->tss.cr3 = 00dfb000, %cr3 = 00dfb000
    Jun 7 14:38:03 gb7cip kernel: *pde = 00
    Jun 7 14:38:03 gb7cip kernel: Oops: 000
    Jun 7 14:38:03 gb7cip kernel: CPU: 0
    Jun 7 14:38:03 gb7cip kernel: EIP: 0
    Jun 7 14:38:03 gb7cip kernel: EFLAGS: 00010082
    Jun 7 14:38:03 gb7cip kernel: eax: 00000000 ebx: c0fa0f7c ecx: c070b2a1 e
    Jun 7 14:38:03 gb7cip kernel: esi: c0806e10 edi: 000002a1 ebp: 51eb851f e
    Jun 7 14:38:03 gb7cip kernel: ds: 0018 es: 0018 ss: 0018
    Jun 7 14:38:03 gb7cip kernel: Process netstat (pid: 9058, process nr: 69, stack
    Jun 7 14:38:03 gb7cip kernel: Stack: 00000000 c070b000 00000246 c070b27a 0000040
    Jun 7 14:38:03 gb7cip kernel: c0e8bf98 00000000 00000400 00000000 c0fa8c0
    Jun 7 14:38:03 gb7cip kernel: 00000073 c1846940 00000000 00000000 0000000
    Jun 7 14:38:03 gb7cip kernel: Call Trace: [proc_kill_inodes+14/64] [mkiss+2341880]
    [system_call+52/56]
    Jun 7 14:38:03 gb7cip kernel: Code: 8b 58 18 eb 04 89 f6 31 db 53 8b 42 40 50 8

    This is the result of cat /proc/net/ax25

    Jun 7 14:39:48 gb7cip kernel: Unable to handle kernel NULL pointer dereference
    Jun 7 14:39:48 gb7cip kernel: current->tss.cr3 = 00753000, %cr3 = 00753000
    Jun 7 14:39:48 gb7cip kernel: *pde = 00000000
    Jun 7 14:39:48 gb7cip kernel: Oops: 0000
    Jun 7 14:39:48 gb7cip kernel: CPU: 0
    Jun 7 14:39:48 gb7cip kernel: EIP: 0010:[mkiss+23394479/33144832]
    Jun 7 14:39:48 gb7cip kernel: EFLAGS: 00010082
    Jun 7 14:39:48 gb7cip kernel: eax: 00000000 ebx: c0fa0f7c ecx: c0b942a3 e
    Jun 7 14:39:48 gb7cip kernel: esi: c0806e10 edi: 000002a3 ebp: 51eb851f e
    Jun 7 14:39:48 gb7cip kernel: ds: 0018 es: 0018 ss: 0018
    Jun 7 14:39:48 gb7cip kernel: Process cat (pid: 9064, process nr: 29, stackpage
    Jun 7 14:39:48 gb7cip kernel: Stack: 00000000 c0b94000 00000246 c0b9427c 00000c0
    Jun 7 14:39:48 gb7cip kernel: c08f3f98 00000000 00000c00 00000000 c043f30
    Jun 7 14:39:48 gb7cip kernel: 00000000 c1846940 00000000 00000000 0000008
    Jun 7 14:39:48 gb7cip kernel: Call Trace: [proc_kill_inodes+14/64] [mkiss+2341880]
    [system_call+52/56]
    Jun 7 14:39:48 gb7cip kernel: Code: 8b 58 18 eb 04 89 f6 31 db 53 8b 42 40 50 8
    gb7cip:root /var/log #

    In message <terhi.victor@logonet.com>, Tomi
    Manninen OH2BNS <bsbjm.nnbhskrmf@flextel.it> writes
    >On Wed, 7 Jun 2000, Paul Lewis wrote:
    >
    >> 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
    >>
    >> 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.
    >
    >You seem to have somethign odd in /etc/syslog.conf or the kernel default
    >message level. Try to fix that so you get the full register dump to your
    >log file (hopefully with symbols resolved). Otherwise writing it to paper
    >and running through ksymoops is the only way...

    What is ksymoops, no man page on my system. Educated guess Kernel Symbol Oops.
    I have just notice there is ksymoops source in the linux source script directory.

    >
    >The register dump with symbols resolved is the information were interested
    >in.
    >

    Should I input the above dumps into ksymoops after I have compiled ksymoops for the
    information that you require?

    -- 
    terhi.victor@logonet.com
    



    This archive was generated by hypermail 2b29 : Wed Jun 07 2000 - 18:38:31 EEST