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-users] On domU console, "BUG: soft lockup detected on CPU#1!"

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] On domU console, "BUG: soft lockup detected on CPU#1!"
From: "Sandor W. Sklar" <ssklar@xxxxxxxxxxxx>
Date: Thu, 17 Jul 2008 17:58:01 -0700
Delivery-date: Thu, 17 Jul 2008 18:00:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

I've got a number of RHEL5 PV domUs running on an RHEL5 x86_64 dom0. I had cause to connect to the domU consoles today, and on one of them, the below output had been written to the console 20-30 times.

  BUG: soft lockup detected on CPU#1!

  Call Trace:
   <IRQ>  [<ffffffff802aad55>] softlockup_tick+0xd5/0xe7
   [<ffffffff8026cb4a>] timer_interrupt+0x396/0x3f2
   [<ffffffff80210afe>] handle_IRQ_event+0x2d/0x60
   [<ffffffff802ab0dd>] __do_IRQ+0xa4/0x105
   [<ffffffff80288712>] _local_bh_enable+0x61/0xc5
   [<ffffffff8026a90e>] do_IRQ+0xe7/0xf5
   [<ffffffff8025db2b>] child_rip+0x11/0x12
   [<ffffffff80396944>] evtchn_do_upcall+0x86/0xe0
   [<ffffffff8025d8ce>] do_hypervisor_callback+0x1e/0x2c
   <EOI>  [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000
   [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000
   [<ffffffff8026be87>] raw_safe_halt+0x84/0xa8
   [<ffffffff80269453>] xen_idle+0x38/0x4a
   [<ffffffff80247ba9>] cpu_idle+0x97/0xba

This domU has an uptime of 84 days, and I've noticed no problems with its regular operation, so I'm wondering if this error block is just something to ignore, or if it might be indicative of a problem that needs further attention.

The domU config is:

  name = "lyberdev1"
  uuid = "344d9366-838b-661c-1ee7-886b97c54048"
  maxmem = 4096
  memory = 2048
  vcpus = 2
  bootloader = "/usr/bin/pygrub"
  on_poweroff = "destroy"
  on_reboot = "restart"
  on_crash = "restart"
  vfb = [  ]
  disk = [ "file:/var/lib/xen/images/lyberdev1-disk0,xvda,w"
    ,"file:/var/lib/xen/images/lyberdev1-disk1,xvdb,w" ]
  vif = [ "mac=00:16:3e:40:0a:88,bridge=xenbr2" ]

The kernel in the domU is 2.6.18-53.1.14.el5xen (rhel5); on the dom0, the kernel is 2.6.18-53.1.21.el5xen (also rhel5), and I've got xen-3.0.3-41.el5. The dom0 hardware is a Sun Fire X4200 M2 (2 x dual- core AMD CPUs), with 8 GB of RAM. I'll note that this doesn't appear on the console of any of the other domUs on the system.

I see a bunch of similar bug reports if I google around, but nothing definitive as to the cause, solution, or severity of this error message, so if someone has a suggestion, I'd really appreciate hearing it, thanks!


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] On domU console, "BUG: soft lockup detected on CPU#1!", Sandor W. Sklar <=