kern/170627: Kernel memory leak when polling cpu temperature via coretemp kernel module.]

[Mark Johnston]

The following reply was made to PR kern/170627; it has been noted by GNATS.

From: Mark Johnston <markjdb at gmail.com>
To: bug-followup at freebsd.org
Cc:  
Subject: Re: kern/170627: Kernel memory leak when polling cpu temperature via
 coretemp kernel module.]
Date: Sun, 9 Sep 2012 03:17:31 -0400

 Forwarding so that this gets logged. The PR can be closed.
 
 ----- Forwarded message from Remme <adscomplex at gmail.com> -----
 
 Date: Sun, 9 Sep 2012 09:39:01 +0300
 From: Remme <adscomplex at gmail.com>
 To: Mark Johnston <markjdb at gmail.com>
 Subject: Re: kern/170627: Kernel memory leak when polling cpu temperature via coretemp kernel module.
 
 Hi Mark,
 
 Please cancel this report.
 Sorry for taking your time - but at the first sight coretemp was the reason.
 (Module unload fixed a problem - but only for a first 12-24 hours.).
 The reason for panic was a sphinxsearch (searchd).
 At this moment we are downgraded it to 0.9.9 and this seems solved a kernel
 panic problem.
 But we still have a growing active memory issue.
 
 Thank you for your time and attention.
 WBR,
 Max.
 
 
 On Sun, Sep 9, 2012 at 2:16 AM, Mark Johnston <markjdb at gmail.com> wrote:
 
 > Hi Max,
 >
 > Why do you think that coretemp is causing the memory leak? As far as I
 > can see, polling the coretemp sysctls shouldn't cause any memory to be
 > allocated at all - coretemp basically just reads a bunch of MSRs. Just
 > for fun, I tried running something like
 >
 > while true; do
 >     for n in $(jot - 0 $(sysctl -n hw.ncpu)); do
 >         sysctl -q dev.cpu.${n}.temperature >/dev/null 2>&1
 >         sysctl -q dev.cpu.${n}.coretemp >/dev/null 2>&1
 >     done
 > done
 >
 > for a few hours and didn't see any problems.
 >
 > What panic are you getting? How exactly are polling the temperature
 > sensors - which sysctls are you reading?
 >
 > Thanks,
 > -Mark
 >
 
 ----- End forwarded message -----