RE: [Xen-devel] [PATCH] Add VMDq support to ixgbe

["Santos, Jose Renato G" <joserenato.santos@xxxxxx>]

> -----Original Message-----
> From: Williams, Mitch A [mailto:mitch.a.williams@xxxxxxxxx] 
> Sent: Thursday, February 05, 2009 2:51 PM
> To: Santos, Jose Renato G; xen-devel@xxxxxxxxxxxxxxxxxxx
> Cc: steven.smith@xxxxxxxxxxxxx
> Subject: RE: [Xen-devel] [PATCH] Add VMDq support to ixgbe
> 
> I have not seen this crash, and I am running the latest 
> Netchannel2 code.  Can you send me some more details?  When 
> do you see this crash? 

  When dom0 boots the interface is disabled
  As soon as I bring the interface up (i.e. ifup eth2) the system crashes.
  NO guest is running. Just dom0

  Here is the kenel panic output
  I have also attached the output of "dmesg" and "xm dmesg" that is executed 
just after the system boots
  Could you please send me the same output for your system so I can take a look 
and see if I can spot anything?

  Thanks

  Renato

====================================================
 Unable to handle kernel paging request at 00000000000078c0 RIP: 
 [<ffffffff80471144>] vmq_alloc_skb+0x64/0x1f0
PGD 5e3e5067 PUD 5e3e4067 PMD 0 
Oops: 0000 [1] SMP 
CPU 0 
Modules linked in: video thermal fan button battery asus_acpi ac
Pid: 0, comm: swapper Not tainted 2.6.18.8-xen0 #1
RIP: e030:[<ffffffff80471144>]  [<ffffffff80471144>] vmq_alloc_skb+0x64/0x1f0
RSP: e02b:ffffffff807a7cb0  EFLAGS: 00010206
RAX: ffff88007ed1bd98 RBX: 0000000000000000 RCX: 0000000000080000
RDX: ffff88007edb10c0 RSI: 0000000000000001 RDI: ffff88007ee50000
RBP: ffffffff807a7ce0 R08: 0000000000000001 R09: ffff88007ee50c80
R10: 000000000000003f R11: 000000000000012c R12: 00000000000078c0
R13: 0000000000000000 R14: 0000000000000500 R15: 00000000000005f4
FS:  00002b9d6ed01da0(0000) GS:ffffffff8074c000(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process swapper (pid: 0, threadinfo ffffffff80760000, task ffffffff80660440)
Stack:  ffff88007ee50000 ffffc200118f7000 0000000000000000 0000000000000000
 ffff88007fef0070 ffff88007ee50500 ffffffff807a7d40 ffffffff803db482
 ffffffff807a7d20 000003ff00000001 ffff88005b788000 ffff88007fe90800
Call Trace:
 <IRQ> [<ffffffff803db482>] ixgbe_alloc_rx_buffers+0x152/0x2d0
 [<ffffffff803dd95b>] ixgbe_clean_rx_irq+0x9eb/0xaa0
 [<ffffffff8022c3dd>] default_wake_function+0xd/0x10
 [<ffffffff805b1161>] _spin_unlock_irqrestore+0x11/0x70
 [<ffffffff8022af2e>] __wake_up+0x4e/0x70
 [<ffffffff803e2262>] ixgbe_clean_rxonly_many+0xb2/0x210
 [<ffffffff803eab0e>] __kc_adapter_clean+0x2e/0x50
 [<ffffffff8053fc44>] net_rx_action+0xc4/0x1c0
 [<ffffffff80239eec>] __do_softirq+0x9c/0x140
 [<ffffffff8020b604>] call_softirq+0x1c/0x28
 [<ffffffff8020d7cc>] do_softirq+0x6c/0x100
 [<ffffffff80239d48>] irq_exit+0x48/0x50
 [<ffffffff80440d82>] evtchn_do_upcall+0x232/0x250
 [<ffffffff8020b13a>] do_hypervisor_callback+0x1e/0x2c
 <EOI> [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000
 [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000
 [<ffffffff8020eed2>] raw_safe_halt+0xc2/0xf0
 [<ffffffff80209b15>] xen_idle+0x75/0x90
 [<ffffffff8020926a>] cpu_idle+0xba/0xe0
 [<ffffffff802073b6>] rest_init+0x26/0x30
 [<ffffffff8076a8f5>] start_kernel+0x265/0x270
 [<ffffffff8076a23d>] _sinittext+0x23d/0x250


Code: 4d 39 a6 c0 73 00 00 4d 8d ae a8 73 00 00 0f 84 58 01 00 00 
RIP  [<ffffffff80471144>] vmq_alloc_skb+0x64/0x1f0
 RSP <ffffffff807a7cb0>
CR2: 00000000000078c0
 <0>Kernel panic - not syncing: Aiee, killing interrupt handler!
 (XEN) Domain 0 crashed: 'noreboot' set - not rebooting.



  

> How many VMs do you have running, and 
> with what options?
> 
> Thanks for catching the config option issue.  I'll spin up a 
> new patch and get it out to Steven.
> 
> -Mitch 
>

Attachment: dmesg_linux.out
Description: dmesg_linux.out

Attachment: dmesg_xen.out
Description: dmesg_xen.out

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel