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 543] domU: BUG: soft lockup detected on CPU#1!

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 543] domU: BUG: soft lockup detected on CPU#1!
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 28 Jun 2006 19:19:32 -0700
Delivery-date: Wed, 28 Jun 2006 19:20:37 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <bug-543-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/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

swbrown@xxxxxxxxxxxx changed:

           What    |Removed                     |Added
                 CC|                            |swbrown@xxxxxxxxxxxx

------- Comment #30 from swbrown@xxxxxxxxxxxx  2006-06-28 19:19 -------
Same 'soft lockup' bug here - happened on a vm that was doing a lot of network
work at that moment, and routing that traffic through the other vms.  Locked
up, had to reboot it.  This is with Debian's current xen hypervisor
(3.0.2+hg9697-1) and kernel (linux-image-2.6.16-2-xen-686: 2.6.16-15).  That vm
had been running fine up until this, and shouldn't have been doing anything
different at the moment it locked up, as it only runs one specialized
application.  dom0 is used as a desktop so might have been somewhat high load
at the time.

BUG: soft lockup detected on CPU#0!

Pid: 0, comm:              swapper
EIP: 0061:[<b0101227>] CPU: 0
EIP is at 0xb0101227
 EFLAGS: 00000246    Not tainted  (2.6.16-1-xen-686 #1)
EAX: 00030000 EBX: 00000000 ECX: 00000000 EDX: b0946000
ESI: 0000040f EDI: 00000002 EBP: b0c98280 DS: 007b ES: 007b
CR0: 8005003b CR2: a7e4a0c7 CR3: 0211e000 CR4: 00000640
 [<b0200f2c>] force_evtchn_callback+0xa/0xc
 [<b020d831>] network_start_xmit+0x2b1/0x2fc
 [<b022cff5>] qdisc_restart+0xf5/0x207
 [<b0220e7b>] dev_queue_xmit+0x19a/0x2ae
 [<b023e4b9>] ip_output+0x20e/0x26d
 [<b023ab64>] ip_forward+0x1d6/0x22e
 [<b0239a62>] ip_rcv+0x405/0x483
 [<b02211ac>] netif_receive_skb+0x21d/0x25b
 [<b020d3c9>] netif_poll+0x59c/0x753
 [<b021fbf1>] net_rx_action+0xcd/0x1d9
 [<b011bcb1>] __do_softirq+0x73/0xf0
 [<b011bd6e>] do_softirq+0x40/0x64
 [<b0105f03>] do_IRQ+0x1f/0x28
 [<b0200fe3>] evtchn_do_upcall+0x60/0x96
 [<b01048b8>] hypervisor_callback+0x2c/0x34
 [<b0103416>] xen_idle+0x5e/0x7d
 [<b0103480>] cpu_idle+0x4b/0x60
 [<b03004b8>] start_kernel+0x31c/0x322

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

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>