From mboxrd@z Thu Jan 1 00:00:00 1970 From: Iustin Pop Subject: Re: 100% reliable Oops on xen 4.0.1 Date: Tue, 14 Aug 2012 11:12:52 +0200 Message-ID: <20120814091251.GS11580@google.com> References: <502A28130200007800094ADE@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <502A28130200007800094ADE@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Peter Moody , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Tue, Aug 14, 2012 at 09:27:31AM +0100, Jan Beulich wrote: > >>> On 14.08.12 at 02:03, Peter Moody wrote: > > I'm not sure what you need from the domU. It's running 2.6.38.8 (but > > I've seen this bug all the way up to 3.5.0-rc7, the latest I've > > tested). It's a fairly beefy setup, 32G memory and 6 cpus. > > Are these kernel versions refer to plain upstream ones? They are mostly Ubuntu kernels, so not vanilla. > > Is the subject referring to 4.0.1 in any way meaningful? I.e. > does the problem not occur with other Xen versions? I believe this was only related to the version we run, not that it's fixed in other Xen version. We will try to test with newer Xens to see. regards, iustin