Re: u3g and ubsa

> 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.

Nick