From owner-freebsd-bugs@FreeBSD.ORG  Sat Jul 12 08:15:07 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 E0EE74D2
 for <freebsd-bugs@FreeBSD.org>; Sat, 12 Jul 2014 08:15:07 +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 C90DD2C18
 for <freebsd-bugs@FreeBSD.org>; Sat, 12 Jul 2014 08:15:07 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s6C8F7AQ078343
 for <freebsd-bugs@FreeBSD.org>; Sat, 12 Jul 2014 08:15:07 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: Sat, 12 Jul 2014 08:15:08 +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-iXVIL1W8pK@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: Sat, 12 Jul 2014 08:15:08 -0000

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

--- Comment #4 from dreamcat4@gmail.com ---
(In reply to Kurt Jaeger from comment #3)
> Can you test if this still happens with the upcoming 9.3-release ?

Sorry. Unfortunately I don't happen to have any suitable FreeBSD-GENERIC build
lying around. Best I can do is put it on my list (sorry, very busy), and try to
get round to it eventually. Maybe in a few weeks time.

In an ideal circumstance, we would:

* Rebuild for this kernel config in a 9.2-GENERIC VM.
* Reproduce panic. [Y/N]
* Then freebsd-update to 9.3 RELEASE (since 9.3 will be released by that time). 
* Rebuild for this kernel config in a 9.3-GENERIC VM.
* Reproduce panic. [Y/N]
* Then freebsd-update to 10.0 RELEASE. 
* Rebuild for this kernel config in a 10.0-GENERIC VM.
* Reproduce panic. [Y/N]

However the situation is complicated by the fact we don't know exactly which
other modules VIMAGE is conflicting with. So in reality, we need to also be:

* Rebuild for this kernel config in a 9.2-GENERIC VM.
* Reproduce panic. [Y/N]
* <edit kernel config>
 * add or remove a suspected module
* Reproduce panic. [Y/N]
* <edit kernel config>
 * add or remove a suspected module
* Reproduce panic. [Y/N]
* <edit kernel config>
 * add or remove a suspected module
Etc. etc.

Which take a lot of time.

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