From owner-freebsd-bugs@FreeBSD.ORG Sun Sep 9 07:20:14 2012 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6492B106566B for ; Sun, 9 Sep 2012 07:20:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4F7C78FC14 for ; Sun, 9 Sep 2012 07:20:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q897KE2U063968 for ; Sun, 9 Sep 2012 07:20:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q897KEv8063960; Sun, 9 Sep 2012 07:20:14 GMT (envelope-from gnats) Date: Sun, 9 Sep 2012 07:20:14 GMT Message-Id: <201209090720.q897KEv8063960@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Mark Johnston Cc: Subject: Re: kern/170627: Kernel memory leak when polling cpu temperature via coretemp kernel module.] X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mark Johnston List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Sep 2012 07:20:14 -0000 The following reply was made to PR kern/170627; it has been noted by GNATS. From: Mark Johnston To: bug-followup@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 ----- Date: Sun, 9 Sep 2012 09:39:01 +0300 From: Remme To: Mark Johnston 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 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 -----