On Tue, Jan 18, 2005 at 01:13:57PM +0900, Horms wrote: > On Tue, Jan 18, 2005 at 04:59:04AM +0100, Sven Luther wrote: > > On Tue, Jan 18, 2005 at 12:56:51PM +0900, Horms wrote: > > > On Mon, Jan 17, 2005 at 12:03:51PM +0100, Frank Lichtenheld wrote: > > > > On Sun, Jan 16, 2005 at 12:33:48PM +0100, Paul van Tilburg wrote: > > > > > The USB block device is known to be experimental and buggy. > > > > > CONFIG_BLK_DEV_UB=m should be set to 'n'. > > > > > > > > > > Since the ub modules takes preference of the old, though working > > > > > usb-storage, hotplug loads ub. Blacklisting ub doesn't help, loading > > > > > usb-storage doesn't work either. > > > > > I really would like for UB to be disable until proven reasonably > > > > > stable. > > > > > > > > Can someone merge this bug with #283852, plz? I'm unsure which of them > > > > to reassign. > > > > I wonder about this, would it not be enough to blacklist the UB generated > > modules in hotplug and/or discover ? > > According to Paul van Tilburg, in Bug#284952 this does not help. > Though he didn't expand on why.
Ah, i also have some second-thoughts about this, since we cannot know exactly how the user is loading the modules. I will disable it in the ppc 2.6.9/2.6.10 kernels. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]