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


Re: [Xen-devel] Re: pvops kernel branches - 2.6.36 options, stable/next/

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: pvops kernel branches - 2.6.36 options, stable/next/etc?
From: Bruce Edge <bruce.edge@xxxxxxxxx>
Date: Thu, 11 Nov 2010 14:06:55 -0800
Cc: Boris Derzhavets <bderzhavets@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>, "ian.campbell@xxxxxxxxxx" <ian.campbell@xxxxxxxxxx>
Delivery-date: Thu, 11 Nov 2010 14:08:25 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=ky9SRFM1MgBRAG3iK3Ul5gWT8SWbvP+HgmzNuE0VPgE=; b=S9Qx/5J4qAHJY2cr/ZU/xPslQ9LP2Y0aIk61P87O2GsDlCl20LMwOxwxLWYawy2Bzr d7jTz0uk3/rfOf7qX8v6u1WTuKSHczrnm1EIaWg5Crlv0xHavcAdUjVifPibMLI+TkTC 5kxJ/B5km3RbdKtzwVFA1cPyn18+tV3cH7gXo=
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:content-transfer-encoding; b=DbrNZf0367RKXcTWd1ttyoudZifu8RsL1HdMZQ3sUFt5Xfbb4HhAOK8KEPU0LiFpj2 m/zSRUIWojgfO5b9/lzlvpYFHAI5/AJeyoCN57CnFqiLMXuyLUx++IlYZleEhNdfOs3F h7dAGsEOtoa69gKXkG0NeTfnmVYF8rtVPMXkQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20101111211147.GA15435@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTim_aB+d6eyipBNAP6UnmGECJbwBGGufiNfb7r-+@xxxxxxxxxxxxxx> <516589.45879.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <AANLkTimDgybuxiQcdNQ=6Hz1fVBP+aqS_SRD6p5Cab-U@xxxxxxxxxxxxxx> <20101111211147.GA15435@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Nov 11, 2010 at 1:11 PM, Konrad Rzeszutek Wilk
<konrad.wilk@xxxxxxxxxx> wrote:
> On Thu, Nov 11, 2010 at 12:20:25PM -0800, Bruce Edge wrote:
>> On Thu, Nov 11, 2010 at 12:03 PM, Boris Derzhavets 
>> <bderzhavets@xxxxxxxxx>wrote:
>> > Konrad,
>> >
>> > (mainline) works as PV DomU kernel ( at Xen 4.0.1 Dom0)  with NFS
>> > remote folder  with no issues. So,, 2.6.36 been built via 
>> > upstream
>> > source are OK. Seems  to be .37-rc1 bug
>> >
>> >
>> I agree. I reinstalled a 2.6.36 domU and am unable to get it to crash using
>> the same actions that reliably crashed the 2.6.37-rc1 domU.
>> Would it be worth bisecting the konrad-pcifront-2.6.32 branch to find which
>> it started failing?
> I think you meant another branch....but I don't believe the problem is related
> to the pcifront. Boris was able to trigger this without using the XenPCI 
> front.

Right, good point. I fell back to that branch as we'd been running OK
with it for a while.

> It might make more sense to bisect from 2.6.36 through 2.6.36-rc1 timeframe.

I'm assuming 37-rc1 not 36-rc1.

> During the merge window time when a lot of patches went in. It seems to point
> to network since that is how you guys are triggering it..
>> I think that 8029255fcc3a7925ad8ee9f5fdc0764b6662301e (on 10/24) was the
>> last good sync that I got.
> Ah, that would be the stable/xen-pcifront-0.8.1 tree. And it was based off
> v2.6.36-rc7. There is also the stable/xen-pcifront-0.8.2 tree
> (5bba6c56dc99ff88f79a79572e29ecf445710878) - which for some mysterious
> reasons on git.kernel.org was tracking the #master branch, so it ended up
> pointing to stable/xen-pcifront-fixes.. I fixed it, but that one 
> (xen-pcifront-0.8.2)
> is based on v2.6.36-rc6, so even older (that was required as it was based on 
> sparse_irq
> rework).

I'll look for it in the mainline.



Xen-devel mailing list