Re: [Xen-users] Linux 2.3.23-rc3 on Xen 3.1 fails in xen_write_cr4

[Bastian Blank <bastian@xxxxxxxxxxxx>]

On Sat, Aug 25, 2007 at 05:46:18PM +0200, Bastian Blank wrote:
> Any suggestions? It seems that some parts of the kernel wants to mess
> with CR4. Is it the MCE support?

After disabling the MCE support, the kernel crashs:
| (XEN) domain_crash_sync called from entry.S (ff16f829)
| (XEN) Domain 1 (vcpu#0) crashed on cpu#0:
| (XEN) ----[ Xen-3.1.0  x86_32p  debug=n  Not tainted ]----
| (XEN) CPU:    0
| (XEN) EIP:    0061:[<c0107a20>]
| (XEN) EFLAGS: 00010286   CONTEXT: guest
| (XEN) eax: 00010061   ebx: 00010061   ecx: c027ac8c   edx: 0000000d
| (XEN) esi: ffffffff   edi: 00000000   ebp: 00000020   esp: c004000c
| (XEN) cr0: 80050033   cr4: 000006f0   cr3: 0bd89000   cr2: 00010061
| (XEN) ds: 007b   es: 007b   fs: 00d8   gs: 0000   ss: e021   cs: 0061
| (XEN) Guest stack trace from esp=c004000c:
| (XEN)    c027abd0 00010061 00010086 00000002 c0107a20 00010061 00010086 
c027abd0
| (XEN)    00010061 00010086 00000002 c0107a20 00010061 00010086 c027abd0 
00010061
| (XEN)    00010086 00000002 c0107a20 00010061 00010086 c027abd0 00010061 
00010086
| (XEN)    00000002 c0107a20 00010061 00010086 c027abd0 00010061 00010086 
00000002
| (XEN)    c0107a20 00010061 00010086 c027abd0 00010061 00010086 00000002 
c0107a20
| (XEN)    00010061 00010086 c027abd0 00010061 00010086 00000002 c0107a20 
00010061
| (XEN)    00010086 c027abd0 00010061 00010086 00000002 c0107a20 00010061 
00010086
| (XEN)    c027abd0 00010061 00010086 00000002 c0107a20 00010061 00010086 
c027abd0
| (XEN)    00010061 00010086 00000002 c0107a20 00010061 00010086 c027abd0 
00010061
| (XEN)    00010086 00000002 c0107a20 00010061 00010086 c027abd0 00010061 
00010086
| (XEN)    00000002 c0107a20 00010061 00010086 c027abd0 00010061 00010086 
00000002
| (XEN)    c0107a20 00010061 00010086 c027abd0 00010061 00010086 00000002 
c0107a20
| (XEN)    00010061 00010086 c027abd0 00010061 00010086 00000002 c0107a20 
00010061
| (XEN)    00010086 c027abd0 00010061 00010086 00000002 c0107a20 00010061 
00010086
| (XEN)    c027abd0 00010061 00010086 00000002 c0107a20 00010061 00010086 
c027abd0
| (XEN)    00010061 00010086 00000002 c0107a20 00010061 00010086 c027abd0 
00010061
| (XEN)    00010086 00000002 c0107a20 00010061 00010086 c027abd0 00010061 
00010086
| (XEN)    00000002 c0107a20 00010061 00010086 c027abd0 00010061 00010086 
00000002
| (XEN)    c0107a20 00010061 00010086 c027abd0 00010061 00010086 00000002 
c0107a20
| (XEN)    00010061 00010086 c027abd0 00010061 00010086 00000002 c0107a20 
00010061

There seems to be two code adresses in the trace:
| c027abd0 T page_fault
| c0107a20 T invalid_op
which are called in a loop.

Bastian

-- 
I'm a soldier, not a diplomat.  I can only tell the truth.
                -- Kirk, "Errand of Mercy", stardate 3198.9

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users