From owner-freebsd-current@freebsd.org  Tue Sep  1 20:30:56 2015
Return-Path: <owner-freebsd-current@freebsd.org>
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 906B79C85E2
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Tue,  1 Sep 2015 20:30:56 +0000 (UTC)
 (envelope-from cse.cem@gmail.com)
Received: from mail-yk0-f180.google.com (mail-yk0-f180.google.com
 [209.85.160.180])
 (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 548876BB;
 Tue,  1 Sep 2015 20:30:56 +0000 (UTC)
 (envelope-from cse.cem@gmail.com)
Received: by ykax124 with SMTP id x124so2563569yka.2;
 Tue, 01 Sep 2015 13:30:48 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=mime-version:reply-to:in-reply-to:references:date:message-id
 :subject:from:to:cc:content-type;
 bh=MBCyk7nv60WwpVkAhHOo0CbOqnfUdg50wQJJTr/QSO0=;
 b=MehF0qB0+lrdKtoqt0uUTEtRiIPaeK2cnESNmAfjao34QE1zv/W2Nt7+zXIjvgKrNF
 a+x+yRzEK5vfdkfID5+h8PgAFwxgHFn5XBcgFjFe4TybX8TollwXJIpvcMgPdEauU2JM
 ynq7yQxx9qZfXA6+vjp1IyAahSKpqu6sFr4S5hXxoVRXrifjJGR2IT+mnKlLjVgXOCSc
 QIhyupSp2W9zQHIm2/Nf+/uiJbZNFEAo9qUZ6jj2b8gZ5oOx10aav61EQ7/RDFS4FXl5
 9sS52U0Su0xxJ75Qe7gNkbUevSgOMSAvZa2q1ozZg8dCTSFv2aAeV+bAjL3AdPaNA8QM
 vDrA==
X-Received: by 10.129.78.12 with SMTP id c12mr29479413ywb.144.1441139448797;
 Tue, 01 Sep 2015 13:30:48 -0700 (PDT)
Received: from mail-yk0-f172.google.com (mail-yk0-f172.google.com.
 [209.85.160.172])
 by smtp.gmail.com with ESMTPSA id s66sm18530079ywe.49.2015.09.01.13.30.48
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Tue, 01 Sep 2015 13:30:48 -0700 (PDT)
Received: by ykdg206 with SMTP id g206so2563076ykd.1;
 Tue, 01 Sep 2015 13:30:48 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.13.193.1 with SMTP id c1mr31157732ywd.172.1441139448369;
 Tue, 01 Sep 2015 13:30:48 -0700 (PDT)
Reply-To: cem@FreeBSD.org
Received: by 10.37.48.134 with HTTP; Tue, 1 Sep 2015 13:30:48 -0700 (PDT)
In-Reply-To: <1907622.HsVbIIOtmz@ralph.baldwin.cx>
References: <CAG6CVpU4dP3jFag8A1fLaYpPwqSeErL54iERL5iFMAKbmW=Bdw@mail.gmail.com>
 <1907622.HsVbIIOtmz@ralph.baldwin.cx>
Date: Tue, 1 Sep 2015 13:30:48 -0700
Message-ID: <CAG6CVpUamGe3RurMMeQMqgimeMjwPNzcyf_Oc23ODTnvk6OHMA@mail.gmail.com>
Subject: Re: Panic on boot during scan with pmspcv
From: Conrad Meyer <cem@FreeBSD.org>
To: John Baldwin <jhb@freebsd.org>
Cc: freebsd-current <freebsd-current@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Sep 2015 20:30:56 -0000

On Mon, Aug 31, 2015 at 6:20 PM, John Baldwin <jhb@freebsd.org> wrote:
> Probably pCardInfo is NULL.
>
> Looking at the pms driver source is making my stomach churn, but I don't
> see anything obvious.  The field is set during attach, so it shouldn't be
> NULL when the intrhook runs.  Do you have any other storage devices on
> this box?  If so, I would try to kldload the pms driver after you have
> booted far enough to setup dumps (either that or setup remote kgdb).
>

In fact, I don't have any storage devices attached to the PMC
controller on this box. So it's a pretty low priority for me other
than not panicing. I've configured the BIOS to legacy boot and the
issue no longer crops up.

I just wanted to register the stack and unpleasantness on -CURRENT@ in
case someone else runs into it too and/or PMC is reading and can
diagnose/fix it.

Best,
Conrad