From owner-freebsd-usb@FreeBSD.ORG Fri Sep 13 04:18:51 2013 Return-Path: Delivered-To: freebsd-usb@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B5EEB4E0 for ; Fri, 13 Sep 2013 04:18:51 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 69F752453 for ; Fri, 13 Sep 2013 04:18:51 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r8D4In8T024946 for ; Thu, 12 Sep 2013 22:18:49 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r8D4InS8024943 for ; Thu, 12 Sep 2013 22:18:49 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Thu, 12 Sep 2013 22:18:49 -0600 (MDT) From: Warren Block To: freebsd-usb@FreeBSD.org Subject: usbdump and hw.usb.no_pf Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Thu, 12 Sep 2013 22:18:50 -0600 (MDT) X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Sep 2013 04:18:51 -0000 A 9-STABLE desktop running amd64 steadfastly refuses to run usbdump(8): # usbdump -i usbus0 -v -w /tmp/usb.log read: Device not configured 0 packets captured 0 packets received by filter 0 packets dropped by kernel It turns out that having hw.usb.no_pf="1" set in /boot/loader.conf to speed up booting disables usbdump. Interestingly, this sysctl can be changed at runtime, but usbdump will still not work. The value has to be set in /boot/loader.conf at boot for usbdump to work again. If usbdump could produce a warning when this sysctl is was set to 1 at boot, it would make the mysterious error less mysterious.