From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Lalancette Subject: Re: Re: [Xen-users] xen-3.0.3 occur kernel panic Date: Mon, 25 Feb 2008 11:01:55 -0500 Message-ID: <47C2E673.3050905@redhat.com> References: <47BB88CD.4040907@SierraAtlantic.com> <47BC6412.9010506@redhat.com> <47C2673B.2080108@SierraAtlantic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <47C2673B.2080108@SierraAtlantic.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: Wei Jiang Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Wei Jiang wrote: >>>From the kernel panic messages, I found that happened > at line 2245 of mm/memory.c > > 2244 pte_unmap(page_table); > * 2245 BUG_ON(vma->vm_flags & VM_PFNMAP);* > 2246 > 2247 if (vma->vm_file) { > > > As we can see, the kernel panic because the vm_flags in a *VM_PFNMAP* > > But why the vm_flags was set to VM_PFNMAP, If it is related to *APIC* ? Yes, Sadique is right. This bug was fixed in 5.1, and will be further refined in 5.2. Chris Lalancette