From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Knorr Subject: Re: [Xen-changelog] Fix NX/XD enable on secondary CPUs. Date: 13 Jul 2005 12:17:30 +0200 Message-ID: <87vf3fko1x.fsf@bytesex.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Xen patchbot -unstable writes: > Fix NX/XD enable on secondary CPUs. > Signed-off-by: Keir Fraser I think I have this problem with PAE as well. Machine is SMP (hyperthreaded). PAE dom0 boots fine on CPU #0. PAE domU is bound to CPU #1 by default and boots to the login prompt as well, but only with NX disabled (and network disabled, but that's another story ...). With NX-enabled domU boot I get this ... (XEN) (file=traps.c, line=872) Non-priv domain attempted RDMSR(c0000080,00000000,20100000). (XEN) (file=traps.c, line=864) Non-priv domain attempted WRMSR(c0000080,00000800,00000000). ... and the kernel crashes shortly later, I guess due to NX pte entry without NX being enabled on CPU #1. It crashes right after the first set_fixmap call which creates a pte entry with NX set. Gerd -- panic("it works"); /* avoid being flooded with debug messages */