| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] iptables causing kernel panic - part II
Keir Fraser wrote:
On 15 May 2006, at 16:35, Matt Ayres wrote:
Here is my trace, I was not able to get the Code line unfortunately so
I don't have specific line numbers. I'd like re-confirmation this is
not specific to Xen. If it is not I will be sending this over to LKML.
There are no Xen-specific functions in the backtrace. This doesn't mean
it isn't a Xen bug (since we make various pervasive functions that are
used all over the place) but it does make it less likely. Certainly
there's nothing in the backtrace that we can use to track down the bug.
We would need a line number, or a kernel image or something like that.
I'll try to get the Code line next time. Is there a more preferred
method than using ksymoops? It seems ksymoops is depreciated as a
/proc/ksyms doesn't even exist on my system and Fedora has stopped
shipping RPM's for it. I do have the vmlinux file and System.map if
that would help.
Sometimes the panic includes xen_idle, ex:
EIP is at ipt_do_table+0xad/0x2d0
eax: 00000002 ebx: cadc221e ecx: cadc221e edx: 00000000
esi: d13f6000 edi: 00004000 ebp: d13f9c20 esp: c0525dd0
ds: 007b es: 007b ss: 0069
Process swapper (pid: 0, threadinfo=c0524000 task=c04a8c00)
Stack: <0>c04dc0ac 00000000 cadc221e 00000000 c83a1000 cfd60000 d13f6000
00000000
00000001 00000000 c0525e70 80000000 c03aeca8 cfd60000 c03e1e18
c0525eb4
00000002 c83a1000 cfd60000 c04dc080 00000000 c03a4420 00000002
c0525eb4
Call Trace:
[<c03aeca8>] ip_forward_finish+0x0/0x36
[<c03e1e18>] ipt_hook+0x1c/0x20
[<c03a4420>] nf_iterate+0x2c/0x5e
[<c03aeca8>] ip_forward_finish+0x0/0x36
[<c03aeca8>] ip_forward_finish+0x0/0x36
PORT HISTORY> next
[<c03a451b>] nf_hook_slow+0x3c/0xc3
[<c03aeca8>] ip_forward_finish+0x0/0x36
[<c03aee7c>] ip_forward+0x19e/0x22e
[<c03aeca8>] ip_forward_finish+0x0/0x36
[<c03add9b>] ip_rcv+0x40e/0x48f
[<c037f289>] netif_receive_skb+0x2b9/0x2f7
[<c037f382>] process_backlog+0xbb/0x14b
[<c037d2ee>] net_rx_action+0xaa/0x17c
[<c011ea03>] __do_softirq+0x73/0xf0
[<c011eac0>] do_softirq+0x40/0x64
[<c010606b>] do_IRQ+0x1f/0x25
[<c02fdfa4>] evtchn_do_upcall+0x60/0x96
[<c0104a2c>] hypervisor_callback+0x2c/0x34
[<c010342e>] xen_idle+0x5e/0x7d
[<c0103509>] cpu_idle+0xbc/0xd5
[<c05264e0>] start_kernel+0x344/0x34b
Code: 89 44 24 18 89 c6 8b 44 24 40 8b 6c 24 18 03 74 83 0c 03 6c 83 20
c7 44 24 0c 00 00 00 00 0f b7 54 24 06 8b 5c 24 08 89 54 24 1c <8a> 4e
53 88 4c 24 23 8b 46 08 0f b6 c9 23 43 0c 3b 06 89 c8 0f
<0>Kernel panic - not syncing: Fatal exception in interrupt
(XEN) Domain 0 crashed: rebooting machine in 5 seconds.
I have the Code line for this, but unfortunately I do not have the
System.map that corresponds to this particular kernel.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home