2.3.15 crashes and other bad things with tcpdump

Pete Clements (clem@clem.digital.net)
Wed, 25 Aug 1999 22:48:07 -0400 (EDT)


Running tcpdump on 2.3.15 causes inbound pings or tcp to no longer
work, outbound connections work fine. The wire traffic shows that
the 2.3.15 machine is responding but the address has been mangled.
A telnet connection generated the first oops. The second oops is
the crash (which is a screen copy) was generated as the result of
a another telnet attempt. pings and ftp attempts as well as a
tcpdump stop and start between the two telnets. Tcpdump on the
2.3.15 box does not see other traffic on wire.

Can generate any additional data that might help.

ksymoops 0.7c on i586 2.3.15. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.3.15/ (default)
-m ./System.map-2.3.15 (specified)

No modules in ksyms, skipping objects
Warning (read_lsmod): no symbols in lsmod, is /proc/modules a valid lsmod file?
c01238a7
Oops: 0000
CPU: 0
EIP: 0010:[<c01238a7>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010082
eax: c7a61c1c ebx: c0421140 ecx: cca61fe0 edx: 00000001
esi: 00000202 edi: c7a61b80 ebp: 0000004a esp: c6f65e20
ds: 0018 es: 0018 ss: 0018
Process tcpdump (pid: 240, stackpage=c6f65000)
Stack: c7a60200 0000004a c6f65ee0 c7a61c1c c0160469 c015fdf6 c7a61b80 c7a601a0
c015ff2e c7a601a0 c6f65efe c7a601a0 c0160b67 c7a601a0 c01897af c7077700
c7a601a0 c6f80efc 0000061c c6f65ea8 c6f65f6c c7077700 0000004a c015c94a
Call Trace: [<c0160469>] [<c015fdf6>] [<c015ff2e>] [<c0160b67>] [<c01897af>] [<c015c94a>] [<c015d694>]
[<c01ad652>] [<c01b98be>] [<c01b49a9>] [<c015df2b>] [<c0107fa4>]
Code: 8b 69 08 81 fd 2b 2f c3 a5 0f 85 fa 00 00 00 8b 69 0c 85 ed

>>EIP; c01238a7 <kfree+77/200> <=====
Trace; c0160469 <memcpy_toiovec+39/70>
Trace; c015fdf6 <kfree_skbmem+26/50>
Trace; c015ff2e <__kfree_skb+10e/120>
Trace; c0160b67 <skb_free_datagram+17/20>
Trace; c01897af <packet_recvmsg+ff/110>
Trace; c015c94a <sock_recvmsg+3a/b0>
Trace; c015d694 <sys_recvfrom+a4/110>
Trace; c01ad652 <con_flush_chars+12/20>
Trace; c01b98be <write_chan+29e/370>
Trace; c01b49a9 <tty_write+1b9/260>
Trace; c015df2b <sys_socketcall+23b/2f0>
Trace; c0107fa4 <system_call+34/38>
Code; c01238a7 <kfree+77/200>
00000000 <_EIP>:
Code; c01238a7 <kfree+77/200> <=====
0: 8b 69 08 movl 0x8(%ecx),%ebp <=====
Code; c01238aa <kfree+7a/200>
3: 81 fd 2b 2f c3 cmpl $0xa5c32f2b,%ebp
Code; c01238af <kfree+7f/200>
8: a5
Code; c01238b0 <kfree+80/200>
9: 0f 85 fa 00 00 jne 109 <_EIP+0x109> c01239b0 <kfree+180/200>
Code; c01238b5 <kfree+85/200>
e: 00
Code; c01238b6 <kfree+86/200>
f: 8b 69 0c movl 0xc(%ecx),%ebp
Code; c01238b9 <kfree+89/200>
12: 85 ed testl %ebp,%ebp

1 warning issued. Results may not be reliable.

ksymoops 0.7c on i586 2.3.15. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.3.15/ (default)
-m ./System.map-2.3.15 (specified)

No modules in ksyms, skipping objects
Warning (read_lsmod): no symbols in lsmod, is /proc/modules a valid lsmod file?
*pde = 00000000
Oops: 0002
CPU: 0
EIP: 0010:[<c015fc5d>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010296
eax: 0000002a ebx: 000000d8 ecx: c0210000 edx: ffffff9d
esi: c016b66d edi: c708e700 ebp: c7b2a9a0 esp: c0211cac
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 0, stackpage=c0211000)
Stack: 00000100 000000d8 c01f40a4 c6fcff18 c7131540 c016b6a7 c7131540 000000d8
c016b66d c6fcff18 c7131540 c70870a0 721d6ceb c0178e8d c7131540 c7b2a9a0
4aefd7cc 49efd7cc c7a778e0 c70870a0 c7a778e0 00000074 c7b2a9a0 c708e700
Call Trace: [<c01f40a4>] [<c016b6a7>] [<c016b66d>] [<c0178e8d>] [<c01790cb>] [<c015fab8>] [<c01c5119>]
[<c0161a0e>] [<c016bb7f>] [<c016c4a9>] [<c01838fc>] [<c01838fc>] [<c0174535>] [<c017966f>] [<c0179884>]
[<c0169047>] [<c0169153>] [<c016945c>] [<c0161ea2>] [<c0118049>] [<c0109024>] [<c0106000>] [<c0108040>]
[<c0106000>] [<c010624b>] [<c0106000>] [<c0100177>]
Code: c7 05 00 00 00 00 00 00 00 00 83 c4 14 5b 5e c3 8d 76 00 a1

>>EIP; c015fc5d <skb_under_panic+2d/40> <=====
Trace; c01f40a4 <lookup.560+8b4/1284>
Trace; c016b6a7 <ip_build_and_send_pkt+77/1f0>
Trace; c016b66d <ip_build_and_send_pkt+3d/1f0>
Trace; c0178e8d <tcp_v4_send_synack+11d/140>
Trace; c01790cb <tcp_v4_conn_request+1eb/260>
Trace; c015fab8 <sock_def_write_space+58/60>
Trace; c01c5119 <loopback_xmit+b9/e0>
Trace; c0161a0e <dev_queue_xmit+be/170>
Trace; c016bb7f <ip_output+8f/100>
Trace; c016c4a9 <ip_build_xmit_slow+499/550>
Trace; c01838fc <fn_hash_lookup+ac/100>
Trace; c01838fc <fn_hash_lookup+ac/100>
Trace; c0174535 <tcp_rcv_state_process+75/7d0>
Trace; c017966f <tcp_v4_do_rcv+14f/1a0>
Trace; c0179884 <tcp_v4_rcv+1c4/390>
Trace; c0169047 <ip_run_ipprot+67/80>
Trace; c0169153 <ip_local_deliver+f3/180>
Trace; c016945c <ip_rcv+27c/310>
Trace; c0161ea2 <net_bh+1b2/230>
Trace; c0118049 <do_bottom_half+49/70>
Trace; c0109024 <do_IRQ+a4/c0>
Trace; c0106000 <get_option+0/60>
Trace; c0108040 <ret_from_intr+0/20>
Trace; c0106000 <get_option+0/60>
Trace; c010624b <cpu_idle+3b/60>
Trace; c0106000 <get_option+0/60>
Trace; c0100177 <L6+0/2>
Code; c015fc5d <skb_under_panic+2d/40>
00000000 <_EIP>:
Code; c015fc5d <skb_under_panic+2d/40> <=====
0: c7 05 00 00 00 movl $0x0,0x0 <=====
Code; c015fc62 <skb_under_panic+32/40>
5: 00 00 00 00 00
Code; c015fc67 <skb_under_panic+37/40>
a: 83 c4 14 addl $0x14,%esp
Code; c015fc6a <skb_under_panic+3a/40>
d: 5b popl %ebx
Code; c015fc6b <skb_under_panic+3b/40>
e: 5e popl %esi
Code; c015fc6c <skb_under_panic+3c/40>
f: c3 ret
Code; c015fc6d <skb_under_panic+3d/40>
10: 8d 76 00 leal 0x0(%esi),%esi
Code; c015fc70 <show_net_buffers+0/50>
13: a1 00 00 00 00 movl 0x0,%eax

Aiee, killing interrupt handler
Kernel panic: Attempted to kill the idle task!
In swapper task - not syncing

1 warning issued. Results may not be reliable.

-- 
Pete Clements 
clem@clem.digital.net

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