From owner-freebsd-current@FreeBSD.ORG Wed May 21 19:21:28 2014 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A58A48D6; Wed, 21 May 2014 19:21:28 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5675B2728; Wed, 21 May 2014 19:21:27 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 3C00F1FE026; Wed, 21 May 2014 21:21:26 +0200 (CEST) Message-ID: <537CFCE4.2000300@selasky.org> Date: Wed, 21 May 2014 21:22:12 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Jan Henrik Sylvester , John Baldwin , Kevin Oberman , Adrian Chadd Subject: Re: Thinkpad T410: resume broken References: <53762216.8020205@gmx.net> <537753F3.6000202@FreeBSD.org> <537CFB7C.60702@janh.de> In-Reply-To: <537CFB7C.60702@janh.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "current@freebsd.org" , Stefan Ehmann , "freebsd-mobile@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 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: Wed, 21 May 2014 19:21:28 -0000 On 05/21/14 21:16, Jan Henrik Sylvester wrote: > Unfortunately, my USB mouse does not work anymore: After the first > resume, it took a few seconds until it worked again (the build in > touchpad was back immediately). After the second resume, it would not > work anymore at all, even after reconnecting it to a different EHCI > port. It does work at a XHCI, though, until the next resume. Anyhow, > this is obviously not related to the original problem. Hi, USB controller are being reset at resume, so I think this indicates a more fundamental PCI/BUS problem. --HPS