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

[Xen-users] BUG: soft lockup detected on CPU#0

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] BUG: soft lockup detected on CPU#0
From: Steven Timm <timm@xxxxxxxx>
Date: Wed, 16 Jan 2008 09:28:21 -0600 (CST)
Delivery-date: Wed, 16 Jan 2008 07:32:13 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

In the past few weeks I have been seeing the following
error message in my Dom0 several times a day.
It does not lead to the crash of anything.  A second server,
same hardware and identically configured, doesn't give this error.

This is Xen 3.1.0 as downloaded from the tarballs of xen.org
and running on top of RHEL 5.1.

BUG: soft lockup detected on CPU#0!

Call Trace:
 <IRQ> [<ffffffff80258269>] softlockup_tick+0xcc/0xde
 [<ffffffff8020e84d>] timer_interrupt+0x3a3/0x401
 [<ffffffff80258898>] handle_IRQ_event+0x4b/0x93
 [<ffffffff8025897e>] __do_IRQ+0x9e/0x100
 [<ffffffff8020cc97>] do_IRQ+0x63/0x71
 [<ffffffff8034b347>] evtchn_do_upcall+0xee/0x165
 [<ffffffff8020abca>] do_hypervisor_callback+0x1e/0x2c
 <EOI> [<ffffffff8020622a>] hypercall_page+0x22a/0x1000
 [<ffffffff8020622a>] hypercall_page+0x22a/0x1000
 [<ffffffff8034b258>] force_evtchn_callback+0xa/0xb
 [<ffffffff803f2272>] thread_return+0xdf/0x119
 [<ffffffff8020622a>] hypercall_page+0x22a/0x1000
 [<ffffffff80228a25>] __cond_resched+0x1c/0x44
 [<ffffffff803f25df>] cond_resched+0x37/0x42
 [<ffffffff802343c4>] ksoftirqd+0x0/0xbf
 [<ffffffff80234432>] ksoftirqd+0x6e/0xbf
 [<ffffffff802422d7>] kthread+0xc8/0xf1
 [<ffffffff8020ae1c>] child_rip+0xa/0x12
 [<ffffffff8024220f>] kthread+0x0/0xf1
 [<ffffffff8020ae12>] child_rip+0x0/0x12

In addition I am also seeing the following on the serial console of the machine (not at the same time):

<Jan/16 05:01 am>(XEN) mm.c:612:d1 Non-privileged (1) attempt to map I/O space 0

Any idea where this is coming from and how to fix it, would be helpful.

Steve Timm



--
------------------------------------------------------------------
Steven C. Timm, Ph.D  (630) 840-8525
timm@xxxxxxxx  http://home.fnal.gov/~timm/
Fermilab Computing Division, Scientific Computing Facilities,
Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.

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

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