From owner-freebsd-bugs@FreeBSD.ORG  Mon Jul 21 19:50:55 2014
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@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 ESMTPS id B000613A
 for <freebsd-bugs@FreeBSD.org>; Mon, 21 Jul 2014 19:50:55 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 97FB12C85
 for <freebsd-bugs@FreeBSD.org>; Mon, 21 Jul 2014 19:50:55 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s6LJotkU039218
 for <freebsd-bugs@FreeBSD.org>; Mon, 21 Jul 2014 19:50:55 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 191468] [vimage] options VIMAGE - kernel panic, crashes during
 system boot
Date: Mon, 21 Jul 2014 19:50:55 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 9.2-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: dreamcat4@gmail.com
X-Bugzilla-Status: Needs Triage
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-191468-8-SRUHM3UCUc@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-191468-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-191468-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jul 2014 19:50:55 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191468

--- Comment #5 from dreamcat4@gmail.com ---
OK. Good news. We have some new information from jandegr, who has recently been
investigating this same issue. Here are his comments:

In short : Vimage or infiniband on 9.3-RELEASE is no problem, but both together
in the same config gives a nice page fault at boot.
No problem for the both in the same config on 10-stable.
They can reproduce it starting from a generic config with the addition of the
infiniband entries from the NAS4Free config.
I did not determine which of the infiniband entries causes it,I treated them as
one block for the purpose of building a VIMAGE kernel, and I already spent
a lot of time to find the infiniband connection.


Forum Link:

http://www.forums.nas4free.org/viewtopic.php?f=69&t=5365&sid=f51d324fd807e82208b3cbf793d0d55d&start=100

-- 
You are receiving this mail because:
You are the assignee for the bug.