https://bugzilla.novell.com/show_bug.cgi?id=687368
https://bugzilla.novell.com/show_bug.cgi?id=687368#c7
Roger Cruz
Not NULL, but pointing to memory that is (no longer?) present. Without /var/log/boot.msg (or whatever its equivalent is on Centos) we won't be able to tell whether the page was there initially.
Quite possibly a dangling pointer, particularly because the stack trace seems to indicate attempts to use xsave, support for which is off by default in the hypervisor (and the kernel shouldn't even detect its availability) mostly because it's incompatible with live migration up to and including Xen 4.1.0.
Hi Jan, We've been seeing the same type of exception and same stack trace when running with 2.6.38 PV-OPS kernel on top of Xen 4.0. Unfortunately, all I have is a picture of the stack trace so it won't help you with the information you asked for here. My question for you is regarding this statement "attempts to use xsave, support for which is off by default in the hypervisor"... How can I confirm that xsave support is turned off? This code only gets excuted when the xsaveopt feature is present in the CPU and when in dom0 I do a 'cat /proc/cpuinfo', I can see the xsaveopt capability is turned on so the dom0 kernel is using it. flags : fpu de tsc msr pae cx8 apic sep cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good nopl nonstop_tsc aperfmperf pni pclmulqdq est ssse3 cx16 sse4_1 sse4_2 x2apic popcnt aes avx hypervisor lahf_lm ida arat epb xsaveopt pln pts dts -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.