From owner-freebsd-stable@FreeBSD.ORG Mon Apr 16 07:04:21 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BAD83106564A for ; Mon, 16 Apr 2012 07:04:21 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mx.nsu.ru (r2b9.nsu.ru [212.192.164.39]) by mx1.freebsd.org (Postfix) with ESMTP id 622728FC08 for ; Mon, 16 Apr 2012 07:04:21 +0000 (UTC) Received: from regency.nsu.ru ([193.124.210.26]) by mx.nsu.ru with esmtp (Exim 4.69) (envelope-from ) id 1SJfyo-0004I4-5W; Mon, 16 Apr 2012 14:04:06 +0700 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.14.2/8.14.2) with ESMTP id q3G76pXK081025; Mon, 16 Apr 2012 14:06:51 +0700 (NOVT) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.14.2/8.14.2/Submit) id q3G76kNi080951; Mon, 16 Apr 2012 14:06:46 +0700 (NOVT) (envelope-from danfe) Date: Mon, 16 Apr 2012 14:06:46 +0700 From: Alexey Dokuchaev To: Eugene Grosbein Message-ID: <20120416070646.GA78414@regency.nsu.ru> References: <20120416042645.GA53074@regency.nsu.ru> <4F8BBE29.1060605@rdtc.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4F8BBE29.1060605@rdtc.ru> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org Subject: Re: RELENG_8 kernel as of Apr 14 does not boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Apr 2012 07:04:21 -0000 On Mon, Apr 16, 2012 at 01:37:29PM +0700, Eugene Grosbein wrote: > 16.04.2012 11:26, Alexey Dokuchaev пишет: > > Just update my 8.x kernel sources last weekend, and newly built kernel did > > not boot for me: > > > > link_elf: symbol mem_range_softc undefined > > KLD file acpi.ko - could not finalize loading > > kernel trap 12 with interrupts disabled > > Try to add 'device mem' to your kernel configuration. :-) I explicitly have "nodevice mem" and "nodevice io" in my config. They are being loaded from /boot/loader.conf. This worked fine for quite a while. I will try to have it compiled-in, but would still prefer it fixed, or in case it cannot be fixed and mem.ko cannot be loaded separately from now on, appropriate entry in UPDATING. ./danfe