[2.2.13 - 14] Oops (with ppp ?)

From: Thomas (sarfata@altern.org)
Date: Fri Apr 21 2000 - 16:14:08 EDT

  • Next message: bert hubert: "Re: [bug] es1371 hangs"

    Hi,

    I have a dual-celery Abit BP6 mobo at 450 Mhz (not overclocked), with
    128Mo of RAM, Adaptec AHA2940U2W, a tulip-based and a ne2k-pci.
    I use an ADSL connection, which opens a pppd connection over a pptp
    (VPN) connection.

    I am having some really annoying problems :
    My system crashes quite randomly from once a day to 5 times a day. I
    have only figured out recently, that it would crash when I play
    Half-Life on a WinBox on my private network (my system acts as a
    firewall), but not only in Half Life. Hangs seems to be related to user
    inputs since it almost never crashes when i am not using it (though it
    does dnetc, shoutcast, and lots of other services all day long).

    I had to copy the oops on a paper, because it would not get logged.
    Once it happenned, the box is completely frozen (no keyleds answer).

    Here is the oops :
    -------------------
    Oops: 0000
    CPU: 1
    EIP: 0010:[<c0113512>]
    EFLAGS: 00010287
    eax: c26d496c ebx: 400eff48 ecx: 00000000 edx: 400eff40
    esi: c26d4968 edi: 00000001 ebp: c40ebbd8 esp: c40ebbc8
    ds: 0018 es:0018 ss: 0018
    Process swapper (pid 0, process nr: 17, stackpage=c40eb000)
    Stack: c26c279f 0000000b 00000282 c4054ea0 00000000 c01b84bb c3a07000
    c26d4000
           0000003a c3a07234 c481e50f c3016c80 00000084 00000286 00000000
    00a07048
           c2db2c5c ffff87a4 c4054d80 c29187e0 c3016c80 00000084 0000c400
    c3016c80
    Call Trace: [<c01b84bb>] [<c481e50f>] [<c015f11c>] [<c015f1da>]
    [<c01638db>] [<c01c62bf>] [<c01c04f1>]
                [<c01c5f63>] [<c01c5e7d>] [<c01c8306>] [<c0185cf9>]
    [<c01c8a40>] [<c0160c77>] [<c0165675>] [<c015e0a6>]
                [<c0160dea>] [<c0160dbc>] [<c016dd42>] [<c016de4c>]
    [<c016d13b>] [<c015f202>] [<c01611a2>] [<c011b589>]
                [<c010b889>] [<c010b8a0>] [<c01103f4>] [<c010a2f8>]
    [<c0100018>] [<c0107f77>] [<c0113309>] [<c0107954>]
                [<c011b589>] [<c0106000>] [<c010b889>] [<c010b8a0>]
    [<c02091e0>]
    Code: 8b 02 85 f8 74 f1 39 f3 75 10 f0 ff 0d 4c e1 24 c0 89 d0 e8
    Aiee, killing interrupt handler
    Kernel panic: Attempted to kill the idle task!
    In interrupt handler - not syncing
    --------------------------------

    and here is ksym 2.3.4 output
    ------------------------------------
    ksymoops 2.3.4 on i686 2.2.14. Options used
         -V (default)
         -k /proc/ksyms (default)
         -l /proc/modules (default)
         -o /lib/modules/2.2.14/ (default)
         -m /usr/src/linux/System.map (default)

    Warning: You did not tell me where to find symbol information. I will
    assume that the log matches the kernel and modules that are running
    right now and I'll use the default options above for symbol resolution.
    If the current kernel and/or modules do not match the log, you can get
    more accurate output by telling me the kernel version and where to find
    map, modules, ksyms etc. ksymoops -h explains the options.

    Oops: 0000
    CPU: 1
    EIP: 0010:[<c0113512>]
    Using defaults from ksymoops -t elf32-i386 -a i386
    EFLAGS: 00010287
    eax: c26d496c ebx: 400eff48 ecx: 00000000 edx: 400eff40
    esi: c26d4968 edi: 00000001 ebp: c40ebbd8 esp: c40ebbc8
    ds: 0018 es:0018 ss: 0018
    Process swapper (pid 0, process nr: 17, stackpage=c40eb000)
    Stack: c26c279f 0000000b 00000282 c4054ea0 00000000 c01b84bb c3a07000
    c26d4000
           0000003a c3a07234 c481e50f c3016c80 00000084 00000286 00000000
    00a07048
           c2db2c5c ffff87a4 c4054d80 c29187e0 c3016c80 00000084 0000c400
    c3016c80
    Call Trace: [<c01b84bb>] [<c481e50f>] [<c015f11c>] [<c015f1da>]
    [<c01638db>] [<c01c62bf>] [<c01c04f1>]
                [<c01c5f63>] [<c01c5e7d>] [<c01c8306>] [<c0185cf9>]
    [<c01c8a40>] [<c0160c77>] [<c0165675>] [<c015e0a6>]
                [<c0160dea>] [<c0160dbc>] [<c016dd42>] [<c016de4c>]
    [<c016d13b>] [<c015f202>] [<c01611a2>] [<c011b589>]
                [<c010b889>] [<c010b8a0>] [<c01103f4>] [<c010a2f8>]
    [<c0100018>] [<c0107f77>] [<c0113309>] [<c0107954>]
                [<c011b589>] [<c0106000>] [<c010b889>] [<c010b8a0>]
    [<c02091e0>]
    Code: 8b 02 85 f8 74 f1 39 f3 75 10 f0 ff 0d 4c e1 24 c0 89 d0 e8

    >>EIP; c0113512 <__wake_up+2e/64> <=====
    Trace; c01b84bb <n_tty_receive_buf+b57/b98>
    Trace; c481e50f <[8390]ei_start_xmit+40f/420>
    Trace; c015f11c <kfree_skbmem+3c/4c>
    Trace; c015f1da <__kfree_skb+ae/b8>
    Trace; c01638db <neigh_resolve_output+cf/154>
    Trace; c01c62bf <ppp_async_encode+29f/2d0>
    Trace; c01c04f1 <pty_write+169/178>
    Trace; c01c5f63 <ppp_tty_push+d3/190>
    Trace; c01c5e7d <ppp_async_send+71/84>
    Trace; c01c8306 <ppp_send_frame+272/2a0>
    Trace; c0185cf9 <ip_fw_check+511/624>
    Trace; c01c8a40 <ppp_dev_xmit+390/460>
    Trace; c0160c77 <dev_queue_xmit_nit+1b/d8>
    Trace; c0165675 <qdisc_restart+45/80>
    Trace; c015e0a6 <call_out_firewall+36/54>
    Trace; c0160dea <dev_queue_xmit+46/e4>
    Trace; c0160dbc <dev_queue_xmit+18/e4>
    Trace; c016dd42 <ip_forward+30a/584>
    Trace; c016de4c <ip_forward+414/584>
    Trace; c016d13b <ip_rcv+2ef/320>
    Trace; c015f202 <skb_clone+1e/a0>
    Trace; c01611a2 <net_bh+1a2/200>
    Trace; c011b589 <do_bottom_half+89/ac>
    Trace; c010b889 <do_IRQ+3d/58>
    Trace; c010b8a0 <do_IRQ+54/58>
    Trace; c01103f4 <do_edge_ioapic_IRQ+78/a8>
    Trace; c010a2f8 <common_interrupt+18/20>
    Trace; c0100018 <startup_32+18/a4>
    Trace; c0107f77 <__switch_to+2f/b8>
    Trace; c0113309 <schedule+1f1/3cc>
    Trace; c0107954 <cpu_idle+4c/54>
    Trace; c011b589 <do_bottom_half+89/ac>
    Trace; c0106000 <get_options+0/7c>
    Trace; c010b889 <do_IRQ+3d/58>
    Trace; c010b8a0 <do_IRQ+54/58>
    Trace; c02091e0 <lk_lockmsg+980/1700>
    Code; c0113512 <__wake_up+2e/64>
    00000000 <_EIP>:
    Code; c0113512 <__wake_up+2e/64> <=====
       0: 8b 02 mov (%edx),%eax <=====
    Code; c0113514 <__wake_up+30/64>
       2: 85 f8 test %edi,%eax
    Code; c0113516 <__wake_up+32/64>
       4: 74 f1 je fffffff7 <_EIP+0xfffffff7>
    c0113509 <__wake_up+25/64>
    Code; c0113518 <__wake_up+34/64>
       6: 39 f3 cmp %esi,%ebx
    Code; c011351a <__wake_up+36/64>
       8: 75 10 jne 1a <_EIP+0x1a> c011352c
    <__wake_up+48/64>
    Code; c011351c <__wake_up+38/64>
       a: f0 ff 0d 4c e1 24 c0 lock decl 0xc024e14c
    Code; c0113523 <__wake_up+3f/64>
      11: 89 d0 mov %edx,%eax
    Code; c0113525 <__wake_up+41/64>
      13: e8 00 00 00 00 call 18 <_EIP+0x18> c011352a
    <__wake_up+46/64>

    Aiee, killing interrupt handler
    Kernel panic: Attempted to kill the idle task!

    1 warning issued. Results may not be reliable.
    ------------------------------------

    The problemes seems to be related to ppp, but i am not sure at all.

    If you can help me, i would be glad to help you carsh my box if you need
    more datas, or anything.

    I should also say, that i had the same problem with 2.2.13, that i
    upgraded and that it did not get any better.

    Thanx

    Thomas Sarlandie

    PS: Please CC answers to me, as i have not subscribed to linux-kernel.
    thx

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/



    This archive was generated by hypermail 2b29 : Fri Apr 21 2000 - 16:24:01 EDT