[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] DomU error on Debian Etch-amd64 softlockup_tick+timer_interrupt


  • To: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Remigiusz Stachura" <remigiusz.stachura@xxxxxxxxx>
  • Date: Wed, 29 Aug 2007 21:30:26 +0200
  • Delivery-date: Thu, 30 Aug 2007 02:52:36 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=AUufx7eLVw33DkNeuGwSo7725lTDvLQiEzjYrEfx8nWYCK9EeFMIfIVH5WyTBdyUUdv34fhKw7UGU+gFhCMp3nCr5MUX0Pm78MRlQkZE2WOM7+2clfVWoFquKtx6ZL/k+YqiYZ+VkVYlDp2X4rvqVNsgKJZAekWPMAGaV/QAVdk=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello,
I am using standard Debian Etch 4.0r1 with standard kernel
2.6.18.dfsg.1-13etch1 (2.6.18-5-xen-amd64) on HP DL 380 G5 server.
>From time to time on DomU in PV mode I get this eror:

Aug 29 14:16:01 tr2 kernel:
Aug 29 14:16:01 tr2 kernel: Call Trace:
Aug 29 14:16:01 tr2 kernel: <IRQ> [<ffffffff8029fb35>] softlockup_tick+0xdb/0xed
Aug 29 14:16:01 tr2 kernel: [<ffffffff80267d5a>] timer_interrupt+0x38d/0x3db
Aug 29 14:16:01 tr2 kernel: [<ffffffff80211154>] handle_IRQ_event+0x2d/0x60
Aug 29 14:16:01 tr2 kernel: [<ffffffff8029fe74>] __do_IRQ+0xa4/0x105
Aug 29 14:16:01 tr2 kernel: [<ffffffff802835f0>] _local_bh_enable+0x59/0xb3
Aug 29 14:16:01 tr2 kernel: [<ffffffff80266556>] do_IRQ+0x65/0x73
Aug 29 14:16:01 tr2 kernel: [<ffffffff80360ed6>] evtchn_do_upcall+0x86/0xe0
Aug 29 14:16:01 tr2 kernel: [<ffffffff8025c586>]
do_hypervisor_callback+0x1e/0x2c
Aug 29 14:16:01 tr2 kernel: <EOI> [<ffffffff802063aa>]
hypercall_page+0x3aa/0x1000
Aug 29 14:16:01 tr2 kernel: [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000
Aug 29 14:16:01 tr2 kernel: [<ffffffff802672d6>] raw_safe_halt+0x84/0xa8
Aug 29 14:16:01 tr2 kernel: [<ffffffff80264559>] xen_idle+0x38/0x4a
Aug 29 14:16:01 tr2 kernel: [<ffffffff802487a1>] cpu_idle+0x97/0xba
Aug 29 14:16:01 tr2 kernel:

My VM config:

ostype="debian"
name="tr2"
memory=8192
cpus=""
vcpus=4
uuid="768c60ca-7182-2341-2c1b-68afe1b1125d"
on_crash="restart"
on_poweroff="destroy"
on_reboot="restart"
localtime=1
builder="linux"
kernel = "/boot/xen/vmlinuz-xen"
ramdisk = "/boot/xen/initrd-xen"
root = "/dev/xvda1 ro"
extra="elevator=cfq"
disk=[ 'phy:/dev/drbd0,xvda1,w',
'phy:/dev/drbd1,xvdb1,w','phy:/dev/drbd2,xvdc1,w','phy:/dev/drbd3,xvdd1,w',
'phy:/dev/cciss/c0d0p8,xvde1,w',]
vif = [ 'mac=00:16:3e:35:96:5a, bridge=xenbr0', ]
acpi=1

I have red this is well known bug but I don't know what it may cause.
What is the reason of this bug and what should I do to eliminate it?

Thanks in advance
R.S.

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.