From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 31 19:46:08 2013 Return-Path: Delivered-To: freebsd-wireless@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 ESMTP id 94CD29E1; Wed, 31 Jul 2013 19:46:08 +0000 (UTC) (envelope-from hans.petter.selasky@bitfrost.no) Received: from mta.bitpro.no (mta.bitpro.no [92.42.64.202]) by mx1.freebsd.org (Postfix) with ESMTP id 16CE024AA; Wed, 31 Jul 2013 19:46:07 +0000 (UTC) Received: from mail.lockless.no (mail.lockless.no [46.29.221.38]) by mta.bitpro.no (Postfix) with ESMTP id 3B7477A13E; Wed, 31 Jul 2013 21:46:07 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.lockless.no (Postfix) with ESMTP id 0129C8F0EC1; Wed, 31 Jul 2013 21:46:13 +0200 (CEST) X-Virus-Scanned: by amavisd-new-2.6.4 (20090625) (Debian) at lockless.no Received: from mail.lockless.no ([127.0.0.1]) by localhost (mail.lockless.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VuCmYRxCY3fA; Wed, 31 Jul 2013 21:46:12 +0200 (CEST) Received: from mail.lockless.no (localhost [127.0.0.1]) by mail.lockless.no (Postfix) with ESMTP id 0DCD88F0EC0; Wed, 31 Jul 2013 21:46:12 +0200 (CEST) Subject: RE: My WLI-UC-GNM up crash From: =?utf-8?Q?Hans_Petter_Selasky?= To: =?utf-8?Q?Adrian_Chadd?= , =?utf-8?Q?Ian_Lepore?= Date: Wed, 31 Jul 2013 21:46:11 +0200 Mime-Version: 1.0 In-Reply-To: References: X-Priority: 3 (Normal) X-Mailer: Zarafa 7.1.4-41394 Message-Id: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: =?utf-8?Q?freebsd-arm?= , =?utf-8?Q?freebsd-wireless=40freebsd=2Eorg?= X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jul 2013 19:46:08 -0000 Hi,=0D=0A=0D=0ATypically this means the USB firmware died, or some comman= d needs to be re-transmitted.=0D=0A=0D=0ASee:=0D=0A=0D=0Ausbdump -i usbus= X -s 65536=0D=0A=0D=0AWhat is really going on.=0D=0A=0D=0A--HPS=0D=0A=20=0D= =0A=20=0D=0A-----Original message-----=0D=0A> From:Adrian Chadd >=0D=0A> Sent: Wednesday 31st July= 2013 20:03=0D=0A> To: Ian Lepore >=0D=0A> Cc: freebsd-arm >; freebsd-wireless@freebsd.org ; Hans Petter Selasky >=0D=0A> Subject: Re: My WLI-UC-GNM up c= rash=0D=0A>=20=0D=0A> No idea about the device disconnect, sorry. is it a= power draw problem=3F=0D=0A>=20=0D=0A>=20=0D=0A> -adrian=0D=0A>=20=0D=0A= > On 31 July 2013 06:41, Ian Lepore > wrote:=0D=0A> > On Wed, 2013-07-31 at 16:28 +0800, XiaoQI Ge wrote= :=0D=0A> >> Last night, I use the latest FreeBSD source (r253827) and=0D=0A= > >> crochet-freebsd compile img=0D=0A> >> My WLI-UC-GNM will be disconne= cted after a period of operation=0D=0A> >>=0D=0A> >> run0: device timeout= =0D=0A> >> run0: at uhub0, port 1, addr 2 (disconnected)=0D=0A> >>=0D=0A>= >> Another log prompted=0D=0A> >> ti_mmchs0: Error: current cmd NULL, al= ready done=3F=0D=0A> >>=0D=0A> >> My BB-Black broken=3F=0D=0A> >=0D=0A> >= The ti_mmchs0 error is not new. My old BBW has done that for months.=0D= =0A> > I'm not sure it's totally harmless, but it's not related to the ru= n0=0D=0A> > timeouts.=0D=0A> >=0D=0A> > -- Ian=0D=0A> >=0D=0A> > ________= _______________________________________=0D=0A> > freebsd-arm@freebsd.org = mailing list=0D=0A> > http://lists.free= bsd.org/mailman/listinfo/freebsd-arm =20=0D=0A> > To unsubscribe, send any mail to "freebsd= -arm-unsubscribe@freebsd.org = "=0D=0A> _______________________________________________=0D=0A> freebsd-= arm@freebsd.org mailing list=0D=0A> htt= p://lists.freebsd.org/mailman/listinfo/freebsd-arm =20=0D=0A> To unsubscribe, send any mail= to "freebsd-arm-unsubscribe@freebsd.org "=0D=0A>=20=0D=0A=0D=0A From owner-freebsd-wireless@FreeBSD.ORG Thu Aug 1 06:27:32 2013 Return-Path: Delivered-To: freebsd-wireless@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 ESMTP id 9A984391; Thu, 1 Aug 2013 06:27:32 +0000 (UTC) (envelope-from rpaulo@felyko.com) Received: from felyko.com (felyko.com [174.136.100.2]) by mx1.freebsd.org (Postfix) with ESMTP id 7E4632BBC; Thu, 1 Aug 2013 06:27:32 +0000 (UTC) Received: from [IPv6:2601:9:4d00:119:c060:f1df:12a7:d6c4] (unknown [IPv6:2601:9:4d00:119:c060:f1df:12a7:d6c4]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by felyko.com (Postfix) with ESMTPSA id D1F9B3982B; Wed, 31 Jul 2013 23:27:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=felyko.com; s=mail; t=1375338446; bh=kBxnkNzrv6vJgjU0JHtW/yLZv1s1bjllwBHhUqB/+nU=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=FW782fvPcutsGqDGmqg+uH5kqXR/PIhQOFSar9p3fMJ5QPJQioh0jCBKyZzxGjrp3 Q9L/XbocQBCN3at+j9Xxx0Kbxg2NteCLYArcvYnjTBZXRZCv6Aty/IMdf/Y168x7AK Z1ivoZx0gB/G9d0x9Dc0l9vFfgu+kaym2BjZxHdk= Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: My WLI-UC-GNM up crash From: Rui Paulo In-Reply-To: Date: Wed, 31 Jul 2013 23:27:25 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <4A2B91AC-286D-4D13-8C1B-DA4822FEDE98@felyko.com> References: <20130729211540.GZ26412@funkthat.com> <1375151095.45247.54.camel@revolution.hippie.lan> To: XiaoQI Ge X-Mailer: Apple Mail (2.1508) Cc: freebsd-arm , "freebsd-wireless@freebsd.org" , Ian Lepore , Hans Petter Selasky X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Aug 2013 06:27:32 -0000 On 31 Jul 2013, at 01:28, XiaoQI Ge wrote: > Last night, I use the latest FreeBSD source (r253827) and > crochet-freebsd compile img > My WLI-UC-GNM will be disconnected after a period of operation >=20 > run0: device timeout > run0: at uhub0, port 1, addr 2 (disconnected) If you are using the USB cable to power the BBB, then that's your = problem. You need a 5V 1A+ power adapter to be able to use USB WiFi = cards with the BeagleBone. -- Rui Paulo