From owner-freebsd-current@FreeBSD.ORG Sat Sep 15 03:53:11 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3732106564A; Sat, 15 Sep 2012 03:53:11 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 559388FC08; Sat, 15 Sep 2012 03:53:11 +0000 (UTC) Received: by obbun3 with SMTP id un3so8913371obb.13 for ; Fri, 14 Sep 2012 20:53:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=6Qu/scQljqCXMAlmy2a1C9RXfBlb36zF2EFab/XOXPU=; b=BZx7yk5hE6PG1Xwh2xHZhDagOkk8Q2Wbsfyyj+mnW2dYnjHQvreH7NbQ2z/ETWT0+T xCrruFcxSQwwlqzFh/kU0i5BtVkeUN3QpiV8EnufdEBoP0P0SBJWBfQ8PHSnTrSuwBOy FxcDCtooRjblHXSvIVa9zcX4SkLe+9mgWZ78MnaxUC3dQ0RY3FfHuqhmIk4zlKeNcGkT X6apCOp0WeCuLk8ULkbBmZ9Lf8zkyp0H/kTdVAF0t7VzAyz+IN/7zcf7UFNnx806Uuxg ltw792bcdbSsmMUa+gHYIm76qlU48IM/9rEOUPoBFZ4CCLlv9TUg9D4iLx+nBWthUriW jr6A== MIME-Version: 1.0 Received: by 10.60.1.106 with SMTP id 10mr6340079oel.84.1347681190683; Fri, 14 Sep 2012 20:53:10 -0700 (PDT) Received: by 10.60.10.228 with HTTP; Fri, 14 Sep 2012 20:53:10 -0700 (PDT) Date: Fri, 14 Sep 2012 22:53:10 -0500 Message-ID: From: Brandon Gooch To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1 Cc: Hans Petter Selasky Subject: sysctl -a hangs system after r240281 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 15 Sep 2012 03:53:11 -0000 I'm running 10-CURRENT amd64 on a Dell M6500: FreeBSD m6500.local 10.0-CURRENT FreeBSD 10.0-CURRENT #22 r240281M: Fri Sep 14 21:18:50 CDT 2012 root@m6500.local:/usr/obj/usr/src/sys/DELL_M6500 amd64 I ran into a strange issue when running `sysctl -a` in which my system would "freeze" -- the only interaction with the system which was registered was a press of the power button (which wouldn't actually initialize a shutdown). This is a big problem when /etc/rc.d/initrandom calls `sysctl -a` during system startup... I traced this behavior back to commit r240281 which added support for USB Dual Mode Drivers: http://svnweb.freebsd.org/base/head/sys/dev/usb/controller/usb_controller.c?r1=240281&r2=240280&pathrev=240281 At r240280, my system boots fine and I can run `sysctl -a` at will with no bad behavior. I haven't dug deeply into this issue, so this e-mail is more of a heads-up report in case anyone else runs into this issue. I'll add more debugging in my kernel config and capture the information from dmesg and others before and after the r240281 commit. Of course, any hints are appreciated as I delve into this.