Project

General

Profile

Actions

Bug #2253

closed

Weird behavior of some modules

Added by juanfra684 over 12 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Category:
-
Target version:
Start date:
12/05/2011
Due date:
% Done:

0%

Estimated time:

Description

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)

Actions #1

Updated by tuxillo over 2 years ago

  • Description updated (diff)
  • Status changed from New to Closed
Actions

Also available in: Atom PDF