On Thursday 13 January 2005 12:51 pm, David Hollis wrote: > On Wed, 2005-01-12 at 19:41 -0800, David Brownell wrote: > > I didn't realize FC3 was mounting this drive, else I might have done > > things differently ... but I think everyone will agree that oopsing > > is not OK. See the following dmesg trace. > > > > I've seen a lot of messages about similar failures lately, as if > > maybe more distros are automounting removable drives. But I also > > remember seeing a lot of fixes go by; does this oops have a fix? > > Not exactly a fix, but did you unmount the drive before removing it?
No, the first I knew about this drive automagically being mounted was seeing the OOPS. If I'd know it was doing that, I'd have manually unmounted it; that's what I meant by doing things "differently"! > With my Sandisk Mini-Cruzer, I don't have any Oops-es but I do always > unmount it prior to unplugging it. It certainly shouldn't Oops on > unmounted-unplug of course. And it's gnome-volume-manager that handles > the automounting BTW. It shouldn't oops if it's mounted either, though ... and it also shouldn't lock up the USB subsystem, forcing a reboot. - Dave ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel