All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Boris Derzhavets <bderzhavets@yahoo.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	xen-devel@lists.xensource.com, Bruce Edge <bruce.edge@gmail.com>
Subject: Re: Re: 2.6.37-rc1 mainline domU - BUG: unable to handle kernel paging request
Date: Tue, 16 Nov 2010 14:00:43 -0500	[thread overview]
Message-ID: <20101116190043.GB11549@dumpdata.com> (raw)
In-Reply-To: <787641.21648.qm@web56106.mail.re3.yahoo.com>

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=2598434
> 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.pcifront.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 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?

> 
>  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.fedoraproject.org/koji/taskinfo?taskID=2598434
>   I believe as soon as xen.pcifront.fixes.patch will be accepted by upstream
> NFS client issue on F14 will be gone 

Ok, they are.. v2.6.37-rc2 which came out today has the fixes.

  reply	other threads:[~2010-11-16 19:00 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10 22:15 2.6.37-rc1 mainline domU - BUG: unable to handle kernel paging request Bruce Edge
2010-11-10 22:30 ` Bruce Edge
2010-11-10 23:03   ` Bruce Edge
2010-11-11 15:56     ` Konrad Rzeszutek Wilk
2010-11-11 16:32       ` Boris Derzhavets
2010-11-11  6:13   ` Bruce Edge
2010-11-11 12:01   ` Boris Derzhavets
2010-11-11 12:08     ` Boris Derzhavets
2010-11-11 16:09       ` Konrad Rzeszutek Wilk
2010-11-11 16:29         ` Boris Derzhavets
2010-11-11 16:46           ` Konrad Rzeszutek Wilk
2010-11-11 16:53             ` Boris Derzhavets
2010-11-12 14:40               ` Bruce Edge
2010-11-12 16:06                 ` Boris Derzhavets
2010-11-13  8:37                   ` Boris Derzhavets
2010-11-12 16:27                 ` Sander Eikelenboom
2010-11-12 17:01                   ` Konrad Rzeszutek Wilk
2010-11-14 16:37                     ` Boris Derzhavets
2010-11-14 16:56                       ` Sander Eikelenboom
2010-11-14 17:09                         ` Boris Derzhavets
2010-11-14 17:19                           ` Sander Eikelenboom
2010-11-14 21:35                         ` Bruce Edge
2010-11-15  8:06                           ` Boris Derzhavets
2010-11-15 11:05                             ` Boris Derzhavets
2010-11-15 14:48                           ` Re: 2.6.37-rc1 mainline domU - BUG: unable to handle kernel paging request, nfsd changes for 2.6.37 Boris Derzhavets
2010-11-15 17:14                           ` Re: 2.6.37-rc1 mainline domU - BUG: unable to handle kernel paging request as Dom0 kernel Boris Derzhavets
2010-11-15 20:21                         ` Re: 2.6.37-rc1 mainline domU - BUG: unable to handle kernel paging request Bruce Edge
2010-11-15 20:32                           ` Sander Eikelenboom
2010-11-16 18:43                           ` Boris Derzhavets
2010-11-16 19:00                             ` Konrad Rzeszutek Wilk [this message]
2010-11-16 20:43                               ` Boris Derzhavets
2010-11-16 21:15                                 ` Konrad Rzeszutek Wilk
2010-11-16 21:42                                   ` Boris Derzhavets
2010-11-16 21:49                                   ` Boris Derzhavets
2010-11-17 21:28                                     ` Bruce Edge
2010-11-16 20:50                               ` Boris Derzhavets
2010-11-11 16:46         ` Boris Derzhavets
2010-11-11 12:26     ` Boris Derzhavets
2010-11-11 15:08   ` Bruce Edge
2010-11-10 22:39 ` Konrad Rzeszutek Wilk
2010-11-10 22:50 ` M A Young
2010-11-10 22:51 ` Sander Eikelenboom
2010-11-11 11:01 ` Boris Derzhavets
2010-11-11 14:50   ` Bruce Edge
2010-11-11 15:06     ` Boris Derzhavets
2010-11-14 17:47 Boris Derzhavets
2010-11-14 17:52 ` Sander Eikelenboom
2010-11-16 19:20 Boris Derzhavets
2010-11-18 10:34 Boris Derzhavets
2010-11-18 16:40 ` Bruce Edge
2010-11-18 17:05   ` Boris Derzhavets
2010-11-18 20:05     ` Bruce Edge
2010-11-19  7:12       ` Boris Derzhavets
2010-11-19 18:16         ` Bruce Edge
2010-11-19 18:52           ` Boris Derzhavets
     [not found]           ` <697216.62238.qm@web56104.mail.re3.yahoo.com>
2010-12-01 21:32             ` Bruce Edge
2010-12-02  6:33               ` Jeremy Fitzhardinge
2010-12-02  8:33                 ` Boris Derzhavets
2010-12-02 14:41                 ` Bruce Edge
2010-12-02 18:05                   ` Bruce Edge
2010-12-02 18:28                     ` Jeremy Fitzhardinge
2010-12-02 18:38                       ` Bruce Edge
2010-12-02 18:50                         ` Jeremy Fitzhardinge
2010-12-02 19:34                           ` Bruce Edge
2010-11-19 14:32     ` Boris Derzhavets

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=20101116190043.GB11549@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=bderzhavets@yahoo.com \
    --cc=bruce.edge@gmail.com \
    --cc=jeremy@goop.org \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.