From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Re: [pv_ops domU] 2.6.30.5 - unable to handle kernel paging request / refresh_cpu_vm_stats / vmstat_update Date: Thu, 20 Aug 2009 17:38:52 -0700 Message-ID: <4A8DEC9C.50207@goop.org> References: <4A89F539.2070801@theshore.net> <4A8A2E74.9010202@goop.org> <4A8AB7B8.4070905@theshore.net> <4A8B0BD2.2060304@goop.org> <4A8D9FC7.7070101@linode.com> <4A8DDCEF.9020303@goop.org> <4A8DE6B7.7060001@linode.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4A8DE6B7.7060001@linode.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: Jed Smith Cc: xen devel , Keir Fraser List-Id: xen-devel@lists.xenproject.org On 08/20/09 17:13, Jed Smith wrote: > Jeremy Fitzhardinge wrote: > >> I see your bisect tested c47c1b1f3a9 as OK, so try e4d0407185. >> > jsmith@lindev7:~/linux-2.6$ git reset --hard e4d0407185 > HEAD is now at e4d0407 xen: use direct ops on 64-bit > > http://lateralus.jedsmith.org/Jeremy1/ > > Fails as before there. I bisected using that commit as the right side > before, but most of the kernels I built failed to boot before the first > printk(); I wasn't sure if there was something environmental going on. > Yes, there's a lot of stuff on that line which will not bisect well; there were substantial changes to percpu data handling, and a change to some of the core pvops calling conventions. It will take care to choose good bisection points to narrow things down. But it also sounds like it could be on the Xen side. Would it be possible to try and narrow down where Xen stops breaking? J