From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Xen dom0 crash in get_phys_to_machine Date: Fri, 12 Nov 2010 16:53:31 -0800 Message-ID: <4CDDE18B.204@goop.org> References: <19636.5260.149513.257699@wylie.me.uk> <19649.34780.401584.994309@wylie.me.uk> <4CDDC288.3000401@infinitumb.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4CDDC288.3000401@infinitumb.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: sven Cc: "Alan J. Wylie" , "xen-devel@lists.xensource.com" , Gianni Tedesco , Andreas Kinzler List-Id: xen-devel@lists.xenproject.org On 11/12/2010 02:41 PM, sven wrote: > is there any news regarding this problem? > > This evening I tried next-2.6.32 again, but still no luck. > > (..had the slight hope the recent changes about lowest-megabyte memory > area might have fixed this, too .. but ..) Sorry, I'd set it to one side while dealing with all the 2.6.37 upstreaming work. Unfortunately I don't have a machine which reproduces this problem, so I've been relying on other people's reports, and they haven't shown any smoking guns yet. But I have been seeing other odd things occasionally which could be the same problem in different guises, so I'll see if I can track those down. Thanks, J