Bug#599089: linux-image-2.6.32-5-xen-686: Kernel Panics when using NFS from DomU to Dom0
On Tue, 2010-10-05 at 22:14 -0400, Jason Kendall wrote:
> Where do you guys commit? I didn't see it on the kernel git tree, and
> can't find a debian one.
Jeremy is the upstream xen kernel maintainer so he has put it in his
tree at git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
specifically
http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=7ed8586dd2ba2340a28a5d3d21f3f531a5bd30f8
I'm just about to pull it into the Debian kernel SVN
svn://svn.debian.org/kernel/dists/trunk/linux-2.6. From there it will go
into unstable/sid whenever 2.6.32-25 is uploaded and then it will
propagate to testing/squeeze some time after that in the usual way.
However once it is in unstable there should be nothing to stop you
installing the package on a squeeze system.
I don't control the upload to sid schedule I'm afraid so I can't really
say when it will happen. Perhaps someone on debian-kernel will chime in.
Ian.
> 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
> >
>
--
Ian Campbell
Friendships last when each friend thinks he has a slight superiority
over the other.
-- Honore DeBalzac
Reply to: