Re: Overheating attributed to Freebsd --sysctl variables not available--

From: Jud (judmarc_at_fastmail.fm)
Date: 11/04/03

  • Next message: nw1: "Re: Overheating attributed to Freebsd --sysctl variables notavailable--"
    To: nw1 <network101@covad.net>, peter lageotakes <plageotakes@yahoo.com>
    Date: Mon, 03 Nov 2003 21:53:29 -0500
    
    

    On Mon, 3 Nov 2003 19:57:38 -0500, nw1 <network101@covad.net> wrote:

    >
    >
    >> What version of FreeBSD are you using?
    >> Did you compile amp into the kernel?
    >
    > I think you're not understanding what I posted @
    > http://69.3.136.141/freebsd/installation/sysctl_variables_missing
    >
    > The first line has what version I'm running. The entire document @
    > http://69.3.136.141/freebsd/installation/sysctl_variables_missing
    > implies; this was a
    > running system with no serious issues; meaning; the sysctl items I'm
    > speaking of were in
    > fact available and working.
    >
    > If i can figure out how to make these sysctl variables available, I can
    > set them like they
    > were before, hence my overheating problem is solved.
    >
    > See what I mean?
    >
    >>
    >> --- nw1 <network101@covad.net> wrote:
    >> > The problem can be viewed @:
    >> >
    >> http://69.3.136.141/freebsd/installation/sysctl_variables_missing
    >> >
    >> > Basically, the machine is overheating (I believe)
    >> > because the cpu's aren't cycling down.
    >> > Previously I was able to cycle the processors down
    >> > with the following sysctl variables:
    >> >
    >> > machdep.apm_suspend_delay:
    >> > machdep.apm_standby_delay:
    >> >
    >> > however, for some reason those variables currently,
    >> > aren't any where to be found by the
    >> > up_and_running system. Please use the hyperlink
    >> > above for details.
    >> >
    >> > Thanks for reading. All feedback is welcome.

    You may want to have a look at /usr/ports/sysutils/fvcool. (If you'd like
    a script to run it on startup, Dr. Matthew Seaman posted one to the
    mailing list some months ago - January?)

    Jud
    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"


  • Next message: nw1: "Re: Overheating attributed to Freebsd --sysctl variables notavailable--"

    Relevant Pages

    • FreeBSD Status report for Oct-Dec 2003
      ... Bluetooth stack for FreeBSD ... Not much to report. ... Bluetooth kernel modules appear to be stable. ... concerns and some src committers are willing to commit the patches. ...
      (freebsd-current)
    • FreeBSD Status Report for Oct-Dec 2003
      ... Bluetooth stack for FreeBSD ... Not much to report. ... Bluetooth kernel modules appear to be stable. ... concerns and some src committers are willing to commit the patches. ...
      (freebsd-hackers)
    • FreeBSD Status Report for Oct-Dec 2003
      ... Bluetooth stack for FreeBSD ... Not much to report. ... Bluetooth kernel modules appear to be stable. ... concerns and some src committers are willing to commit the patches. ...
      (freebsd-stable)
    • RE: FreeBSD 4.11 P13 Crash
      ... I do not want to jinx myself, but after back revving to FreeBSD 4.9 + ... think it is related to IPFilter in conjunction with 4 Intel nics and/or ... page fault while in kernel mode ... Okay this time my kernel was recompiled so there are no modules to ...
      (freebsd-hackers)
    • Re: 5.3 interrupt storm (atapicam) and I/O error
      ... attached you will find a copy of my custom kernel ... config which did work without any issue under FreeBSD ... The following hardware configuration *won't* cause ... * harddrive attached to IDE channel #1 ...
      (freebsd-questions)