From owner-freebsd-current@FreeBSD.ORG Wed Nov 26 09:14:12 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 666741065672 for ; Wed, 26 Nov 2008 09:14:12 +0000 (UTC) (envelope-from vova@sw.ru) Received: from relay.sw.ru (mailhub.sw.ru [195.214.232.25]) by mx1.freebsd.org (Postfix) with ESMTP id CBE348FC08 for ; Wed, 26 Nov 2008 09:14:10 +0000 (UTC) (envelope-from vova@sw.ru) Received: from vbook.fbsd.ru ([10.30.1.111]) (authenticated bits=0) by relay.sw.ru (8.13.4/8.13.4) with ESMTP id mAQ9E7hK016094 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Nov 2008 12:14:09 +0300 (MSK) Received: from vova by vbook.fbsd.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1L5GTH-000284-Ju; Wed, 26 Nov 2008 12:14:07 +0300 From: Vladimir Grebenschikov To: Nick Hibma In-Reply-To: <200811260928.36978.nick@van-laarhoven.org> References: <492A62EF.7000803@bsdforen.de> <200811251545.10807.nick@van-laarhoven.org> <1227685292.1852.12.camel@localhost> <200811260928.36978.nick@van-laarhoven.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: SWsoft Date: Wed, 26 Nov 2008 12:14:07 +0300 Message-Id: <1227690847.1790.20.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: freebsd-current@freebsd.org Subject: Re: u3g and ubsa X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vova@fbsd.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Nov 2008 09:14:12 -0000 On Wed, 2008-11-26 at 09:28 +0100, Nick Hibma wrote: > > dmesg has: > > Nov 26 10:25:49 vbook kernel: ucom0: invalid receive data size, > > -754491385 chars > > Nov 26 10:25:49 vbook kernel: ucom0: invalid receive data size, > > -754491390 chars > > Nov 26 10:25:51 vbook kernel: ucom0: invalid receive data size, > > -754491385 chars > > Nov 26 10:25:52 vbook kernel: ucom0: invalid receive data size, > > -754491390 chars > > Nov 26 10:25:56 vbook kernel: ucom0: invalid receive data size, > > 626606082 chars > > Nov 26 10:25:59 vbook kernel: ucom0: invalid receive data size, > > 466214914 chars > > Nov 26 10:26:00 vbook kernel: ucom0: invalid receive data size, > > 466214919 chars > > Nov 26 10:26:01 vbook kernel: ucom0: invalid receive data size, > > 466214914 chars > > [Organising my thoughts] It looks like the actlen field in the returned xfer > is completely bogus. That either means > 1) someone scribbled over it > 2) the xfer is pointing in the wrong direction or is not initialised > 3) there is a bug in the USB code that does notset actlen correctly in some > cases, but I would expect it to 0 in that case. > > I'll have to have a better look to see what is happening. Keep in mind - that when I've these messages only when even connect on port does not works. When connect works - there was no such messages. > Nick -- Vladimir B. Grebenschikov vova@fbsd.ru