From owner-freebsd-usb@FreeBSD.ORG  Tue May 16 09:13:06 2006
Return-Path: <owner-freebsd-usb@FreeBSD.ORG>
X-Original-To: freebsd-usb@FreeBSD.org
Delivered-To: freebsd-usb@FreeBSD.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9759316A413
	for <freebsd-usb@FreeBSD.org>; Tue, 16 May 2006 09:13:06 +0000 (UTC)
	(envelope-from sem@FreeBSD.org)
Received: from relay-er5.mbrd.ru (relay-er5.mbrd.ru [194.117.71.33])
	by mx1.FreeBSD.org (Postfix) with ESMTP id BD80643D49
	for <freebsd-usb@FreeBSD.org>; Tue, 16 May 2006 09:13:05 +0000 (GMT)
	(envelope-from sem@FreeBSD.org)
Received: from msd.mbrd.ru ([172.16.33.193])
	by relay-er5.mbrd.ru with esmtpa (Exim 4.x) id 1Ffvbo-000FMe-Vw
	for freebsd-usb@FreeBSD.org; Tue, 16 May 2006 13:12:53 +0400
Message-ID: <44699796.40206@FreeBSD.org>
Date: Tue, 16 May 2006 13:12:54 +0400
From: Sergey Matveychuk <sem@FreeBSD.org>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: freebsd-usb@FreeBSD.org
X-Enigmail-Version: 0.93.2.0
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: 7bit
Cc: 
Subject: all usb-ethernet adapters are borked?
X-BeenThere: freebsd-usb@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: FreeBSD support for USB <freebsd-usb.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
	<mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb>
List-Post: <mailto:freebsd-usb@freebsd.org>
List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
	<mailto:freebsd-usb-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 16 May 2006 09:13:06 -0000

After I've explored my problem with rue(4) I've found out our USB stack
is incompatible with our current TCP/IP implementation (6.0+) ("Trying
sleep, but thread marked as sleeping prohibited" problem).

I've discussed it with glebius and he told me, it's complete USB problem.

As I understand USB transfer should be rewritten to use no mspleep calls.

Any comments? Any quick fixes?
-- 
Sem.