On Wed, Jul 16, 2003 at 01:15:12PM -0700, Mike Fedyk wrote:
> On Tue, Jul 15, 2003 at 07:31:50PM -0700, Greg KH wrote:
> > On Tue, Jul 15, 2003 at 06:46:50PM -0700, Mike Fedyk wrote:
> > > On Tue, Jul 15, 2003 at 06:37:43PM -0700, Greg KH wrote:
> > > > On Tue, Jul 15, 2003 at 06:29:48PM -0700, Mike Fedyk wrote:
> > > > > Here's a nice oops for you guys.
> > > > >
> > > > > Hotplug is the trigger. I can't reproduce without hotplug.
> > > > >
> > > > > hotplug tries to load ohci, ehci, and finally uhci (the correct module), it
> > > > > oopses for each driver with hotplug, but if I try without hotplug ('apt-get
> > > > > remove hotplug' before rebooting), I can load all three usb drivers with no
> > > > > oops.
> > > >
> > > > If you just load these drivers by hand, does the oops happen?
> > > >
> > >
> > > I didn't look into the hotplug scripts to see which hotplug modules (and
> > > they are modules for me) were being loaded and in which order.
> >
> > It should just do:
> > modprobe -q ehci-hcd >/dev/null 2>&1
> > modprobe -q ohci-hcd >/dev/null 2>&1
> > modprobe -q uhci-hcd >/dev/null 2>&1
> >
> > That's what the latest hotplug package has in it. I don't know what
> > Debian has lately...
> >
> > > I did load the usb drivers by hand with no oops though.
> >
> > That's really strange.
> >
> > > > Can you enable debugging in the kobject code, or the driver base code to
> > > > try to get some better debug messages of what is going on?
> > > >
> > >
> > > Please tell me which file that's in, and what I need to change, or give a
> > > patch.
> >
> > Here's a patch that I always run with. It is pretty verbose, but helps
> > me out a lot in debugging and development.
> >
> > Let us know if it shows anything interesting.
> >
> Ok, I only see it when the system is booting, and after looking at the
> hotplug script in init.d there is different behaviour on boot, and on later
> invocations.
Ok, here are some more files it is referencing to:
This archive was generated by hypermail 2b29 : Wed Jul 23 2003 - 22:00:26 EST