From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [Xen-users] 2.6.23 oops Date: Fri, 12 Oct 2007 08:30:57 -0700 Message-ID: <470F9331.4030500@goop.org> References: <20071011144817.n5x1drwcgug44sg0@whitelist.dk> <200710111629.05457.mark.williamson@cl.cam.ac.uk> <470E5248.1070502@goop.org> <20071011210001.cpd3whfy5ogwkwwc@whitelist.dk> <470E8FE8.6050908@goop.org> <20071011232116.e28c5kuo64o5woow@whitelist.dk> <470E99E2.7070300@goop.org> <20071012114600.6agb26rjo0tcgg8w@whitelist.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20071012114600.6agb26rjo0tcgg8w@whitelist.dk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-15?Q?Morten_B=F8geskov?= Cc: xen-devel@lists.xensource.com, Mark Williamson List-Id: xen-devel@lists.xenproject.org Morten B=F8geskov wrote: > New compiled xen-3.1.1-rc3 PAE, 2.6.18-xen (domU) PAE & > 2.6.23 PAE (config included) Still no difference. I just realized I hadn't been reading your backtrace closely enough, since it looks similar to the bug I'd been working on. Turns out having an xfs rootfs is what triggers your bug - I can repro it now, so I'll see if I can work out what's going on. BTW, did last night's little patch help with the UP time issue? J