On Fri, Oct 20, 2006 at 09:49:09AM +0200, Alexander Larsson wrote: > On Thu, 2006-10-19 at 12:37 -0400, Bill Nottingham wrote: > > Alexander Larsson (alexl@xxxxxxxxxx) said: > > > Further information from the reporter seems to say that it only affects > > > xen kernels (dom0), on all cpu:s but opterons. Very strange stuff. > > > > ... including x64? Or is it just on 32-bit? > > >From the bug: > > Opteron box, x86_64 kernel 2.6.18-2798, x86_64 mono 1.1.17-3: works > Opteron box, x86_64 kernel 2.6.18-2798xen, x86_64 mono 1.1.17-3: works > Opteron box, i686 kernel 2.6.18-2798, i686 mono 1.1.17-3: works > Opteron box, i686 kernel 2.6.18-2798xen, i686 mono 1.1.17-3: works > EM64T box, x86_64 kernel 2.6.18-2798, x86_64 mono 1.1.17-3: works > EM64T box, x86_64 kernel 2.6.18-2798xen, x86_64 mono 1.1.17-3: works > EM64T box, i686 kernel 2.6.18-2798, i686 mono 1.1.17-3: works > EM64T box, i686 kernel 2.6.18-2798xen, i686 mono 1.1.17-3: SEGFAULT > Athlon box, i686 kernel 2.6.18-2798xen, i686 mono 1.1.17-3: SEGFAULT > Pentium 4 box, i686 kernel 2.6.18-2798xen, i686 mono 1.1.17-3: SEGFAULT Sounds more like a Xen bug than an execshield bug. File a bz against kernel-xen. Dave -- http://www.codemonkey.org.uk -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
