From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Xen-unstable panic: FATAL PAGE FAULT Date: Mon, 30 Aug 2010 10:02:05 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: MaoXiaoyun , xen devel List-Id: xen-devel@lists.xenproject.org On 30/08/2010 09:47, "MaoXiaoyun" wrote: > 3) Every panic pointer to the same address: ffff8315ffffffe4, which is > not a valid page address. > I printted pages of the domain in assign_pages, which all looks like > ffff82f60bd64000, at least > ffff82f60 is the same. Yes, well you may not be crashing on a supposed page address. Certainly the page pointer that relinquish_memory() is working on, and passed to put_page->free_domheap_pages is valid enough to not cause any of those functions to crash when dereferencing it. At the moment you really have no idea what is causing free_heap_pages() to crash. > A bit of lost direction to go further. Thanks. You need to find out which line of code in free_heap_pages() is crashing, and what variable it is trying to dereference when it crashes. You have a nice backtrace with an EIP value, so you can 'objdump -d xen-syms' and search for the EIP in the disassembly. If you have a debug build of Xen you can even do 'objdump -S xen-syms' and have the disassembly annotated with corresponding source lines. Have you seen this on more than one physical machine? If not, have you run memtest on the offending machine? -- Keir