From owner-freebsd-current@FreeBSD.ORG Mon Mar 30 22:29:23 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9A60BC07; Mon, 30 Mar 2015 22:29:23 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5A0B1169; Mon, 30 Mar 2015 22:29:23 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 47B5F1FE023; Tue, 31 Mar 2015 00:29:18 +0200 (CEST) Message-ID: <5519CE6C.10600@selasky.org> Date: Tue, 31 Mar 2015 00:30:04 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Gleb Smirnoff , Manfred Antar Subject: Re: Panic on current amd64 References: <201503282202.t2SM2cAb004263@pozo.com> <20150330211943.GV64665@FreeBSD.org> In-Reply-To: <20150330211943.GV64665@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: rrs@FreeBSD.org, freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 30 Mar 2015 22:29:23 -0000 On 03/30/15 23:19, Gleb Smirnoff wrote: > On Sat, Mar 28, 2015 at 03:02:28PM -0700, Manfred Antar wrote: > M> I get the following panic on current svn ver r280793: > M> > M> Sat Mar 28 14:41:28 PDT 2015 > M> > M> FreeBSD/amd64 (pozo.com) (ttyu0) > M> > M> panic: Invalid CPU in callout 16 > > The same happened to me in the OFED code. After investigation > it appeared that for some unknown reason, the OFED code used > /usr/include/sys/callout.h instead of SYSDIR/sys/callout.h, > that yield in wrong value passing as parameter. > > I failed to reproduce the problem. :( So, the fix is a rebuild > of kernel. But the right fix is to understand what went wrong > in the previous build. > Hi, How did you compile the OFED stuff? Did you set the SYSDIR variable when building? --HPS