Date: Sun, 7 Apr 2002 21:53:52 -0600 From: Scott Long <scott_long@btc.adaptec.com> To: Josef Karthauser <joe@freebsd.org> Cc: cvs-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/dev/usb uhci.c Message-ID: <20020408035351.GA6762@hollin.btc.adaptec.com> In-Reply-To: <200204071803.g37I3jj44027@freefall.freebsd.org> References: <200204071803.g37I3jj44027@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Apr 07, 2002 at 11:03:45AM -0700, Josef Karthauser wrote: > joe 2002/04/07 11:03:45 PDT > > Modified files: > sys/dev/usb uhci.c > Log: > MFNetBSD: > revision 1.153 > date: 2002/02/11 11:40:33; author: augustss; state: Exp; lines: +67 -26 > Switch to the same abort mechanism as in [eo]hci; it should be more > robust. > > Revision Changes Path > 1.114 +67 -23 src/sys/dev/usb/uhci.c Joe, This change (or actually, this group of changes) changes the behaviour of the ums lockup problem. Now, when I physically detach the device, the detach never completes in the ums driver. I haven't tracked it down yet, but I suspect that ums_detach is never even being called. In fact, usbdevs reports that the device is still connected. However, if I kldunload the ums driver ums_detach does get called, and further down the abort callstack there is a panic. I'll send you all of the relevant debugger info if you are interested. Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020408035351.GA6762>