From owner-freebsd-current@FreeBSD.ORG  Mon Jan 26 20:11:50 2015
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id BBFE445A
 for <freebsd-current@freebsd.org>; Mon, 26 Jan 2015 20:11:50 +0000 (UTC)
Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com
 [IPv6:2607:f8b0:4001:c05::230])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 83F36797
 for <freebsd-current@freebsd.org>; Mon, 26 Jan 2015 20:11:50 +0000 (UTC)
Received: by mail-ig0-f176.google.com with SMTP id hl2so337281igb.3
 for <freebsd-current@freebsd.org>; Mon, 26 Jan 2015 12:11:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date:message-id:subject
 :from:to:content-type;
 bh=QG1gRCWzWBuCmxVxFZml8Dfd845q/+NI0TLb7lerS+U=;
 b=Q5vgZZQ3XaH5tQuN2vn7Nstd84ZZN3ii4LJRXbpgU5qZ7KdL7K8gt/pGSr0k+3K1jP
 1rsn3vMQdI5Ql/LsZbDvomPlmnsSM7yW/dcStFTtbArvXVLUMUfVoCEXBCtSA/06TfVd
 SaPb3ZSxPdaa+VuVRVf8ibcynBbymhRSZ4XDDoaTj6Fr4O86AD+awPrePykWr45GcwPU
 dor9UuJrmJ48Kjvjw366P8hriq0udZsuVHjho3r3ugxJ/g/CpWkXcLLpG1j2HK/GBPor
 /HOwCX4l3k/iQm13A2ukD3GVtiYooq0pM4bpL07GcWE0yUHzV+Huw4oYjeToWh5lardm
 XxFA==
MIME-Version: 1.0
X-Received: by 10.42.201.78 with SMTP id ez14mr22495945icb.22.1422303110009;
 Mon, 26 Jan 2015 12:11:50 -0800 (PST)
Sender: adrian.chadd@gmail.com
Received: by 10.36.78.14 with HTTP; Mon, 26 Jan 2015 12:11:49 -0800 (PST)
In-Reply-To: <CAJ-VmonoZ0bz2HRNi2s5yA7vNSeUAGjwnt80L8MBY9OOEz_9-w@mail.gmail.com>
References: <CAJ-VmonoZ0bz2HRNi2s5yA7vNSeUAGjwnt80L8MBY9OOEz_9-w@mail.gmail.com>
Date: Mon, 26 Jan 2015 12:11:49 -0800
X-Google-Sender-Auth: qbT8WRVU6Z0LUqXuZAJpWJOHfqM
Message-ID: <CAJ-VmokZ7b1Wz0CsMdbjiVBwTQW_s78ePC2USE+yArzrMrbXbw@mail.gmail.com>
Subject: Re: Is anyone using the schedgraph.d script?
From: Adrian Chadd <adrian@freebsd.org>
To: freebsd-current <freebsd-current@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 20:11:50 -0000

... ignore it for now; I ran some other profiling and then when I
tried schedgraph.d again, it started spitting out events for that CPU.

I'll file a PR if I see it happen more often.

:(


-a


On 26 January 2015 at 12:05, Adrian Chadd <adrian@freebsd.org> wrote:
> Hi,
>
> I'm having problems with Ryan's schedgraph.d script
> (people.freebsd.org/~rstone/dtrace/)
>
> It runs fine, but if a CPU core is 100% busy, I get zero scheduler
> events logged from it. Said core is doing around 30,000 syscalls a
> second, around 250,000 context switches and 125,000 interrupt sa
> second - but whilst it's doing this, I get zero events from dtrace for
> said CPU.
>
> Has anyone hit this kind of situation before?
>
>
>
> -a