Date: Tue, 04 Nov 2008 18:30:51 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: bruce@cran.org.uk Cc: current@freebsd.org, Olivier@freebsd.org, bright@mu.org, rbgarga@gmail.com, freebsd-current@freebsd.org, freebsd-usb@freebsd.org, lme@freebsd.org Subject: Re: USB4BSD release candidate number 3 - request for review Message-ID: <20081104.183051.689649421.imp@bsdimp.com> In-Reply-To: <20081104165029.225511d8@tau.draftnet> References: <20081104220725.GC8256@e.0x20.net> <20081104230402.GD8256@e.0x20.net> <20081104165029.225511d8@tau.draftnet>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20081104165029.225511d8@tau.draftnet>
Bruce Cran <bruce@cran.org.uk> writes:
: On Wed, 5 Nov 2008 00:04:02 +0100
: Lars Engels <lme@FreeBSD.org> wrote:
: > Now I just removed everything but usb2_core from the kernel config and
: > load the modules manually. So far it runs pretty good.
: >
: > Mounting a umass device, removing it and doing an 'ls' on the
: > mountpoint freezes the system, I thought this should not happen with
: > the new stack?
: >
:
: I seem to remember the problem was tracked back to something in the cam
: layer not liking surprise removals?
For msdos filesystem, there were a number of minor tweaks that were
made to make this suck less. Some were in the old usb layer, but most
were in the buffer cache of FreeBSD to make it more resilient to
errors from the device... But it wasn't totally fixed... Hans' stack
did have a period of time when card removal was working better than
the stock FreeBSD stack, but that got cleaned up before 7.0.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081104.183051.689649421.imp>