Date: Wed, 31 Jul 2013 07:41:11 -0600 From: Ian Lepore <ian@FreeBSD.org> To: XiaoQI Ge <ghw@7axu.com> Cc: freebsd-arm <freebsd-arm@FreeBSD.org>, "freebsd-wireless@freebsd.org" <freebsd-wireless@FreeBSD.org>, Hans Petter Selasky <hans.petter.selasky@bitfrost.no> Subject: Re: My WLI-UC-GNM up crash Message-ID: <1375278071.45247.144.camel@revolution.hippie.lan> In-Reply-To: <CAKrd9eVzY1GX71G88jk0icivoYNR5Tgx3QewqFdvC_jPi-sMnA@mail.gmail.com> References: <cakrd9exvuqeqz=3ntmh7k3e4_6fjw9jph_tpfchujhqhwwbzsg@mail.gmail.com> <zarafa.51f6ad45.7961.536131947b8b1205@mail.lockless.no> <20130729211540.GZ26412@funkthat.com> <1375151095.45247.54.camel@revolution.hippie.lan> <CAKrd9eVzY1GX71G88jk0icivoYNR5Tgx3QewqFdvC_jPi-sMnA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2013-07-31 at 16:28 +0800, 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 > > run0: device timeout > run0: at uhub0, port 1, addr 2 (disconnected) > > Another log prompted > ti_mmchs0: Error: current cmd NULL, already done? > > My BB-Black broken? The ti_mmchs0 error is not new. My old BBW has done that for months. I'm not sure it's totally harmless, but it's not related to the run0 timeouts. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1375278071.45247.144.camel>