From owner-freebsd-current@freebsd.org Fri Jul 31 06:50:21 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 01E719AE8C0 for ; Fri, 31 Jul 2015 06:50:21 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id BC665F9D; Fri, 31 Jul 2015 06:50:20 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 924D11DC2; Fri, 31 Jul 2015 06:50:19 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Fri, 31 Jul 2015 06:50:16 +0000 From: Glen Barber To: Larry Rosenman Cc: Benno Rice , freebsd-current@freebsd.org Subject: Re: pmspcv panic on boot on this box Message-ID: <20150731065016.GT90754@FreeBSD.org> References: <765D2BB8-F101-4D8C-BF1D-BB896904FB29@FreeBSD.org> <20150730201351.GH90754@FreeBSD.org> <20150730201517.GI90754@FreeBSD.org> <20150730221728.GK90754@FreeBSD.org> <452d406c68674df3834c75bd3736e6dc@thebighonker.lerctr.org> <20150731041815.GO90754@FreeBSD.org> <20150731042114.GP90754@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="NQqDiQVflaif2hna" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.23 (2014-03-12) 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: Fri, 31 Jul 2015 06:50:21 -0000 --NQqDiQVflaif2hna Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 31, 2015 at 01:33:32AM -0500, Larry Rosenman wrote: > On 2015-07-30 23:21, Glen Barber wrote: > >On Fri, Jul 31, 2015 at 04:18:15AM +0000, Glen Barber wrote: > >>On Thu, Jul 30, 2015 at 06:57:05PM -0500, Larry Rosenman wrote: > >>> On 2015-07-30 17:17, Glen Barber wrote: > >>> >On Thu, Jul 30, 2015 at 03:20:46PM -0500, Larry Rosenman wrote: > >>> >>Kernel compiling -- give mr a bit and I'll boot it and make sure it > >>> >>comes > >>> >>up. > >>> >> > >>> > > >>> >Larry, have you had any luck with this patch applied? If it resolves > >>> >your issue, I want to make sure it is included in the 10.2-RC2 build. > >>> > > >>> >Thanks. > >>> > > >>> [...] > >>> > >>> There are 3 pictures from the CURRENT panic. > >>> > >>> it STILL fails. :( > >>> > >> > >>Larry, I am sorry this is causing headaches for you, and I certainly > >>appreciate the prompt (and detailed) report, and assistance debugging > >>this. > >> > >>Would you be able to try one more test case? > >> > >>I'm interested in the behavior without the 'nodevice pmsdrv' addition to > >>your kernel configuration (effectively, removing the device from the > >>GENERIC kernel), and *without* the patch provided from Benno? > >> > > > >To be more specific on what I'm interested in, 'nodevice pmsdrv' and > >'device pmsdrv' should *both* be removed from the kernel configuration, > >and the pms(4) should only be available as a .ko module. > > > >>In particular, I'm interested in if ahd(4) attaches or if loader(8) > >>auto-loads pms(4) after the PCI IDs are detected. > >> > >>As this issue also affects the upcoming 10.2-RELEASE, your willingness > >>to help debug this is greatly appreciated, as you've tripped over > >>something that would have caused a great deal of pain after 10.2 was > >>release. > >> > >>I owe you several beers. > >> > > > >Glen > My kernel is based on GENERIC (I.E. include GENERIC). > With the nodedevice pmspcv, after boot, if I kldload pmspcv, NO PANIC. >=20 Okay. I'm interested in the behavior if the pmspcv is removed entirely (no 'nodevice' or 'device' entry). > Unfortunately, I've got a funeral to go to in Dallas (~150Mi away from ho= me) > today, Friday, and will > not be back until late Saturday (US/CDT, GMT-5). >=20 My condolences. :( I'm going to be occupied testing the 10.2-RC2 (while taking into account the pms(4) issue), so no worries regarding getting back to me. There was another report as well, so I'll parallelize as needed. > I can probably help someone with this on Sunday, but would appreciate a > real-tome conversation, as the box in question is at > a COLO facility, and does NOT have IPMI, so I need to be physically there. >=20 > Where in the world are you located, Glen? >=20 I'm in Pennsylvania. I'll email you my phone number off-list when you return if that is helpful for debugging, and we can try to streamline this. Deal with the non-computer stuff first though, please. Glen --NQqDiQVflaif2hna Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVuxqoAAoJEAMUWKVHj+KT6zgQAI6FgIV90fsNAPG/n1f3kUEY A0UjdR0lSOLlwQB6gSI9NV7UQCP+SfPVozTfbUt2zW1yX+wz/BWUT8s5FM5shqDt fomS11zH+IcAlti0YidPm5mzkLflE+c4/VyVfV+oRlCulCN1Tw8X2sD/ewyPxYz+ lCjjY3S507+aCbpzNcpIuEdjIEKv/7pBDq95Rjjr9M6iA8aZ6ccm4YQUIIo3RnbH 3l1AG1x6Ovd39JIOJQCbhpktNQ75YbFQyP1MvbZ4agmKi/5mFRPINZeT/npOlvDK qNa86twJSaAx54CBZWRnzBeAW97s2V9hbgvytVOcqvAWfuPw6c49ptWVxrUhd2hG S8PV9+rX9jKkD2ntC0rv1tMjAwqOcJx26FKte8nMQQhqJ7cPCsIVqLxzq8Ach5wS ZeQAT1i3H+BOEJVcFGVaNgF0U2kWpBb8chMf2ot7bXJxrh48Q3rCKPX8bd3r/YNz HTFRB8eA4Q2i359BdLF3vP257JY2xSNYnEqrrxlJUTea4Uegra18HbAZ35vmROnc +MjB2Cry4Km0bPn+Qn5qlVnA/F95beOpN+RFc7HoGayE0qVOqAfUY3s8383kO6Ge lLV2QL5KNNviyEaMsFZ5XvFtNcXVdYKHvsJMEBnZ9pI1QWcKpuoCSFIHzB+7xxVX Tou1yl0tIIlMyPRP7tUT =8HxX -----END PGP SIGNATURE----- --NQqDiQVflaif2hna--