Re: [Xen-users] Xen 4.3.1 / Linux 3.12 panic

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

(CCing Linux guys, not because this involves Linux but because I CCed
them on the previous mail)

On Wed, 2013-11-06 at 10:12 +0100, Wouter de Geus wrote:
> I've been experimenting some more.
> Last 24 hours I've been constantly compiling (in a while loop) using my 
> (non-Xen) stock slackware kernel 3.10.7, stable as a rock.
> 
> Just booted Xen 4.3.1 with my custom 3.11 kernel, crashed as soon as I did a 
> rm -rf on some old sources.
> Here's the console output:
> ------
> (XEN) ----[ Xen-4.3.1  x86_64  debug=n  Not tainted ]----
> (XEN) CPU:    4
> (XEN) RIP:    e008:[<ffff82c4c013f47c>] do_dbs_timer+0x11c/0x240

The is a cpufreq thing from the looks of it.

cpufreq differences between native Linux and Xen could cause weird
memory corruption, manifesting as a variety of page faults, GPFs etc, I
guess.

Perhaps investigate disabling cpufreq stuff under Xen? I'm not sure how
one does this exactly but google through up
http://wiki.xen.org/wiki/Xen_power_management and I saw some references
in http://xenbits.xen.org/docs/unstable/misc/xen-command-line.html

Ian.


> (XEN) RFLAGS: 0000000000010286   CONTEXT: hypervisor
> (XEN) rax: 0000000000000000   rbx: 000000003b9d8704   rcx: 000000000000001d
> (XEN) rdx: 0000000000000000   rsi: 0000000000000000   rdi: 0000000000000000
> (XEN) rbp: ffff830834fd6380   rsp: ffff830834fffe30   r8:  00000012d91afd3e
> (XEN) r9:  ffff830834ff7128   r10: 0000000000000000   r11: 0000000000000000
> (XEN) r12: 0000000000000000   r13: ffff830977948860   r14: 8000000000000380
> (XEN) r15: 000000000000001d   cr0: 000000008005003b   cr4: 00000000000406f0
> (XEN) cr3: 00000000d7c5f000   cr2: 0000000000000000
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 0000   cs: e008
> (XEN) Xen stack trace from rsp=ffff830834fffe30:
> (XEN)    0000000000000286 ffff82c4c02ea940 ffff82c4c0300980 0027ac4021424b00
> (XEN)    000000fb00000000 ffff831021424d00 ffff831021424d50 00000012d91b237a
> (XEN)    0000000000000004 0000000000000000 0000000000000000 ffff82c4c019bbf1
> (XEN)    00000000ffffffff ffff82c4c02c7800 0014e1920000200d 0000000000000000
> (XEN)    0000000000000000 00000000ffffffff ffff82c4c02c7800 ffff82c4c01245f4
> (XEN)    000000000000e008 ffff830834ff8000 ffff830834ff8000 0000000000000004
> (XEN)    0000000000000004 ffff82c4c01584ce 0000000000000000 0000000000000000
> (XEN)    0000000000000001 0000000000000000 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000004 ffff8300d7afc000
> (XEN)    0000004374cd5a00 0000000000000000
> (XEN) Xen call trace:
> (XEN)    [<ffff82c4c013f47c>] do_dbs_timer+0x11c/0x240
> (XEN)    [<ffff82c4c019bbf1>] acpi_processor_idle+0x201/0x550
> (XEN)    [<ffff82c4c01245f4>] __do_softirq+0x74/0xa0
> (XEN)    [<ffff82c4c01584ce>] idle_loop+0x1e/0x50
> (XEN)
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 4:
> (XEN) GENERAL PROTECTION FAULT
> (XEN) [error_code=0000]
> (XEN) ****************************************
> (XEN)
> (XEN) Manual reset required ('noreboot' specified)
> ------
> 
> Suggestions anyone? :)
> 
> Regards,
> 
> Wouter.
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users