From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boris Derzhavets Subject: Re: Re: 2.6.37-rc1 mainline domU - BUG: unable to handle kernel paging request Date: Tue, 16 Nov 2010 12:50:14 -0800 (PST) Message-ID: <591702.71845.qm@web56107.mail.re3.yahoo.com> References: <20101116190043.GB11549@dumpdata.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2094207540==" Return-path: In-Reply-To: <20101116190043.GB11549@dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: Jeremy Fitzhardinge , xen-devel@lists.xensource.com, Bruce Edge List-Id: xen-devel@lists.xenproject.org --===============2094207540== Content-Type: multipart/alternative; boundary="0-1707061619-1289940614=:71845" --0-1707061619-1289940614=:71845 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sorry, typo. Correct :- The best results for 2.6.37-rc1-git8 + xen.next-2.6.37.patch +=0A xen.pcifr= ont.fixes.patch Boris. --- On Tue, 11/16/10, Konrad Rzeszutek Wilk wrote: From: Konrad Rzeszutek Wilk Subject: Re: [Xen-devel] Re: 2.6.37-rc1 mainline domU - BUG: unable to hand= le kernel paging request To: "Boris Derzhavets" Cc: "Jeremy Fitzhardinge" , xen-devel@lists.xensource.com,= "Bruce Edge" Date: Tuesday, November 16, 2010, 2:00 PM On Tue, Nov 16, 2010 at 10:43:49AM -0800, Boris Derzhavets wrote: > Today i've built vmlinuz-2.6.37-0.1.rc1.git8.xendom0.fc14.x86_64 > via Michael's http://koji.fedoraproject.org/koji/taskinfo?taskID=3D259843= 4 > and uncommented xen.pcifront.fixes.patch in kernel.spec, i.e. >=20 > # Xen patches > ApplyPatch xen.next-2.6.37.patch > # ApplyPatch xen.upstream.core.patch > ApplyPatch xen.pcifront.fixes.patch > # ApplyPatch xen.pvhvm.fixes.patch >=20 > as a fesult a got kernel wich runs pretty stable NFS client at Xen 4.0.1= =20 > F14 Dom0 (2.6.32.25-172.xendom0.fc14.x86_64). > =A0=20 > =A0 I was able several times copied from NFS folder F14's ISO image (3.2 = GB)=20 > to DomU and scp'ed it back and didn't get any kernel crashing on DomU. Huh. I .. what? I am confused. I thought we established that the issue was not related to Xen PCI front? You also seem to uncomment the upstream.core.patches and the xen.pvhvm.patch - why? >=20 > =A0On Ubuntu 10.04 this kernel may be built as 2.6.37-rc1&git8 patched vi= a > xen.next-2.6.37.patch > xen.pcifront.fixes.patch > All required upstream patches may be taken (as well as 2 above) > from=A0 http://koji.fedoraproject.org/koji/taskinfo?taskID=3D2598434 > =A0 I believe as soon as xen.pcifront.fixes.patch will be accepted by ups= tream > NFS client issue on F14 will be gone=20 Ok, they are.. v2.6.37-rc2 which came out today has the fixes. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel =0A=0A=0A --0-1707061619-1289940614=:71845 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable

Sorry, typo. Correct :-

The best resul= ts for 2.6.37-rc1-git8 + xen.next-2.6.37.patch +=0A xen.pcifront.fixes.patc= h

Boris.

--- On Tue, 11/16/10, Konrad Rzeszutek Wilk &l= t;konrad.wilk@oracle.com> wrote:

From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re:= [Xen-devel] Re: 2.6.37-rc1 mainline domU - BUG: unable to handle kernel pa= ging request
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc:= "Jeremy Fitzhardinge" <jeremy@goop.org>, xen-devel@lists.xensource.c= om, "Bruce Edge" <bruce.edge@gmail.com>
Date: Tuesday, November 16= , 2010, 2:00 PM

On Tue, Nov 16, 2010 at 10:= 43:49AM -0800, Boris Derzhavets wrote:
> Today i've built vmlinuz-2.6= .37-0.1.rc1.git8.xendom0.fc14.x86_64
> via Michael's http://koji.fedoraproject.org/koji/taskinfo?taskID=3D259= 8434
> and uncommented xen.pcifront.fixes.patch in kernel.spec, i= .e.
>
> # Xen patches
> ApplyPatch xen.next-2.6.37.patch=
> # ApplyPatch xen.upstream.core.patch
> ApplyPatch xen.pcifro= nt.fixes.patch
> # ApplyPatch xen.pvhvm.fixes.patch
>
> = as a fesult a got kernel wich runs pretty stable NFS client at Xen 4.0.1 > F14 Dom0 (2.6.32.25-172.xendom0.fc14.x86_64).
>
>= ; I was able several times copied from NFS folder F14's ISO image (3= .2 GB)
> to DomU and scp'ed it back and didn't get any kernel crashi= ng on DomU.

Huh. I .. what? I am confused. I thought we established = that the issue
was not related to Xen PCI front? You also seem to uncomm= ent the
upstream.core.patches and the xen.pvhvm.patch - why?

>=
> On Ubuntu 10.04 this kernel may be built as 2.6.37-rc1&git8 patched via
> xen.next-2.6.37.patch
> xen.= pcifront.fixes.patch
> All required upstream patches may be taken (as= well as 2 above)
> from http://koji.fedoraproj= ect.org/koji/taskinfo?taskID=3D2598434
> I believe as soon= as xen.pcifront.fixes.patch will be accepted by upstream
> NFS clien= t issue on F14 will be gone

Ok, they are.. v2.6.37-rc2 which came o= ut today has the fixes.

____________________________________________= ___
Xen-devel mailing list
Xen-devel= @lists.xensource.com
http://lists.xensource.com/xen-devel

=0A=0A --0-1707061619-1289940614=:71845-- --===============2094207540== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============2094207540==--