Date: Wed, 26 Nov 2008 12:14:07 +0300 From: Vladimir Grebenschikov <vova@fbsd.ru> To: Nick Hibma <nick@van-laarhoven.org> Cc: freebsd-current@freebsd.org Subject: Re: u3g and ubsa Message-ID: <1227690847.1790.20.camel@localhost> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1227690847.1790.20.camel>