[driverloader] Fedora core driverloader kernel crash, latest Version.

[Ian Hutchinson]

	Just FYI, I have found that the latest generic driverloader 1.66
appears to be improved with respect to the rpm distribution
1.65_k2.4.22_1.2174.nptl-1fdr. However, it is not perfect.

I tried out the source 1.66 driverloader version with a plain 2.4.26 linux
kernel. It behaves AFAIK the same with the 2.4.26 as it does if I use the
generic source 1.66 version with the 2.4.22-1.2174 kernel.

Both of them seem to show fewer (and perhaps none) of the
> > > Apr 18 22:32:22 localhost kernel: driverloader:
> > > ndisWrapCheckForHangTimerFunc_stk:
> PCI-0000:02:02.0-8086:1043-8086:2551 hung,
errors.

The driverloader module seems to be able to be modprobe and modprobe -r
inserted and removed without crashing PROVIDED that the thinkpad is not
suspended (using apm) while driverloader module is installed. However, if
the machine is suspended with the driverloader module installed, then any
subsequent attempt to modprobe -r remove it, causes a kernel crash.

Therefore the driverloader module is still buggy, but at least now I can
avoid the bugs by ensuring that the module is removed prior to each
suspend (which can be done automatically only by changing the scripts,
which I have done.)

	Ian Hutchinson
	http://www.psfc.mit.edu/people/hutch/


> > >
> > > Using driverloader stock distribution for Fedora core: 2.4.22-1.2174
> > > Stock Fedora kernel
> > >
> > >   $ cat /proc/version
> > > Linux version 2.4.22-1.2174.nptl (bhcompile at tweety.devel.redhat.com)
> > (gcc
> > > version 3.2.3 20030422 (Red Hat Linux 3.2.3-6)) #1 Wed Feb 18 16:38:32
> > EST
> > > 2004
> > >
> > > Thinkpad T41. Centrino, with windows driver for the wireless.
> > >
> > > Sometimes the driver will hang giving messages like this:
> > >
> > > Apr 18 22:32:18 localhost kernel: PCI: Found IRQ 11 for device 02:02.0
> > > Apr 18 22:32:18 localhost kernel: PCI: Sharing IRQ 11 with 00:1d.2
> > > Apr 18 22:32:18 localhost kernel: PCI: Sharing IRQ 11 with 00:1f.1
> > > Apr 18 22:32:19 localhost kernel: eth1: New link status: Disconnected
> > > (0002)
> > > Apr 18 22:32:19 localhost kernel: driverloader: ndisSetInformation:
> > > 802_11_ENCRY
> > > PTION_STATUS st=FAILURE retrying..
> > > Apr 18 22:32:19 localhost kernel: driverloader: ndisSetInformation:
> > > 802_11_ENCRY
> > > PTION_STATUS st=FAILURE retrying..
> > > Apr 18 22:32:20 localhost kernel: driverloader: ndisSetInformation:
> > > 802_11_ENCRY
> > > PTION_STATUS st=FAILURE W=0 N=4
> > > Apr 18 22:32:20 localhost kernel: driverloader: ndisSetInformation:
> > > 802_11_AUTHE
> > > NTICATION_MODE st=FAILURE W=0 N=0
> > > Apr 18 22:32:20 localhost kernel: driverloader: ndisSetInformation:
> > > 802_11_AUTHE
> > > NTICATION_MODE st=FAILURE W=0 N=0
> > > Apr 18 22:32:20 localhost kernel: eth1: Error -5 setting
> authentication
> > > mode
> > > Apr 18 22:32:22 localhost kernel: driverloader:
> > > ndisWrapCheckForHangTimerFunc_stk:
> PCI-0000:02:02.0-8086:1043-8086:2551
> > > hung,
> > > resetting
> > >
> > > With the older version, one could
> > > modprobe -r driverloader
> > > and then reinstall, and that would fix it.
> > >
> > > With this version, however, if you try to modprobe -r driverloader,
> the
> > > whole
> > > system hangs, and has to be power cycled to restart.
> > >
> > > Obviously this is a fairly serious bug.
> > >
> > > Be nice if it were fixed, or else someone could tell how to avoid it.
> > >
> > > 	Ian Hutchinson
> > > 	http://www.psfc.mit.edu/people/hutch/
> > >
> > > _______________________________________________
> > > driverloader mailing list
> > > driverloader at lists.linuxant.com
> > > https://www.linuxant.com/mailman/listinfo/driverloader
> >
>