From owner-freebsd-current@FreeBSD.ORG Fri Apr 19 17:55:09 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 88786821 for ; Fri, 19 Apr 2013 17:55:09 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 4FFEDAE0 for ; Fri, 19 Apr 2013 17:55:09 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.80.1) for freebsd-current@freebsd.org with esmtp (envelope-from ) id <1UTA0P-000pKX-SK>; Fri, 19 Apr 2013 14:01:29 +0200 Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198]) by inpost2.zedat.fu-berlin.de (Exim 4.80.1) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1UTA0P-000EBu-PW>; Fri, 19 Apr 2013 14:01:29 +0200 Subject: sysctl -a: Crashes CURRENT From: "O. Hartmann" To: freebsd-current Content-Type: text/plain; charset="us-ascii" Date: Fri, 19 Apr 2013 14:01:29 +0200 Message-ID: <1366372889.1828.7.camel@telesto> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Originating-IP: 130.133.86.198 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Apr 2013 17:55:09 -0000 trying to read the temperature on an Intel Core-i7 3930K box (10.0-CURRENT #2 r249647: Fri Apr 19 13:22:41 CEST 2013 amd64) via sysctl -a|grep tempe crashes sporadically the system due to panic/page fault and dumps core. I'm not able to reproduces this behaviour by intention, as I stated at the beginning, the crash occurs sporadically. That also happened once on a Core2Duo based box (Intel E8400), but also not being reproducable. First occurence was over Easter. Since all the boxes in question use the Intel temperature sensor driver in-core, the question is whether there is a known issue and I better do not use the driver (device coretemp). Since I'm also incapable of triggering this error by will, I'm sorry not providing more informations. the last incident was during kernel compilation, but at this very moment, I recompile also a kernel and try trigering the crash - but it doesn't work. Oliver