I've hit this bug after installing wheezy rc1 on a desktop system with a large amount of memory. It requires manual tuning of the kernel defaults for vm.dirty* in /etc/sysctl.conf.
It took me some time to determine what was overriding my sysctl settings. I don't claim to know the best solution, but I agree with the original reporter that the current situation is not good. The so-called sane defaults "0 10 5 500" should just be removed ASAP from the script, as suggested in the first solution. This is going to bite everyone who has pm-utils installed and overrides these vm settings with sysctl. In general, it would be polite behavior if the script did not change anything if it has never been invoked with a "true" argument. If the "state_exists laptop_mode_default" check does not satisfy this requirement, then explicit logic should be added to guarantee it. A more complete solution, including moving *all* the hard-coded values to somewhere in /etc, seems like it would be highly desirable. When I eventually install wheezy on a laptop I will certainly need a reasonable way to change the 40/60% dirty settings included in this script. (JMHO, but those settings seem like complete madness as a default.) Allowing the laptop-mode script to manipulate the dirty*bytes settings instead of *ratio would also be a feature to consider... Thanks for all your work! Regards, David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
