[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: USB4BSD release candidate number 3 - request for review
- To: "M. Warner Losh" <imp_(_at_)_bsdimp_(_dot_)_com>
- Subject: Re: USB4BSD release candidate number 3 - request for review
- From: Rink Springer <rink_(_at_)_FreeBSD_(_dot_)_org>
- Date: Wed, 5 Nov 2008 11:04:33 +0100
- Cc: current_(_at_)_freebsd_(_dot_)_org, bright_(_at_)_mu_(_dot_)_org, lme_(_at_)_freebsd_(_dot_)_org, freebsd-current_(_at_)_freebsd_(_dot_)_org, freebsd-usb_(_at_)_freebsd_(_dot_)_org, rbgarga_(_at_)_gmail_(_dot_)_com
On Wed, Nov 05, 2008 at 02:18:17AM -0700, M. Warner Losh wrote:
> In message: <200811050914_(_dot_)_44225_(_dot_)_hselasky_(_at_)_c2i_(_dot_)_net>
> Hans Petter Selasky <hselasky_(_at_)_c2i_(_dot_)_net> writes:
> : On Wednesday 05 November 2008, Lars Engels wrote:
> : > 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?
> :
> : It is not a USB problem. It is the CAM layer that is hanging on the disk.
>
> Sure it is CAM layer and not buffer cache or filesystem code?
Well, the CAM layer problem will immediately first - it does not like
CAM busses disappearing. Once this is fixed or avoided and the problem
still shows up, we can blame buffer cache / filesystem code.
As I suggested before, a good fix is to create one CAM bus per USB root
hub, and use that to attach all umass devices to. This will also get rid
of the one-bus-per-umass-device which is visually unappealling.
Regards,
Rink
--
Rink P.W. Springer - http://rink.nu
"Anyway boys, this is America. Just because you get more votes doesn't
mean you win." - Fox Mulder
_______________________________________________
freebsd-usb_(_at_)_freebsd_(_dot_)_org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscribe_(_at_)_freebsd_(_dot_)_org"
Visit your host, monkey.org