> > > > I noticed a crash when I unload ethercat master's kernelmodule: > > > # /etc/init.d/ethercat start > > > .... wait a while > > > # /etc/init.d/ethercat stop > > > # dmesg > dmesg_beforcrash && sync > > > .... wait another second, and the system freezes, completly... > > > > > > Any idea? Dmesg looks like everything went fine... I also let the > > > module run for several hours, without a problem, its only on > > > unloading.. Did I made a mistake in my driver? > > > > Probably... ;-) > > > > I know this from patching new drivers by myself. Try to search from > > illegal kfree() in the exit code. My experience is, that they are the #1 > > reason for freezes. > I changed the init script and disabled restoring of modules (this way the > original e100 module isnt inserted after ec_e100 is removed...). That way I > the computer doesnt crash, I can also reinsert ec_e100, use it and remove > it again... But as soon as I insert the original e100 driver, the system > crashs... It seems that the ec_e100 driver leaves the device in an unknown > state.... Any idea?
I had the same problems with the e100 driver with the versions 2.6.24 and 2.6.26. I can´t provide a solution, since i solved it like you by not reloading the e100 driver, because i have no need to do this in the end version. I just wanted to inform you that it might is not a problem with the patch you made but a problem that already existed in the basic code of the 2.6.26 driver you used for updating the driver. Regards Christian -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01 _______________________________________________ etherlab-dev mailing list [email protected] http://lists.etherlab.org/mailman/listinfo/etherlab-dev
