> I assume you are merely refering to the detailed init-script activities > than to particular runlevel. I don't have the ehci-hcd included anywhere > for automated loading. So the system came up with usbcore and ohci-hcd > loaded. I've rmmod'ed the ohci-hcd and modprobed the ehci-hcd which was > hitting the poisoned memory. Loading the ehci-hcd with the ohci still > there was fine.
So it's likely you were hitting exactly the same thing I was seeing, since you removed hcds and saw the error when loading one later. For me, it didn't matter what hcd got loaded first or second. Greg said he had the start of a handle on this. > See this too. Situation improved for me if I do always keep the > following order (read: workaround to avoid the symptoms): > > - wait until device is idle (module usecount==0) > - unplug the device > - rmmod the driver > > Any change to this scheme and I'm running into trouble sooner or later. I think that was what I noticed too, for usb drivers. Cardbus was another story; all but completely unusable. - Dave ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
