From owner-freebsd-usb@FreeBSD.ORG Fri Jul 30 15:55:19 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C23F1065677 for ; Fri, 30 Jul 2010 15:55:19 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe10.swip.net [212.247.155.33]) by mx1.freebsd.org (Postfix) with ESMTP id 68F778FC16 for ; Fri, 30 Jul 2010 15:55:17 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=Q9VExO8FNj0A:10 a=8nJEP1OIZ-IA:10 a=M8b_wTzEtboA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=6I5d2MoRAAAA:8 a=poegI_aAKXUd66diI5gA:9 a=psuG5rOUw4V6MrEgYgHit0r3kjoA:4 a=wPNLvfGTeEIA:10 a=cz0DJFMf1QgA:10 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe10.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 1213225679; Fri, 30 Jul 2010 17:55:16 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org, bf1783@gmail.com Date: Fri, 30 Jul 2010 17:52:07 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.1-PRERELEASE; KDE/4.4.5; amd64; ; ) References: In-Reply-To: X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'(; _IjlA: hGE..Ew, XAQ*o#\/M~SC=S1-f9{EzRfT'|Hhll5Q]ha5Bt-s|oTlKMusi:1e[wJl}kd}GR Z0adGx-x_0zGbZj'e(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201007301752.07485.hselasky@c2i.net> Cc: freebsd-acpi@freebsd.org Subject: Re: suspend/resume and the freebsd usb stack X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2010 15:55:19 -0000 On Friday 30 July 2010 16:53:22 b. f. wrote: > Are these criticisms of suspend/resume for the usb stack justified?: > > http://lists.freebsd.org/pipermail/svn-src-head/2010-July/018974.html > > If so, are there any plans to fix the problem(s)? > > Regards, > b. Hi, Suspend and resume has not been too much tested! Some part is done in the BIOS, the other part is done in the OS. You can try doing a detach instead of a suspend, and an attach instead of a resume. Patches are welcome! --HPS