summaryrefslogtreecommitdiffstats
path: root/sys/nfsserver
diff options
context:
space:
mode:
authormav <mav@FreeBSD.org>2009-11-14 16:20:07 +0000
committermav <mav@FreeBSD.org>2009-11-14 16:20:07 +0000
commit6ca2296a1ba7d79ea4c890c09191fb27e9ef7bdf (patch)
tree97a6ad1a74b5e163a2d7f2d8250349461df60c3a /sys/nfsserver
parentb056f85a3c5445b7eea6adc5e38992e1d71014e5 (diff)
downloadFreeBSD-src-6ca2296a1ba7d79ea4c890c09191fb27e9ef7bdf.zip
FreeBSD-src-6ca2296a1ba7d79ea4c890c09191fb27e9ef7bdf.tar.gz
Previous solution appeared to be unsufficient. After additional testing
I have found that it is not only desktop CPUs problem. but mobile also. Probably AP on laptops just started initially at lower frequency, hiding the problem. Disable frequency validation by default, for systems with more then one CPU, until we can implement it properly. It looks like making more harm now then benefits. Add 'hw.est.strict' loader tunable to control it. Now my iXsystems Invincibook is able to run at 800MHz lowest frequency, instead of 1200MHz before, when 800MHz was incorrectly reported invalid.
Diffstat (limited to 'sys/nfsserver')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud