From owner-freebsd-usb@FreeBSD.ORG Mon Jun 17 19:20:05 2013 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 35C17613; Mon, 17 Jun 2013 19:20:05 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x22d.google.com (mail-qa0-x22d.google.com [IPv6:2607:f8b0:400d:c00::22d]) by mx1.freebsd.org (Postfix) with ESMTP id E32181A25; Mon, 17 Jun 2013 19:20:04 +0000 (UTC) Received: by mail-qa0-f45.google.com with SMTP id ci6so1687936qab.18 for ; Mon, 17 Jun 2013 12:20:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=pxRIarUDvAXiWVhHVRzbpTIPZtZ0uXkPaWU3Oy8l80M=; b=lBKVRxiSyBC/L3tSttsJrtWc+CrC0yqUd36s2Xac16FbogV/emWohFGSF5smn+74dR WI18/iIHoRvCZTID2OGufaiS5gRH1UHlmnt4/TPnI2GjOCX3F9j38nXHJW0GcC2yQYvD gRm0yAG5i768ZMnTs1VByLNUKeNQDxwwdW6vB63gOqNLfUmrt1o9YpWmxjGgMTNWhAna yQM3UAy5tzIeGTc05TXbe74W7d0dINbDDu4lVYVMls0JqF861weKQenyKot1nmjvSqZn kzgOR7CyFYW7yZOiUZa6DFVJh5eI2hmYtdDYauaxvBDZ3NQf/olmQP3EGZNHPO5rf0t1 z5zA== MIME-Version: 1.0 X-Received: by 10.229.112.6 with SMTP id u6mr7167855qcp.47.1371496804475; Mon, 17 Jun 2013 12:20:04 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.5.65 with HTTP; Mon, 17 Jun 2013 12:20:04 -0700 (PDT) Date: Mon, 17 Jun 2013 12:20:04 -0700 X-Google-Sender-Auth: XdHl3wEWmaNfUPmFhJhPgj7921k Message-ID: Subject: T400 suspend/resume quirk - USB ports stay powered down From: Adrian Chadd To: freebsd-usb@freebsd.org, freebsd-mobile@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 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: Mon, 17 Jun 2013 19:20:05 -0000 Hi, The one annoyance with my Thinkpad T400 is that the USB ports stay powered down upon resume. this is on a very recent -9 (as of a few days ago.) What kind of debugging information would help people chase down what this particular issue is? Thanks! adrian