From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Edge Subject: Re: Re: 2.6.37-rc1 mainline domU - BUG: unable to handle kernel paging request Date: Thu, 2 Dec 2010 10:38:46 -0800 Message-ID: References: <697216.62238.qm@web56104.mail.re3.yahoo.com> <4CF73DCF.4010200@goop.org> <4CF7E558.3010206@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4CF7E558.3010206@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: Boris Derzhavets , xen-devel@lists.xensource.com, Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On Thu, Dec 2, 2010 at 10:28 AM, Jeremy Fitzhardinge wrot= e: > On 12/02/2010 10:05 AM, Bruce Edge wrote: >> On Thu, Dec 2, 2010 at 6:41 AM, Bruce Edge wrote: >>> >>> On Wed, Dec 1, 2010 at 10:33 PM, Jeremy Fitzhardinge >>> wrote: >>>> On 12/01/2010 01:32 PM, Bruce Edge wrote: >>>>> I just checked the recently released 2.6.73-rc4, >>>> Do you mean mainline 2.6.37-rc4, or the one in xen/next-2.6.37? >>> mainline >>> >>>>> =A0and while the BUG >>>>> signature is different, it still fails under NFS accesses. This is >>>>> 100% recreatable. >>>> Please try this patch which is queued up for mainline. =A0It's already= in >>>> xen/next-2.6.37. >>> After testing the mainline .37 I also tried xen/next-2.6.37 with the sa= me >>> result. At least, I still hit a BUG after accessing an NFS mount. I did= n't >>> compare the stack, but the BUG condition looked the same. >>> I'll reconfirm the location and traceback of the xen/next kernel. >>> >>> -Bruce >>> >>> >> I re-ran the test with xen/next-2.6.37. The fault was a bit different th= is time. >> The dom0 started spewing these as the domU appeared to hang: > > OK, these look like exactly the sort of symptoms which should be fixed > by that patch, so assuming you're actually running the right kernel > (worth checking! =A0I get bitten by this occasionally), there's something > else going on here. You're right, my branch was a day out of date. I didn't have the last changes to: arch/x86/xen/grant-table.c | 28 +++++--- arch/x86/xen/mmu.c | 124 ++++++++++-------------------- include/linux/mm.h | 6 ++ include/linux/vmalloc.h | 2 - mm/memory.c | 56 ++++++++++---- mm/vmalloc.c | 182 ++++++++++++++--------------------------= ---- rebuilding with great expectations now :-) -Bruce > > What NFS version are you using, and other parameters? =A0What is the NFS > server? =A0What's the file access pattern going on? > > Thanks, > =A0 =A0J >