Dag-Erling Smorgrav wrote: > Robert Watson <rwatson_at_FreeBSD.org> writes: > >> |-----------------+-------------+-------------+--------------------------| >> | Panic on | | | If a network device | >> | load/unload a | | | driver, possibly any | >> | kernel module | | | driver, is linked into | >> | for a driver | Patch | Maxime | the kernel and then | >> | already | submitted | Henrion | loaded and unloaded as a | >> | statically | | | module, the kernel will | >> | linked into the | | | panic. This has been | >> | kernel. | | | observed with both if_dc | >> | | | | and if_fxp. | >> |-----------------+-------------+-------------+--------------------------| > > I'm unable to reproduce this; kldload refuses to load a module which > is already present, and if you try to preload a driver which is > compiled into the kernel, the kernel will refuse to register it. I've seen panics like this happen with loading such duplicate modules via /boot/loader.conf (i.e. not with kldload from the console.) Is this what you mean by "preload"? It doesn't happen for all modules, but it does for some. I think I remember random.ko being one that caused problems, but I'm not sure, and can't test right now (away from the machine). Lars -- Lars Eggert <larse_at_isi.edu> USC Information Sciences Institute
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:07 UTC