RE: [Xen-ia64-devel] FYI: gcc segfault also meet with as

["Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>]

Yes this problem has been with us for several months and
anybody who exercises Xen/ia64 heavily will probably see it
occur.  It is definitely not specific to gcc... it may even
be occuring in ltp, but since it is not repeatable (the
failure appears almost randomly), it is hard to link a
single ltp test failure to the "gcc segfault" problem.

Based on what I have seen, I suspect it has something
to do with a stale translation... perhaps some flush/purge
is not working properly or maybe a region id is being
incorrectly re-used.

Isolating this problem will take a lot of effort and
some sophisticated debug tools/hardware.  However, I
would not recommend Xen/ia64 be "released" to customers
until it is found/fixed.

Dan

> -----Original Message-----
> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf 
> Of Tristan Gingold
> Sent: Tuesday, April 04, 2006 6:13 AM
> To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-ia64-devel] FYI: gcc segfault also meet with as
> 
> Hi,
> 
> I am not currently tracking the gcc segfault; I am just watching it.
> During a Linux compilation, I also got as segfault.
> 
> No conclusion :-(
> 
> Tristan.
> 
> 
> 
> _______________________________________________
> Xen-ia64-devel mailing list
> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ia64-devel
> 

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