|
On Tue, 27 Apr 2004, Julian Anastasov wrote:
> Can you pass this output via ksymoops? You can see
> linux/Documentation/oops-tracing.txt
Here's the output (there are no modules in use and the defaults are
correct for the rest of it):
ksymoops 2.4.5 on i686 2.4.25. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.25/ (default)
-m /boot/System.map-2.4.25 (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.
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:[<c026bd66>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: 00000000 ebx: f4dc49a0 ecx: 00000000 edx: 00000000
esi: 00000000 edi: f4dc49a0 ebp: 96e65a18 esp: c031fd98
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 0, stackpage=c031f000)
Stack: f4dc49a0 c026d0a4 f4dc49a0 f70e38c0 c026db92 f4dc49a0 f70e95a0 00000000
f70e38c0 e9ba7800 f70e38d4 c026de64 f70e95a0 f70e38c0 f70e95a0 00000000
f70e38c0 c026ef27 f70e95a0 f70e38c0 c031fe58 c0391b48 c0229090 00000000
Call Trace: [<c026d0a4>] [<c026db92>] [<c026de64>] [<c026ef27>] [<c0229090>]
[<c0220f4c>] [<c0229090>] [<c0229090>] [<c022129f>] [<c0229090>] [<c02291c0>]
[<c0228cd5>] [<c0229090>] [<c02291c0>] [<c022935a>] [<c02291c0>] [<c02212d8>]
[<c0229046>] [<c02291c0>] [<c021937b>] [<c0219429>] [<c021955e>] [<c011e88d>]
[<c010881d>] [<c01052b0>] [<c01052b0>] [<c010acc8>] [<c01052b0>] [<c01052b0>]
[<c01052dc>] [<c0105342>] [<c0105000>] [<c0105050>]
Code: 89 50 04 89 02 0f b7 43 40 c7 03 00 00 00 00 c7 43 04 00 00
>>EIP; c026bd66 <ip_vs_conn_unhash+5a/90> <=====
>>ebx; f4dc49a0 <END_OF_CODE+34a21de0/????>
>>edi; f4dc49a0 <END_OF_CODE+34a21de0/????>
>>ebp; 96e65a18 Before first symbol
>>esp; c031fd98 <init_task_union+1d98/2000>
Trace; c026d0a4 <ip_vs_check_template+18/44>
Trace; c026db92 <ip_vs_sched_persist+72/32c>
Trace; c026de64 <ip_vs_schedule+18/bc>
Trace; c026ef27 <ip_vs_in+163/310>
Trace; c0229090 <ip_local_deliver_finish+0/130>
Trace; c0220f4c <nf_iterate+30/84>
Trace; c0229090 <ip_local_deliver_finish+0/130>
Trace; c0229090 <ip_local_deliver_finish+0/130>
Trace; c022129f <nf_hook_slow+d7/194>
Trace; c0229090 <ip_local_deliver_finish+0/130>
Trace; c02291c0 <ip_rcv_finish+0/1dc>
Trace; c0228cd5 <ip_local_deliver+181/18c>
Trace; c0229090 <ip_local_deliver_finish+0/130>
Trace; c02291c0 <ip_rcv_finish+0/1dc>
Trace; c022935a <ip_rcv_finish+19a/1dc>
Trace; c02291c0 <ip_rcv_finish+0/1dc>
Trace; c02212d8 <nf_hook_slow+110/194>
Trace; c0229046 <ip_rcv+366/3b0>
Trace; c02291c0 <ip_rcv_finish+0/1dc>
Trace; c021937b <netif_receive_skb+11b/148>
Trace; c0219429 <process_backlog+81/124>
Trace; c021955e <net_rx_action+92/154>
Trace; c011e88d <do_softirq+7d/dc>
Trace; c010881d <do_IRQ+dd/ec>
Trace; c01052b0 <default_idle+0/34>
Trace; c01052b0 <default_idle+0/34>
Trace; c010acc8 <call_do_IRQ+5/d>
Trace; c01052b0 <default_idle+0/34>
Trace; c01052b0 <default_idle+0/34>
Trace; c01052dc <default_idle+2c/34>
Trace; c0105342 <cpu_idle+3e/54>
Trace; c0105000 <_stext+0/0>
Trace; c0105050 <rest_init+50/54>
Code; c026bd66 <ip_vs_conn_unhash+5a/90>
00000000 <_EIP>:
Code; c026bd66 <ip_vs_conn_unhash+5a/90> <=====
0: 89 50 04 mov %edx,0x4(%eax) <=====
Code; c026bd69 <ip_vs_conn_unhash+5d/90>
3: 89 02 mov %eax,(%edx)
Code; c026bd6b <ip_vs_conn_unhash+5f/90>
5: 0f b7 43 40 movzwl 0x40(%ebx),%eax
Code; c026bd6f <ip_vs_conn_unhash+63/90>
9: c7 03 00 00 00 00 movl $0x0,(%ebx)
Code; c026bd75 <ip_vs_conn_unhash+69/90>
f: c7 43 04 00 00 00 00 movl $0x0,0x4(%ebx)
<0>Kernel panic: Aiee, killing interrupt handler!
2 warnings issued. Results may not be reliable.
|
