From owner-freebsd-infiniband@freebsd.org Thu Apr 21 14:19:20 2016 Return-Path: Delivered-To: freebsd-infiniband@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 DBBE2B1634B for ; Thu, 21 Apr 2016 14:19:20 +0000 (UTC) (envelope-from justin@postgresql.org) Received: from meldrar.postgresql.org (meldrar.postgresql.org [IPv6:2a02:c0:301:0:ffff::31]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.postgresql.org", Issuer "Gandi Standard SSL CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A26F01F38 for ; Thu, 21 Apr 2016 14:19:20 +0000 (UTC) (envelope-from justin@postgresql.org) Received: from 82-69-92-196.dsl.in-addr.zen.co.uk ([82.69.92.196] helo=[172.16.1.14]) by meldrar.postgresql.org with esmtpsa (TLS1.0:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1atFRp-0000e5-6H for freebsd-infiniband@freebsd.org; Thu, 21 Apr 2016 14:19:18 +0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Kernel panic (page fault) on 10.3-STABLE with IB & VIMAGE modules From: Justin Clift In-Reply-To: <210EB5F8-DEC1-4F5E-9CC7-003AF3784B50@postgresql.org> Date: Thu, 21 Apr 2016 15:19:13 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <210EB5F8-DEC1-4F5E-9CC7-003AF3784B50@postgresql.org> To: freebsd-infiniband@freebsd.org X-Mailer: Apple Mail (2.1878.6) X-Pg-Spam-Score: -2.9 (--) X-BeenThere: freebsd-infiniband@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Infiniband on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2016 14:19:21 -0000 On 21 Apr 2016, at 15:16, Justin Clift wrote: > Hi all, >=20 > Have been hitting a kernel panic (page fault) with the IB modules = loaded > on 10.3-STABLE. (compiled multiple times over the last few days, all = panicing) >=20 > Spent several hours narrowing down the cause, and it's definitely a = bad > interaction between the IB modules (unsure which) + the "VIMAGE" = module. Forgot to mention, it's 100% reproducible, and very easily. All that = needs to be done is have an interface (eg ib0) be in IPoIB mode with an IP = assigned. (eg 10.10.100.1) When that interface is pinged from another host (eg "ping 10.10.100.1") = the kernel panic immediately happens. Every time. ;) + Justin -- "My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there." - Indira Gandhi