WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: Bug#599089: linux-image-2.6.32-5-xen-686: Kernel Panics

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: [Xen-devel] Re: Bug#599089: linux-image-2.6.32-5-xen-686: Kernel Panics when using NFS from DomU to Dom0
From: Jason Kendall <jakendall@xxxxxxxxx>
Date: Tue, 05 Oct 2010 22:14:07 -0400
Cc: 599089@xxxxxxxxxxxxxxx, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Arnd Hannemann <hannemann@xxxxxxxxxxxxxxxxxxx>, Ian Campbell <ijc@xxxxxxxxxxxxxx>
Delivery-date: Fri, 08 Oct 2010 09:10:57 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=Qa4rYko5R8fAFClEtioly0MEpX2K0SVGn/Hb08CNuUM=; b=VMzTs+KMqsU7sFsUoaCbSpr2rXpBRIzqv8G16Qfu5IMs6sosCo3hscMQSXPNP/yPeD mSfqw3tL9TNDZUbQ1FUTsQ6QadzQyqnJyFO/T4pz9QRz8+klswhg+oXDntkHO0y3YdE8 NezD47ruGmj1yQfKR/zO9pvoFexScJkipH+Zg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=hK9lomnItNy30XP/dHbrsJ/+xyuiSW4dX887dni+r8pjsL0Dl1TNgxCgVQDaz0FmHA pNbLyyBvAqkRBeo2Yv70gdXPXsQSHrM5vFwks35wpsSpEUxsAVx0NiP3jPsWQZANrI6I 1a332vWVRSXAykZpq9DXn0VF4Gqz2f6Y/o0f0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4CABA91B.5020403@xxxxxxxx>
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: <4CA9EF03.20407@xxxxxxxxx> <1286272060.23155.7508.camel@xxxxxxxxxxxxxxxxxxxxxx> <1286272348.23155.7527.camel@xxxxxxxxxxxxxxxxxxxxxx> <4CAB584A.7090909@xxxxxxxx> <1286302967.10974.1.camel@xxxxxxxxxxxxxxxxxxxxx> <4CABA91B.5020403@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.11) Gecko/20100713 Thunderbird/3.0.6
Where do you guys commit? I didn't see it on the kernel git tree, and can't find a debian one.

Would this happen to make it into Squeeze soon? ETA?

Save me the trouble of a recompile :)

Cheers,
Jay


On 10-10-05 06:39 PM, Jeremy Fitzhardinge wrote:
  On 10/05/2010 11:22 AM, Ian Campbell wrote:
On Tue, 2010-10-05 at 09:54 -0700, Jeremy Fitzhardinge wrote:
On 10/05/2010 02:52 AM, Ian Campbell wrote:
On Tue, 2010-10-05 at 10:47 +0100, Ian Campbell wrote:
In addition to the kernel logging of the error I get this from the
hypervisor:
(XEN) mm.c:2062:d0 Error pfn 16d99: rd=ffff83011fefa000,
od=0000000000000000, caf=180000000000000, taf=0000000000000000
(XEN) mm.c:658:d0 Could not get page ref for pfn 16d99
(XEN) mm.c:3621:d0 Could not get page for mach->phys update
Adding a bit more logging to the kernel I get:
gnttb_copy_grant_page old c22ebcd8 P:0x1ec8e M:0xc499d F:0x41000000
gnttb_copy_grant_page new c2324ce0 P:0x1fe18 M:0x11cd32 F:0x40000000
(XEN) mm.c:2062:d0 Error pfn 1cd32: rd=ffff83011fefa000, od=0000000000000000, 
caf=180000000000000, taf=0000000000000000
(XEN) mm.c:658:d0 Could not get page ref for pfn 1cd32
(XEN) mm.c:3621:d0 Could not get page for mach->phys update

Notice how MFN 0x11cd32 has become 0x1cd32 by the time it gets to the
hypervisor!
Oy, more of these.  It might be better to use PFN_PHYS().
I thought there ought to be a helper but couldn't find one, PFN_PHYS
sounds like a good bet, unless we want to alias it as MFN_MACH or
something?
Doesn't really seem worth it, unless phys_addr_t ends up not being large
enough for a machine address.  But I think we rely on that pretty
heavily anyway.

I've committed it with that change.

     J

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