From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@Oracle.COM>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>
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 [thread overview]
Message-ID: <4C5AE51F.8060203@goop.org> (raw)
In-Reply-To: <20100805145214.GC5697@phenom.dumpdata.com>
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
next prev parent reply other threads:[~2010-08-05 16:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 15:30 [xen-4.0.1-rc5-pre] [pvops 2.6.32.16] Complete freeze within 2 days, no info in serial log Sander Eikelenboom
2010-08-03 15:45 ` Konrad Rzeszutek Wilk
2010-08-03 15:51 ` Jeremy Fitzhardinge
2010-08-03 16:18 ` Sander Eikelenboom
2010-08-03 17:18 ` Sander Eikelenboom
2010-08-05 9:48 ` Sander Eikelenboom
2010-08-05 14:52 ` Konrad Rzeszutek Wilk
2010-08-05 15:12 ` Sander Eikelenboom
2010-08-05 16:21 ` Jeremy Fitzhardinge [this message]
2010-08-06 9:21 ` Sander Eikelenboom
2010-08-06 15:17 ` Konrad Rzeszutek Wilk
2010-08-06 20:44 ` Jeremy Fitzhardinge
2010-08-08 13:54 ` Sander Eikelenboom
2010-08-08 16:57 ` Sander Eikelenboom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C5AE51F.8060203@goop.org \
--to=jeremy@goop.org \
--cc=keir.fraser@eu.citrix.com \
--cc=konrad.wilk@Oracle.COM \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.