Xen project Mailing List

[Xen-users] Re: [Xen-devel] Kernel panic with 2.6.32-30 under network activity

From: Olivier Hanesse <olivier.hanesse@xxxxxxxxx>

Date: Thu, 17 Mar 2011 13:11:46 +0100

Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>

Delivery-date: Thu, 17 Mar 2011 05:13:34 -0700

Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=qM1Box4Kp1JoQlwCQ7jUY+5TX8YzNEWy04Qkizr5JcV2Zb6/3CqNdPldbmPITtrGfe u2Qw3z4CifmEidE3z9p2T6p+mkc/qKvU1tX28D+JLSQVjiwuxTb8bPzL1bNE98jM62w5 /3h4A10AQaTXsWbJivHZWTnirFfusiuCsB32k=

List-id: Xen user discussion <xen-users.lists.xensource.com>

2011/3/17 Jan Beulich <JBeulich@xxxxxxxxxx>

>>> On 17.03.11 at 11:34, Olivier Hanesse <olivier.hanesse@xxxxxxxxx> wrote:
> It happens again a few minutes ago. It is the same kernel stack each time
> (alignment check: 0000 [#1] SMP etc ...)
>
> The dom0 where all the faulty domU are running is a dual Xeon 5420 so 8 real
> cores available.
> 20 domUs are running on it, 35 vcpus are set up, is that too much ? The bug
> happens randomly on domUs
> I was running the same config with xen3.2 without any issue.

Are we to read this as "same kernels in DomU-s and Dom0"? If so,
that would hint at some subtle Xen regression. If not, you'd need
to be more precise as to what works and what doesn't, and would
possibly want to try intermediate versions to narrow when this
got introduced.

Dom0 et DomU are using different kernels (both coming from Debian repository, but same version)

domU :

ii linux-image-2.6.32-bpo.5-amd64 2.6.32-30~bpo50+1 Linux 2.6.32 for 64-bit PCs

dom0:

ii linux-image-2.6.32-bpo.5-xen-amd64 2.6.32-30~bpo50+1 Linux 2.6.32 for 64-bit PCs, Xen dom0 suppor

I was running Debian Lenny's version for xen 3.2, so it was 2.6.26

> I found this old post :
> http://lists.xensource.com/archives/html/xen-devel/2010-03/msg01561.html
>
> It may be related, no issue with 2.6.24, and issue with 2.6.32.

Yes, that indeed looks very similar. Nevertheless, without this
being generally reproducible, we'll have to rely on you doing
some analysis/debugging work on this.

I "pinned" all domUs cpus in order that they don't use the same cpu as dom0 (which is pinned to cpu0).

I can run any analysis/debugging tools you want.

I will also try an older kernel (for example 2.6.32-10) and see what happens.

Jan

Regards

Olivier

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