Date: Thu, 25 Sep 2003 15:44:47 -0700
From: Greg KH <greg@kroah.com>
To: Philippe Troin <phil@fifi.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops in vanilla 2.4.22 serial-usb driver
Message-ID: <20030925224447.GB30186@kroah.com>
References: <87llsdy01v.fsf@ceramic.fifi.org> <20030925185039.GB29088@kroah.com> <87eky4hauq.fsf@ceramic.fifi.org> <20030925210104.GB29680@kroah.com> <87ad8sh54y.fsf@ceramic.fifi.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87ad8sh54y.fsf@ceramic.fifi.org>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1130
Lines: 32

On Thu, Sep 25, 2003 at 03:31:25PM -0700, Philippe Troin wrote:
> Greg KH <greg@kroah.com> writes:
> 
> > On Thu, Sep 25, 2003 at 01:27:57PM -0700, Philippe Troin wrote:
> > > > > BTW, is there any way to restart khubd without rebooting?
> > > > 
> > > > Nope, sorry.
> > > 
> > > Are there any technical reasons behind that, or that just that it is
> > > not implemented?
> > 
> > It's a bit hard to restart a kernel thread that is oopsed :)
> 
> Yes, but still, with a completely modular USB subsystem, removing all
> the modules and reinsrting them (when possible) restarts khubd... So
> if it is possible with modules, it ought to be possible with
> monolithic USB...

Usually when khubd oopses like this, a usb module is stuck with a
incremented reference count which prevents the usbcore from being able
to be unloaded.

But hey, patches are always accepted :)

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/