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/
Home Products Support Community News


[Xen-bugs] [Bug 1294] Kernel Dom0 Oops on high network traffic load, xe

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1294] Kernel Dom0 Oops on high network traffic load, xen 3.2.1-testing
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Fri, 18 Jul 2008 12:56:30 -0700
Delivery-date: Fri, 18 Jul 2008 12:56:35 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <bug-1294-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

wickbt@xxxxxxx changed:

           What    |Removed                     |Added
                 CC|                            |wickbt@xxxxxxx

------- Comment #2 from wickbt@xxxxxxx  2008-07-18 12:56 -------
I've just run into this as well on a Dell Poweredge 2970, Xen 3.2.1 with kernel from the mercurial repo. The only VM running at the time of the
crash was a 64-bit paravirtual instance, same kernel as Dom0.

Manually installing and inserting the latest bnx2 drivers (bnx2-1.7.1c) in
place of the 1.4.44 version included in the Xen kernel seems to resolve this; I
haven't been able to recreate the panic after doing so.

- Tim Wickberg

Kernel oops is:

bnx2: peth0: BUG! Tx ring full when queue awake!
Unable to handle kernel NULL pointer dereference at 00000000000000e8 RIP:
 [<ffffffff8804de83>] :bnx2:bnx2_poll+0xf8/0xc42
PGD 1f725067 PUD 1f726067 PMD 0
Oops: 0000 [1] SMP
Modules linked in: xt_physdev iptable_filter ip_tables x_tables mptctl mptbase
bridge button ac battery ipmi_devintf ipmi_si ipmi_msghandler ipv6 ext3 jbd
serio_raw pcspkr igb i2c_piix4 sfc mii i2c_core tsdev joydev usbhid reiserfs
dm_mirror dm_snapshot dm_mod ide_generic sd_mod ide_cd cdrom megaraid_sas
scsi_mod bnx2 ehci_hcd ohci_hcd usbcore serverworks thermal fan
Pid: 0, comm: swapper Not tainted #2
RIP: e030:[<ffffffff8804de83>]  [<ffffffff8804de83>] :bnx2:bnx2_poll+0xf8/0xc42
RSP: e02b:ffffffff80531da0  EFLAGS: 00010286
RAX: 000000000000aeb3 RBX: ffff88001b59daf0 RCX: 000000000000aeb2
RDX: 0000000000000001 RSI: 00000000000000af RDI: ffff880001086000
RBP: ffff880001086500 R08: 0000000000000000 R09: 000000010002b27b
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000aeb2aeaf
R13: 0000000000000000 R14: 000000010002b277 R15: ffff88001c53c000
FS:  00002aec6f483ae0(0000) GS:ffffffff804db000(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process swapper (pid: 0, threadinfo ffffffff804f2000, task ffffffff804654e0)
Stack:  ffff880020767600 ffffffff80531eac ffffffff80531eac ffff880001086000
 ffffffff80000000 ffff88001f41ca12 ffffffff80531dd8 ffffffff80531e60
 ffff88001f908ec0 ffff880020767600 0000000000000000 0000000000000001
Call Trace:
 <IRQ> [<ffffffff8039c71f>] netif_receive_skb+0x1ca/0x2eb
 [<ffffffff8039e727>] process_backlog+0xd0/0x182
 [<ffffffff8039e9a2>] net_rx_action+0xe3/0x24a
 [<ffffffff8808abf2>] :megaraid_sas:megasas_isr+0x19/0x282
 [<ffffffff80234d4c>] __do_softirq+0x83/0x117
 [<ffffffff8020b1b0>] call_softirq+0x1c/0x28
 [<ffffffff8020d011>] do_softirq+0x6a/0xed
 [<ffffffff8020cf9e>] do_IRQ+0x6a/0x73
 [<ffffffff8034fd4e>] evtchn_do_upcall+0x13c/0x1fb
 [<ffffffff8020ace6>] do_hypervisor_callback+0x1e/0x2c
 <EOI> [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000
 [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000
 [<ffffffff8020e39c>] raw_safe_halt+0xb8/0xdd
 [<ffffffff8020984d>] xen_idle+0x6d/0x80
 [<ffffffff80209024>] cpu_idle+0xab/0xce
 [<ffffffff804fc7d2>] start_kernel+0x269/0x26e
 [<ffffffff804fc215>] _sinittext+0x215/0x21b

Code: 49 8b 85 e8 00 00 00 66 83 78 06 00 74 20 8b 40 04 ff c0 41
RIP  [<ffffffff8804de83>] :bnx2:bnx2_poll+0xf8/0xc42
 RSP <ffffffff80531da0>
CR2: 00000000000000e8
 <0>Kernel panic - not syncing: Aiee, killing interrupt handler!
 (XEN) Domain 0 crashed: rebooting machine in 5 seconds.

Specific hardware:

03:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev c3) (prog-if
00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=03, secondary=04, subordinate=04, sec-latency=64
        Memory behind bridge: ec000000-edffffff
        Capabilities: [60] Express PCI/PCI-X Bridge IRQ 0
        Capabilities: [90] PCI-X bridge device
        Capabilities: [b0] Power Management version 2

04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit
Ethernet (rev 12)
        Subsystem: Dell Unknown device 0205
        Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 18
        Memory at ec000000 (64-bit, non-prefetchable) [size=32M]
        Capabilities: [40] PCI-X non-bridge device
        Capabilities: [48] Power Management version 2
        Capabilities: [50] Vital Product Data
        Capabilities: [58] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list