I've found a funny behaviour in the Linux kernel (version 3.19.0). We were testing a network driver and the system hung completely, it didn't even responded to SysRq commands. After the reboot, the driver we were testing still appeared as loaded, even when it's not configured to load at boot. What's worse, it couldn't be removed neither with
modprobe -r nor
rmmod -f. The kernel log didn't show anything helpful.
We tried to reboot again and again, even blacklisting the module but it always appeared as a loaded module. The only solution we found was to reinstall the kernel (
apt-get remove/install linux-image-$(uname-r)). It then disappeared and everything started working perfectly again.
Does anyone know what could be happening here and why did the kernel load the module even when explicitly told to not do so?
Edit: the reconfiguration didn't fix it, I had to reinstall the kernel package.