From owner-freebsd-current@FreeBSD.ORG  Tue Aug  6 05:53:56 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 6E69088E;
 Tue,  6 Aug 2013 05:53:56 +0000 (UTC)
 (envelope-from gljennjohn@googlemail.com)
Received: from mail-bk0-x22a.google.com (mail-bk0-x22a.google.com
 [IPv6:2a00:1450:4008:c01::22a])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id C46FB292B;
 Tue,  6 Aug 2013 05:53:55 +0000 (UTC)
Received: by mail-bk0-f42.google.com with SMTP id jk14so1277694bkc.15
 for <multiple recipients>; Mon, 05 Aug 2013 22:53:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=googlemail.com; s=20120113;
 h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to
 :x-mailer:mime-version:content-type:content-transfer-encoding;
 bh=pNUTzaZa0XFUgPDetEcTMr/B/Wc3pbcz2Fbwq7QsgYg=;
 b=vadfhJnqJI1pcI3ixpb7dGHNGveF9DlopzZGvd7NwTE1mGsJ/y2QONbdlqymAg35Ax
 a0OhavejMntYE2Ytj2g18cksVAFEahNk1TG/UoHEnEl+VWtJL4KL5elokvO/gobxQb2q
 1ShkZPm0olx+bKYDLk4Di5P/XDzTtoXKPoP0hB8gFMNVq4NF7/SIQiTKLKyhQBF+tj7r
 k/BgSC4FjjAc83s+K2mQ62qyvsnpzZKlEpHWid04wCnIJueVpqyeocTAq1HXtZ2lHJWE
 7kPi5iXqpdFUamq658elZnJcaQOEnlnVxWgE6XSO3Hbk48ckCPJM3OgiidiveEzehRRd
 tJGA==
X-Received: by 10.204.55.13 with SMTP id s13mr3264932bkg.170.1375768433886;
 Mon, 05 Aug 2013 22:53:53 -0700 (PDT)
Received: from ernst.home (p4FCA7DE8.dip0.t-ipconnect.de. [79.202.125.232])
 by mx.google.com with ESMTPSA id h5sm410701bkg.8.2013.08.05.22.53.52
 for <multiple recipients>
 (version=TLSv1.2 cipher=RC4-SHA bits=128/128);
 Mon, 05 Aug 2013 22:53:53 -0700 (PDT)
Date: Tue, 6 Aug 2013 07:53:50 +0200
From: Gary Jennejohn <gljennjohn@googlemail.com>
To: Craig Rodrigues <rodrigc@FreeBSD.org>
Subject: Re: Kernel Panic on FreeBSD 10.0-CURRENT #1 r253918
Message-ID: <20130806075350.497414fd@ernst.home>
In-Reply-To: <CAG=rPVdx4PoMnHLXapDDAQeePyywCfY5HH8b5gm8ys1pyVwB7A@mail.gmail.com>
References: <CAOFF+Z1tPbBkugE2ReRqAPHdmpkOCBFxz-bF9agVhGq4j56Eow@mail.gmail.com>
 <CAG=rPVfcu8=10mBLqR_AscJGv274sQbXjjjCCYh7tRRWOnJrMw@mail.gmail.com>
 <CAOFF+Z2cXzUnpMNR+TMj4ggZxVxaoXpYUMWzV1yg4degKR_GVw@mail.gmail.com>
 <CAG=rPVdx4PoMnHLXapDDAQeePyywCfY5HH8b5gm8ys1pyVwB7A@mail.gmail.com>
X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.17; amd64-portbld-freebsd10.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: "Sam Fourman Jr." <sfourman@gmail.com>,
 FreeBSD Current <freebsd-current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: gljennjohn@googlemail.com
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 05:53:56 -0000

On Mon, 5 Aug 2013 10:29:23 -0700
Craig Rodrigues <rodrigc@FreeBSD.org> wrote:

> On Sun, Aug 4, 2013 at 3:59 PM, Sam Fourman Jr. <sfourman@gmail.com> wrote:
> 
> >
> >
> >
> > Craig,
> >
> > Thank you for getting back to me, I will get to work on this right away
> > and get you what you need.
> > but are we CERTAIN this panic could be from VIMAGE? I totally thought I
> > had a # infront of that line when I built this kernel...
> >
> > if you notice I did post the kernel config at the bottom of that email,
> > and VIMAGE is NOT included...
> > but maybe I did something wrong and somehow built VIMAGE in anyway..
> >
> > is there some sort of command I can run to ask the system if it does
> > indeed have VIMAGE?
> >
> 
> On the booted an running system, if you type:
> 
> sysctl kern.conftxt
> 
> that will display the actual kernel config options used to build the
> running kernel.
>

Not necessarily

 sysctl kern.conftxt
 sysctl: unknown oid 'kern.conftxt': No such file or directory

-- 
Gary Jennejohn