Re: [ANNOUNCE] udev 021 release

[Greg KH]

On Wed, Mar 03, 2004 at 10:58:56PM -0500, Bill Nottingham wrote:
> Greg KH (greg@xxxxxxxxx) said: 
> > Sorry, but you're a bit late.  We've been moving this way since before
> > 2.4.0.
> > 
> > The fact that module unload even works today is a blessing due to all of
> > the well-documented issues involved.  I doubt any distro will enable
> > module unloading because of it.
> 
> So, then, answer this question. In previous kernels, 2.4 and otherwise,
> a driver or piece of hardware may get into a 'confused' state. You unload
> the driver, reload it, it resets, everything is peachy.
> 
> How do I reinitialize a driver or hardware in your 'no-unload'
> scenario?

Disconnect the hardware device.  Oh, you don't have a PCI hotplug
system, well get one :)

Seriously, sure, try to unload the module.  But please refer to all of
the different threads on lkml during the 2.5 development cycle about
module unloading.  Also note the way that module unloading might be done
in 2.7 (by keeping the old memory around, and never freeing it...)

Also realize that it's better to fix the driver in a situation like you
mention.  Unloading the driver is often times not a viable solution for
a lot of people (like if your scsi driver is also the one holding your
root disk...)

thanks,

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