From: "Andres Lagar-Cavilla" <andres@lagarcavilla.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
"jingsu@gridcentric.ca" <jingsu@gridcentric.ca>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: BUG: soft lockup - CPU#0 stuck for 61s!
Date: Thu, 29 Mar 2012 09:51:47 -0700 [thread overview]
Message-ID: <f69bda01bb91884260e03a96e20a8667.squirrel@webmail.lagarcavilla.org> (raw)
In-Reply-To: <1333038715.18810.84.camel@zakaz.uk.xensource.com>
> On Thu, 2012-03-29 at 16:43 +0100, Andres Lagar-Cavilla wrote:
>> Ian,
>>
>> I came across the subject line on a 96GB server with over 85 VMs
>> running.
>> Completely frozen and unresponsive, qemu-dm processes hung on event
>> channels. I'm using the XenServer 6.0 dom0 kernel on top of the
>> xen-unstable tip hypervisor.
>>
>> I believe you solved the issue backporting some event channel patches to
>> the 2.6.32 kernel, as described in this thread
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638172
>>
>> I am missing a bit of context in order to retrieve the patches and apply
>> them to my setup. What trees are involved here?
>
> This was a backport to a 2.6.32 pvops kernel. The Debian Squeeze kernel
> is a snapshot from Jeremy's xen.git at some point in the past.
> drivers/xen/events.c is pretty different to the classic-Xen kernels like
> XenServers.
>
>> I'm looking in particular
>> for "multiple fixes to PIRQ event channel handling" and friends, but I
>> don't have commit identifiers, nor a tree URL (neither I am too sure
>> what
>> changesets from which upstream tree do the backports aggregate).
>
> I think the pirq stuff was because the aforementioned snapshot happened
> to be taken in the middle of a transition in how pirqs were handled, so
> I was back porting the remainder.
>
> Anyway, if you want them you can find them in the Debian source
> package, they are listed in debian/patches/series/40-extra, the paths
> there are relative to debian/patches.
>
> Also, I think (but I'm not 100% sure any more) that these patches
> correspond to this branch in my xenbits tree:
>
> git://xenbits.xen.org/people/ianc/linux-2.6.git debian/squeeze/evtchn
>
Thanks very much, this will get me going
Andres
> Ian
>
>
prev parent reply other threads:[~2012-03-29 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 15:43 BUG: soft lockup - CPU#0 stuck for 61s! Andres Lagar-Cavilla
2012-03-29 16:31 ` Ian Campbell
2012-03-29 16:51 ` Andres Lagar-Cavilla [this message]
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=f69bda01bb91884260e03a96e20a8667.squirrel@webmail.lagarcavilla.org \
--to=andres@lagarcavilla.org \
--cc=Ian.Campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jingsu@gridcentric.ca \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xen.org \
/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).