xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: prickett233 <prickett233@hotmail.com>
To: xen-devel@lists.xensource.com
Subject: Re: Dom0 panic on xen 3.4.3
Date: Mon, 27 Dec 2010 16:50:04 -0800 (PST)	[thread overview]
Message-ID: <1293497404863-3319865.post@n5.nabble.com> (raw)
In-Reply-To: <4CCE9662.5040600@redhat.com>


We also experience this same problem with the dom0 crashing when multiple
domU's are starting up at the same time.  Our setup consists of a dual pair
CentOS 5.5 running LVM/DRBD/Xen and have tried the default EL Xen version
3.0.3-105 including other newer versions (3.4.0 and 3.4.3) from the GITCO
repo [ http://www.gitco.de/repo/ ] with the crashing still occurring
independent of Xen version.

>From the kernel crash output we found a related post here [
http://lists.linbit.com/pipermail/drbd-user/2009-March/011652.html ] that
discusses a problem with I/O and network interface affecting DRBD.  By
turning off scatter/gather on the dom0's network interface we no longer
experience crashes in the dom0.

We came across this crashing issue when migrating our Xen VM's to newer
servers, but when running on our older servers the dom0 did not crash.  As
this issue appears to be related to the network driver/chipset, for the
record and hopefully our results will be useful to others,  the difference
between these servers NIC is;

----

Old servers (CentOS 5.3)  without dom0 crashing, uses tg3 network driver:

$ uname -a
Linux ldx12020 2.6.18-128.4.1.el5xen #1 SMP Tue Aug 4 20:51:12 EDT 2009
x86_64 x86_64 x86_64 GNU/Linux

$ lspci
03:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5722 Gigabit
Ethernet PCI Express
04:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5722 Gigabit
Ethernet PCI Express

$ ethtool -i eth0
driver: tg3
version: 3.93
firmware-version: 5722-v3.07, ASFIPMI v6.02
bus-info: 0000:03:00.0

----
 
New servers with dom0 crashing, uses bnx2 network driver:

$ uname -a
Linux tnx176 2.6.18-194.26.1.el5xen #1 SMP Tue Nov 9 13:35:30 EST 2010
x86_64 x86_64 x86_64 GNU/Linux

$ lspci
01:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709
Gigabit Ethernet (rev 20)
01:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709
Gigabit Ethernet (rev 20)
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709
Gigabit Ethernet (rev 20)
02:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709
Gigabit Ethernet (rev 20)

$ ethtool -i eth0
Cannot get driver information: Operation not supported

dmesg output: Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.0.2 (Aug
21, 2009)

----

Hopefully we can see this bug fixed.


Cheers,
Paul
-- 
View this message in context: http://xen.1045712.n5.nabble.com/Dom0-panic-on-xen-3-4-3-tp2642628p3319865.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

  reply	other threads:[~2010-12-28  0:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-20 18:15 Dom0 panic on xen 3.4.3 Cris Daniluk
2010-08-20 23:59 ` Pasi Kärkkäinen
2010-08-21  0:20   ` Cris Daniluk
2010-08-21 10:12     ` Pasi Kärkkäinen
2010-08-21 22:27       ` Cris Daniluk
2010-11-01 10:28         ` Paolo Bonzini
2010-12-28  0:50           ` prickett233 [this message]
2010-12-28 10:38             ` Pasi Kärkkäinen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1293497404863-3319865.post@n5.nabble.com \
    --to=prickett233@hotmail.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).