There's no guarantee that a kernel module has cleaned up correctly after itself when it's unloaded (and left the hardware in the expected state) either so hence the request for a reboot. There is a further complication because you are dealing with a binary module so you can't inspect the code thus the kernel will mark itself tainted from the moment the module is loaded until the computer is shutdown. Typically once a kernel module is loaded you don't go and unload it (unless you are kernel developer testing something).
-- Unnecessary Reboots after Updates https://bugs.launchpad.net/bugs/115092 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
