WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Kernel panic: not syncing

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Kernel panic: not syncing
From: pak333@xxxxxxxxxxx
Date: Thu, 18 May 2006 18:06:26 +0000
Delivery-date: Thu, 18 May 2006 11:06:51 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hello,
I just launched a couple of guests and tried running iperf. The network is working fine with static IPs. I can ping between all machines.
However, this is what happens when I start iperf with simply
"iperf -c Ipaddress"
 
Can someone shed some light on this
 
Thanks
- Pak
 
Unable to handle kernel NULL pointer dereference at virtual address 000000c9
 printing eip:
c02398cb
0f9bc000 -> *pde = 00000001:96d86001
0d676000 -> *pme = 00000000:00000000
Oops: 0002 [#1]
SMP
Modules linked in:
CPU:    0
EIP:    0061:[<c02398cb>]    Not tainted VLI
EFLAGS: 00010096   (2.6.12.6-xenU)
EIP is at network_tx_buf_gc+0xd9/0x253
eax: 0000002e   ebx: 00000019   ecx: c0600aec   edx: 00000000
esi: 00000045   edi: c0600220   ebp: 0004024c   esp: c04d1cd0
ds: 007b   es: 007b   ss: 0069
Process iperf (pid: 1480, threadinfo=c04d0000 task=cd668a20)
Stack: c0600aec 00000000 c04d0000 00040253 c0600000 00000000 c06002ac c0600220
       c0600000 c023a118 c0600000 c05d2cc0 00000000 c04d1d84 00000107 c013c1f0
       0 0000107 c0600000 c04d1d84 00000000 c031b780 00000107 00008380 c031b79c
Call Trace:
 [<c023a118>] netif_int+0x28/0x117
 [<c013c1f0>] handle_IRQ_event+0x61/0xa5
 [<c013c2f9>] __do_IRQ+0xc5/0x11c
 [<c010d928>] do_IRQ+0x1d/0x28
 [<c0104925>] evtchn_do_upcall+0x87/0xeb
 [<c0109738>] hypervisor_callback+0x2c/0x34
 [<c0210d38>] __copy_from_user_ll+0x35/0x9e
 [<c0210e59>] copy_from_user+0x3d/0xa4
 [<c0106992>] alloc_skb+0x52/0xaa
 [<c025f43f>] tcp_sendmsg+0x238/0xff9
 [<c023bd7d>] sock_aio_write+0xf6/0x108
 [<c015fcaa>] do_sync_write+0xbe/0x102
 [<c0123c45>] do_softirq+0x60/0x69
 [<c0133b27>] autoremove_wake_function+0x0/0x4b
 [<c010b4a3>] do_gettimeofday+0x56/0x250
 [<c015fd8e>] vfs_write+0xa0/0x129
 [<c015fed6>] sys_write+0x4b/0x74
 [<c0109 551>] syscall_call+0x7/0xb
Code: cc 08 00 00 89 04 24 e8 1d ce ec ff 8b 87 c4 00 00 00 89 84 9f c4 00 00 00 c7 84 9f d0 08 00 00 00 00 00 00 89 9f c4 00 00 00 90 <ff> 8e 84 00 00 00 0f 94 c0 84 c0 0f 84 60 ff ff ff 8b 4c 24 08
 <0>Kernel panic - not syncing: Fatal exception in interrupt
 
 
 
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Kernel panic: not syncing, pak333 <=