From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luke S Crawford Subject: BUG: soft lockup detected on CPU#0! Date: 02 Aug 2010 18:54:54 -0400 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org so yeah, i've been getting these on both my amd G34 systems as well as my socket F (mcp55) systems. three times in as many months, all on different servers. relivant bits of xm info: xen_major : 3 xen_minor : 4 xen_extra : .3 this is with the xen.org 2.6.18 kernel that comes with 3.4.3 Call Trace: [] softlockup_tick+0xce/0xe0 [] timer_interrupt+0x3a8/0x402 [] handle_IRQ_event+0x4e/0x96 [] __do_IRQ+0xa4/0x105 [] do_IRQ+0x44/0x4d [] evtchn_do_upcall+0x19e/0x256 [] do_hypervisor_callback+0x1e/0x2c [] show_rd_sect+0x0/0x68 [] __read_lock_failed+0x8/0x14 [] get_device+0x17/0x20 [] .text.lock.spinlock+0x53/0x8a [] show_rd_sect+0x27/0x68 [] sysfs_read_file+0xa5/0x12c [] vfs_read+0xcb/0x171 [] sys_read+0x45/0x6e [] tracesys+0xab/0xb5 -- Luke S. Crawford http://prgmr.com/xen/ - Hosting for the technically adept http://nostarch.com/xen.htm - We don't assume you are stupid.