From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [xen-4.0.1-rc5-pre] [pvops 2.6.32.16] Complete freeze within 2 days, no info in serial log Date: Thu, 05 Aug 2010 09:21:51 -0700 Message-ID: <4C5AE51F.8060203@goop.org> References: <698099271.20100803173057@eikelenboom.it> <20100803154541.GA16122@phenom.dumpdata.com> <4C583AFE.7080001@goop.org> <1048476317.20100805114844@eikelenboom.it> <20100805145214.GC5697@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20100805145214.GC5697@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: Sander Eikelenboom , "xen-devel@lists.xensource.com" , Keir Fraser List-Id: xen-devel@lists.xenproject.org On 08/05/2010 07:52 AM, Konrad Rzeszutek Wilk wrote: > The videograbber (vl4) stack trace you sent to me some time ago looked > liked a mutex was held for a very very long time... which I wonder if > that is the cmpxch compiler bug that has hit some folks. Are you using > Debian? The symptom of that bug is that gcc doesn't see any writes to a static variable, so it puts it in a RO section, causing faults. So while I guess its within the realm of possibilities that this is a different manifestation of the same bug, it doesn't seem likely. J