From owner-freebsd-current@freebsd.org Mon Aug 3 15:44:37 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C8239AEE39 for ; Mon, 3 Aug 2015 15:44:37 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 01DF66F1 for ; Mon, 3 Aug 2015 15:44:37 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by wibud3 with SMTP id ud3so119689466wib.0 for ; Mon, 03 Aug 2015 08:44:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=AdaYSREFORK6FsiiOpHu3PFia3HhLET3ant8HRHoi1o=; b=lhd26mr+WqfLmwrZbR66/X85ig+IiJ9+0dx8pVJtK/Ybjux2UBt7uRjY6hGZH0ZLOa kbBqWRNRHyon2TwaFJqpElX0tWEUH4rCnQG5FVgmo8iY1CW3NPHerghn2yc9W+T3nKH6 qk8Q4rjx9oqlQ6zaAvOyPZVICGQs/u3jNnNP6HillO22m0YbFnB11yI5slZwWx0Odyev hNFAKx9zbMoplvhXHHSHKP5gdiIPjhH8XSGhe0u/9A4tZqxhtWrP/VwTg7ecPjcje5Z7 o/swd91KZZDDExWj4dQwJj9gSirWT0QmTnUh3ERPdSq4ZXuV2l2Q4tc+o+4Hn6iwbSiI zsRw== X-Received: by 10.180.108.35 with SMTP id hh3mr27874233wib.48.1438616675167; Mon, 03 Aug 2015 08:44:35 -0700 (PDT) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by smtp.gmail.com with ESMTPSA id lq9sm23493207wjb.35.2015.08.03.08.44.33 (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Mon, 03 Aug 2015 08:44:33 -0700 (PDT) Date: Mon, 3 Aug 2015 17:44:31 +0200 From: Mateusz Guzik To: "O. Hartmann" Cc: David Wolfskill , Navdeep Parhar , Current Subject: Re: panic in sysctl code in recent head Message-ID: <20150803154430.GA13581@dft-labs.eu> Mail-Followup-To: Mateusz Guzik , "O. Hartmann" , David Wolfskill , Navdeep Parhar , Current References: <20150801122636.GN70804@albert.catwhisker.org> <20150803172858.42d38266.ohartman@zedat.fu-berlin.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20150803172858.42d38266.ohartman@zedat.fu-berlin.de> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 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: Mon, 03 Aug 2015 15:44:37 -0000 On Mon, Aug 03, 2015 at 05:28:58PM +0200, O. Hartmann wrote: > Am Sat, 1 Aug 2015 05:26:36 -0700 > David Wolfskill schrieb: > > > On Thu, Jul 30, 2015 at 12:11:22PM -0700, Navdeep Parhar wrote: > > > A kernel built from head as of today panics with this on loading a module. > > > Does anyone else see this too? > > > .... > > > > Sorry for the delay -- but no; I have not seen it. > > > > Each of the builds listed in > > > > also involves loading (at minimum) nvidia.ko and geom_eli.ko; usually, a > > few more -- successfully. > > > > Peace, > > david > > Including FreeBSD 11.0-CURRENT #28 r286232: Mon Aug 3 16:55:05 CEST 2015 amd64, I can > bring down any of my CURRENT boxes (>= IvyBridge) by the issue of > > sysctl -a|grep tempe > > for looking after the recent temperature (all kernel have the Intel specific driver for > the temperature senors compiled in, like > > [...] > coretemp0: on cpu0 > est0: on cpu0 > coretemp1: on cpu1 > est1: on cpu1 > coretemp2: on cpu2 > est2: on cpu2 > coretemp3: on cpu3 > est3: on cpu3 > > > I haven't tried issuing the crashing command with kernsl without this module compiled in. The grep in question has no relation to whatever panic you are seeing. What you can do is show your panic (at least the backtrace) and preferably narrow the problem down to the exact revision which introduced it. -- Mateusz Guzik