Issue #2253 has been reported by Juan Francisco Cantero Hurtado.
----------------------------------------
Bug #2253: Weird behavior of some modules
http://bugs.dragonflybsd.org/issues/2253
Author: Juan Francisco Cantero Hurtado
Status: New
Priority: High
Assignee:
Category:
Target version:
I've had this bug in my notes from one or two months. I report this now because
I think is related with #2252 but the problem is more wide than the specific
modules. My problem is with dsched_fq.
Steps:
- Delete or comment all lines related to dsched in loader.conf and sysctl.conf.
- Reboot the system.
- Log in the system with the root account.
- Run "sysctl dsched.policies":
# dsched.policies = noop fq
- Run "kldstat". It doesn't show the module dsched_fq loaded.
- Run "sysctl -w dsched.policy.default=fq":
# noop -> fq
All works perfect, right?. More steps:
- Add dsched_fq to your loader.conf file.
- Reboot the system.
- Log in the system with the root account.
- Run "sysctl dsched.policies":
# dsched.policies = noop
- Run "kldstat". It shows the module dsched_fq loaded.
- Run "sysctl -w dsched.policy.default=fq":
# noop -> noop
I updated the past week the base and kernel (i386)
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://bugs.dragonflybsd.org/my/account
