From owner-freebsd-current Thu May 31 1:44:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from henny.webweaving.org (gate.qubesoft.com [212.113.16.243]) by hub.freebsd.org (Postfix) with ESMTP id 6A8EA37B422 for ; Thu, 31 May 2001 01:44:40 -0700 (PDT) (envelope-from n_hibma@FreeBSD.ORG) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.11.3/8.11.3) with ESMTP id f4V8iVu34926; Thu, 31 May 2001 09:44:31 +0100 (BST) (envelope-from n_hibma@FreeBSD.ORG) Date: Thu, 31 May 2001 09:44:31 +0100 (BST) From: X-X-Sender: To: Warner Losh Cc: Subject: Re: USB Ethernet hang on "eject" In-Reply-To: <200105310355.f4V3tiE88901@harmony.village.org> Message-ID: <20010531094239.S34739-100000@henny.webweaving.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Of course not. I never do that with pccards :-) That's why I asked it :-) It shouldn't be necessary. > When I do that, as a work around, I find that I can pull the plug. > > How hard is it to fix the way that the ethernet driver reads the MII > registers in the interrupt context? Hard, but probably not impossible. Especially with threads in interrupts or worker threads, it should be possible. Task queue might be a solution as well, although I guess the problem is that the action is blocking, and task queue might not handle that very well. A worker thread for the ethernet drivers is probably the simplest solution. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message