Date: Tue, 31 Mar 2015 01:41:04 +0300 From: Gleb Smirnoff <glebius@FreeBSD.org> To: Hans Petter Selasky <hps@selasky.org> Cc: rrs@FreeBSD.org, freebsd-current@freebsd.org Subject: Re: Panic on current amd64 Message-ID: <20150330224104.GZ64665@glebius.int.ru> In-Reply-To: <5519CE6C.10600@selasky.org> References: <201503282202.t2SM2cAb004263@pozo.com> <20150330211943.GV64665@FreeBSD.org> <5519CE6C.10600@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 31, 2015 at 12:30:04AM +0200, Hans Petter Selasky wrote: H> On 03/30/15 23:19, Gleb Smirnoff wrote: H> > On Sat, Mar 28, 2015 at 03:02:28PM -0700, Manfred Antar wrote: H> > M> I get the following panic on current svn ver r280793: H> > M> H> > M> Sat Mar 28 14:41:28 PDT 2015 H> > M> H> > M> FreeBSD/amd64 (pozo.com) (ttyu0) H> > M> H> > M> panic: Invalid CPU in callout 16 H> > H> > The same happened to me in the OFED code. After investigation H> > it appeared that for some unknown reason, the OFED code used H> > /usr/include/sys/callout.h instead of SYSDIR/sys/callout.h, H> > that yield in wrong value passing as parameter. H> > H> > I failed to reproduce the problem. :( So, the fix is a rebuild H> > of kernel. But the right fix is to understand what went wrong H> > in the previous build. H> H> How did you compile the OFED stuff? Did you set the SYSDIR variable when H> building? I just have this in my kernel config: options OFED device mlxen -- Totus tuus, Glebius.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150330224104.GZ64665>