Re: [Xen-devel] latest pv_ops dom0 (2.6.29-rc6) crashes / unhandled page fault

[M A Young <m.a.young@xxxxxxxxxxxx>]

On Mon, 2 Mar 2009, Pasi Kärkkäinen wrote:

> On Mon, Mar 02, 2009 at 08:07:56PM +0000, M A Young wrote:
> > On Mon, 2 Mar 2009, Pasi Kärkkäinen wrote:
> >
> > > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input
> > > to Xen)
> > > (XEN) Freed 112kB init memory.
> > > mapping kernel into physical memory
> > > (XEN) d0:v0: unhandled page fault (ec=0000)
> > > (XEN) Pagetable walk from bffff000:
> > > (XEN)  L3[0x002] = 000000003d204001 00001204
> > > (XEN)  L2[0x1ff] = 0000000000000000 ffffffff
> > > (XEN) domain_crash_sync called from entry.S (ff1a2c9e)
> > > (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
> > > (XEN) ----[ Xen-3.3.1  x86_32p  debug=n  Not tainted ]----
> > ...
> >
> > What is your setting for CONFIG_CC_STACKPROTECTOR in your compile? There
> > are bits of xen_kernel_start that break if you have this enabled.
> [root@dom0test linux-2.6-xen]# grep CONFIG_CC_STACKPROTECTOR .config
> # CONFIG_CC_STACKPROTECTOR is not set
>
> So it's not that..
Strange, because it looked pretty similar to the second crash of
http://lists.xensource.com/archives/html/xen-devel/2009-02/msg00852.html
and the followup
http://lists.xensource.com/archives/html/xen-devel/2009-02/msg00875.html
It might be worth double-checking the state of -fstack-protector 
-fno-stack-protector -fstack-protector-all etc. in your Makefile.
        Michael Young

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