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-users

Re: [Xen-users] Xen 3.1 clock problems

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Xen 3.1 clock problems
From: Tony Hoyle <tmh@xxxxxxxxxxxx>
Date: Wed, 30 May 2007 17:54:14 +0100
Delivery-date: Wed, 30 May 2007 09:52:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <907625E08839C4409CE5768403633E0B02561D7E@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <907625E08839C4409CE5768403633E0B02561D7E@xxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.10 (Windows/20070221)
Petersson, Mats wrote:
Sorry for not being more help here...
I've found on the domu I last rebooted it has a large number of the following:

May 30 01:43:42 wolf359 kernel: BUG: soft lockup detected on CPU#1!
May 30 01:43:42 wolf359 kernel:
May 30 01:43:42 wolf359 kernel: Call Trace:
May 30 01:43:42 wolf359 kernel:  <IRQ>  [<ffffffff8029ea86>] 
softlockup_tick+0xdb/0xed
May 30 01:43:42 wolf359 kernel:  [<ffffffff8027d9ae>] 
run_rebalance_domains+0x14a/0x3a7
May 30 01:43:42 wolf359 kernel:  [<ffffffff802663f5>] 
timer_interrupt+0x39c/0x3fa
May 30 01:43:42 wolf359 kernel:  [<ffffffff8021129c>] handle_IRQ_event+0x29/0x5b
May 30 01:43:42 wolf359 kernel:  [<ffffffff802a02ee>] 
handle_level_irq+0xae/0x100
May 30 01:43:42 wolf359 kernel:  [<ffffffff8025b21c>] call_softirq+0x1c/0x28
May 30 01:43:42 wolf359 kernel:  [<ffffffff80264c8b>] do_IRQ+0x64/0xcd
May 30 01:43:42 wolf359 kernel:  [<ffffffff803646f0>] evtchn_do_upcall+0x86/0xe0
May 30 01:43:42 wolf359 kernel:  [<ffffffff8025acfe>] 
do_hypervisor_callback+0x1e/0x30
May 30 01:43:42 wolf359 kernel:  <EOI>  [<ffffffff802063aa>] 
hypercall_page+0x3aa/0x1000
May 30 01:43:42 wolf359 kernel:  [<ffffffff802063aa>] 
hypercall_page+0x3aa/0x1000
May 30 01:43:42 wolf359 kernel:  [<ffffffff80265912>] raw_safe_halt+0x7f/0xa3
May 30 01:43:42 wolf359 kernel:  [<ffffffff80262c10>] xen_idle+0x34/0x4d
May 30 01:43:42 wolf359 kernel:  [<ffffffff80247858>] cpu_idle+0x89/0xac
May 30 01:43:42 wolf359 kernel:

Since rebooting this hasn't repeated and the time is back to normal.

The first one of these is possibly the source of the problem:

May 29 19:13:39 wolf359 dhclient: DHCPREQUEST on eth0 to 81.187.26.102 port 67
May 29 19:13:39 wolf359 dhclient: DHCPACK from 81.187.26.102
May 29 19:13:40 wolf359 dhclient: bound to 192.168.44.12 -- renewal in 300 
seconds.
May 29 19:14:31 wolf359 kernel: Breaking affinity for irq 260
May 29 19:14:31 wolf359 kernel: Breaking affinity for irq 261
May 29 19:14:31 wolf359 kernel: Breaking affinity for irq 262
May 29 16:53:23 wolf359 kernel: netfront: device eth0 has flipping receive path.
May 29 16:53:23 wolf359 kernel: netfront: device eth0 has flipping receive path.
May 29 16:53:23 wolf359 kernel: Initializing CPU#1
May 29 17:02:34 wolf359 kernel: BUG: soft lockup detected on CPU#1!
May 29 17:02:34 wolf359 kernel:
May 29 17:02:34 wolf359 kernel: Call Trace:
May 29 17:02:34 wolf359 kernel:  <IRQ>  [<ffffffff8029ea86>] 
softlockup_tick+0xdb/0xed
May 29 17:02:34 wolf359 kernel:  [<ffffffff8027d9ae>] 
run_rebalance_domains+0x14a/0x3a7
May 29 17:02:34 wolf359 kernel:  [<ffffffff802663f5>] 
timer_interrupt+0x39c/0x3fa
May 29 17:02:34 wolf359 kernel:  [<ffffffff8021129c>] handle_IRQ_event+0x29/0x5b
May 29 17:02:34 wolf359 kernel:  [<ffffffff802a02ee>] 
handle_level_irq+0xae/0x100
May 29 17:02:34 wolf359 kernel:  [<ffffffff8025b21c>] call_softirq+0x1c/0x28
May 29 17:02:34 wolf359 kernel:  [<ffffffff80264c8b>] do_IRQ+0x64/0xcd
May 29 17:02:34 wolf359 kernel:  [<ffffffff8025af6f>] child_rip+0x11/0x12
May 29 17:02:34 wolf359 kernel:  [<ffffffff803646f0>] evtchn_do_upcall+0x86/0xe0
May 29 17:02:34 wolf359 kernel:  [<ffffffff8025acfe>] 
do_hypervisor_callback+0x1e/0x30
May 29 17:02:34 wolf359 kernel:  <EOI>  [<ffffffff802063aa>] 
hypercall_page+0x3aa/0x1000
May 29 17:02:34 wolf359 kernel:  [<ffffffff802063aa>] 
hypercall_page+0x3aa/0x1000
May 29 17:02:34 wolf359 kernel:  [<ffffffff80265912>] raw_safe_halt+0x7f/0xa3
May 29 17:02:34 wolf359 kernel:  [<ffffffff80262c10>] xen_idle+0x34/0x4d
May 29 17:02:34 wolf359 kernel:  [<ffffffff80247858>] cpu_idle+0x89/0xac
May 29 17:02:34 wolf359 kernel:
May 29 17:17:01 wolf359 /USR/SBIN/CRON[2038]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
May 29 17:17:01 wolf359 kernel: BUG: soft lockup detected on CPU#1!

Tony

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