From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: Xenalyze? Date: Thu, 8 Jul 2010 17:36:35 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Thomas Graves Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org I had a work-around for the problem in a local patch-queue somewhere. I've pushed it (along with a bunch of local stuff I had lying around ) -- do a pull and let me know if it works better. -George On Thu, Jul 8, 2010 at 3:46 PM, Thomas Graves wrote= : > > -bash-3.2$ hg id > 503e0902a86a+ tip > -bash-3.2$ hg parents > changeset: =A0=A049:503e0902a86a > tag: =A0=A0=A0=A0=A0=A0=A0=A0tip > user: =A0=A0=A0=A0=A0=A0=A0George Dunlap > date: =A0=A0=A0=A0=A0=A0=A0Tue Jun 22 17:11:51 2010 +0100 > summary: =A0=A0=A0=A0More xenalyze type fixes > > I=92m using a clone of http://xenbits.xensource.com/ext/xenalyze.hg and t= hen > patched with the patch -p1 < back-patches/3.4.diff and make on rhel5.4. > > Let me know if you > > Thanks, > Tom > > > On 7/8/10 9:24 AM, "George Dunlap" wrote: > > The file length itself probably isn't that important, but rather the > fact that longer trace files increase the opportunity for certain > kinds of probabilistic problematic events to occur. > > The problem here looks like a problem with TSC skew -- xenalyze is > having trouble figuring out how to process the records in the right > order because of drift in the TSC value across cores (that's what the > "Possible tsc skew" messages are about), and end up breaking an > assumption because it's failing (hence the "FATAL: p->current =3D NULL" > message) . > > Can you give me the cs of the tip of your hg tree? =A0I'll take a look > and see if I have a local fix. > > =A0-George > > On Thu, Jul 8, 2010 at 3:09 PM, Thomas Graves wro= te: >> Hello, >> >> I'm new to using xentrace and xenalyze and I am having problems running >> xenalyze on a large trace file. It is always giving me a fatal error. If= I >> run it on like a 30 second trace it seems to work fine. >> >> Is this a known issue or am I possibly doing something wrong? =A0Do you >> think >> it would work if I truncate the file or would it be missing stuff xenaly= ze >> expects? =A0 If there is no way to truncate it =A0perhaps I'll see if I = can >> modify it to only show me certain time frame - I haven't looked at the >> code >> yet so I guess I'll have to see if that is possible. >> >> I'm using xen3.4.3 with rhel5.4 dom0 running a rhel5.4 vm. >> >> I'm trying to debug a vm hang at boot which sporadically occurs so I jus= t >> have trace running while I do a bunch of creates and deletes so the trac= e >> file gets fairly large. =A0If you have other ideas what might work bette= r I >> would be interested in hearing them. >> >> >> ------- >> -bash-3.2$ ls -la trace.raw >> -rw-r--r-- 1 root root 13238044416 Jul =A07 23:02 trace.raw >> -bash-3.2$ xenalyze/xenalyze --cpu-hz=3D2.43G --summary =A0trace.raw > o= ut >> >> ------- >> .. >> .. >> .. >> .. >> runstate_change old_runstate blocked, d1402v0 runstate runnable. =A0Poss= ible >> tsc skew. >> runstate_change old_runstate blocked, d1402v0 runstate runnable. =A0Poss= ible >> tsc skew. >> runstate_change old_runstate runnable, d1402v0 runstate running. =A0Poss= ible >> tsc skew. >> =A0Not updating. >> FATAL: p->current null >> ] =A020f101(20:f:101) 3 [ 802061ea ffffffff f ] >> ----- >> >> >> Any help is appreciated, >> Thanks, >> Tom Graves >> >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel >> > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > >