Re: Subject: Re: port-xen/45975: panic: HYPERVISOR_mmu_update failed, ret: -22 on -current MP domU (amd64)

[Greg Oster <oster%cs.usask.ca@localhost>]

The following reply was made to PR port-xen/45975; it has been noted by GNATS.

From: Greg Oster <oster%cs.usask.ca@localhost>
To: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
Cc: gnats-bugs%NetBSD.org@localhost, gnats-admin%NetBSD.org@localhost, 
netbsd-bugs%NetBSD.org@localhost,
 riz%NetBSD.org@localhost
Subject: Re: Subject: Re: port-xen/45975: panic: HYPERVISOR_mmu_update
 failed, ret: -22 on -current MP domU (amd64)
Date: Tue, 14 Feb 2012 15:08:42 -0600

 On Tue, 14 Feb 2012 22:02:43 +0100
 Manuel Bouyer <bouyer%antioche.eu.org@localhost> wrote:
 
 > On Tue, Feb 14, 2012 at 02:58:15PM -0600, Greg Oster wrote:
 > > 
 [snip]
 > > 
 > > relevant bits of 'xm dmesg' looks like:
 > > 
 > > (XEN) domain.c:509:d9 Attempt to change CR4 flags 00002620 ->
 > > 00000620 (XEN) domain.c:509:d9 Attempt to change CR4 flags 00002620
 > > -> 00000620 (XEN) domain.c:509:d9 Attempt to change CR4 flags
 > > 00002620 -> 00000620 (XEN) mm.c:2012:d9 Bad type (saw
 > > 00000000e8000001 != exp 0000000020000000) for mfn 190e00 (pfn
 > > 59a5b) (XEN) mm.c:745:d9 Attempt to create linear p.t. with write
 > > perms
 > > 
 > > If you need more info, just let me know... (this is a test vm, so
 > > can be killed at will/on demand..)
 > 
 > Yes, that's the same problem. Is it with i386 or amd64 ?
 
 amd64 (on a Q6600 Intel box)
 
 Later...
 
 Greg Oster