From owner-freebsd-current@FreeBSD.ORG Tue Apr 16 20:03:07 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 74DD66A1; Tue, 16 Apr 2013 20:03:07 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-oa0-f52.google.com (mail-oa0-f52.google.com [209.85.219.52]) by mx1.freebsd.org (Postfix) with ESMTP id 35FA61438; Tue, 16 Apr 2013 20:03:07 +0000 (UTC) Received: by mail-oa0-f52.google.com with SMTP id k18so888722oag.39 for ; Tue, 16 Apr 2013 13:03:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=vUGSwXRi2dug0e6ufpVkA6LHXluyQU7ewHT1aLD1mks=; b=H8qG4Z3i6XNBgyNokdArKTms2lAD8NtYOeoXFqGMgaw8SH2P23cUL+4WAPKpTADlY/ zJxwrfAQix79NwGOYmCX58CR75L7Y+1qrjB4Spvzac88Ygneyz5/STuwe5KgiBDIIeD8 4ERKdmPEtLfC5+d0ldiyU5+hHKK5cgjYkfYZwcAoLfSne/Y5T0j8+6VN2RDsofOXhv9Q lVGQHhtuAX961JN7kZO91LDV5VCG1zIBAdTSQTrgtow+TenNd+C2kwkQLKiGVJ6FVEVk U7i9i+28cLo3GL0ukybcRWpGqbr8gop3I8sS3CUUqNy7GRiGW6kArFw6+a3ojSGGojr/ TiSA== MIME-Version: 1.0 X-Received: by 10.60.132.196 with SMTP id ow4mr1421064oeb.75.1366142586458; Tue, 16 Apr 2013 13:03:06 -0700 (PDT) Received: by 10.76.109.236 with HTTP; Tue, 16 Apr 2013 13:03:06 -0700 (PDT) In-Reply-To: <516DAD14.9020307@FreeBSD.org> References: <516DAD14.9020307@FreeBSD.org> Date: Tue, 16 Apr 2013 16:03:06 -0400 Message-ID: Subject: Re: DTrace gone quiet? From: Ryan Stone To: Navdeep Parhar Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Apr 2013 20:03:07 -0000 On Tue, Apr 16, 2013 at 3:57 PM, Navdeep Parhar wrote: > I just upgraded my kernel and userspace to head (r249552) and I notice > that DTrace doesn't output anything until I hit ctrl-c. All previous > "hits" on the probe appear lost. For example: > > # dtrace -n 'fbt::ether_output:entry' > dtrace: description 'fbt::ether_output:entry' matched 1 probe > > (No output here. I waited a long time before the ctrl-c and I know the > system is actively transmitting and receiving Ethernet traffic). > > ^C > CPU ID FUNCTION:NAME > 9 29354 ether_output:entry > 8 29354 ether_output:entry > 8 29354 ether_output:entry > 8 29354 ether_output:entry > > > Can anyone confirm or contradict this on a recent HEAD (around r249552 > in my case)? > > Regards, > Navdeep > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > Hm, if you run with "-x bufpolicy=switch" does it work? It sounds as through the ring buffer policy is being set by default for you. I'm not sure how that could happen.