On Jan 2, 2008, at 3:23 PM, Scott James Remnant wrote: > Sorry, but the suggested fix here is incorrect. > > All the powernowd stop script does is send the TERM signal to the > daemon, which is already performed by the sendsigs script; and set the > scaling governor to "performance", which is only done so when the > daemon > is stopped by hand (e.g. when the package is removed) the effect is > undone. > > This should have absolutely no effect on the ability of the computer to > be rebooted or powered off.
IIRC, the sendsigs script runs much later. I think that when I reported this, I tried sending the TERM at several different places in the reboot/shutdown sequence, and it really made a difference in observable behavior. > If this does, this is a bug in the module itself and should be fixed > there -- not by adding unnecessary symlinks. "Package $FOO misbehaves only when some code is executed in the kernel, regardless of any lack of problems with that code in the absence of Package $FOO, so the bug must be in the kernel, and not in Package $FOO." OK, understood. -- Feisty can't reboot after adding p4-clockmod to /etc/modules https://bugs.launchpad.net/bugs/118015 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
