From owner-freebsd-stable@FreeBSD.ORG Tue May 5 14:12:52 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91F28106564A; Tue, 5 May 2009 14:12:52 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from megatron.madpilot.net (megatron.madpilot.net [88.149.173.206]) by mx1.freebsd.org (Postfix) with ESMTP id 04A678FC0C; Tue, 5 May 2009 14:12:51 +0000 (UTC) (envelope-from mad@madpilot.net) Received: by megatron.madpilot.net (Postfix, from userid 1000) id A5290130C54; Tue, 5 May 2009 16:12:50 +0200 (CEST) Date: Tue, 5 May 2009 16:12:50 +0200 From: Guido Falsi To: Gavin Atkinson Message-ID: <20090505141250.GA85300@megatron.madpilot.net> References: <20090505110624.GA83487@megatron.madpilot.net> <1241521951.47323.3.camel@buffy.york.ac.uk> <20090505121247.GN1948@deviant.kiev.zoral.com.ua> <1241526927.47323.5.camel@buffy.york.ac.uk> <1241531476.47323.8.camel@buffy.york.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1241531476.47323.8.camel@buffy.york.ac.uk> X-Operating-System: FreeBSD 7.1-STABLE User-Agent: Mutt/1.5.19 (2009-01-05) Cc: Kostik Belousov , freebsd-stable@FreeBSD.org, jhb@FreeBSD.org Subject: Re: [PANIC] recent 7.2-STABLE when probing drm 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: Tue, 05 May 2009 14:12:52 -0000 On Tue, May 05, 2009 at 02:51:16PM +0100, Gavin Atkinson wrote: > On Tue, 2009-05-05 at 13:35 +0100, Gavin Atkinson wrote: > > [...] > > > > I wonder if r189373 also needs merging? > > Looking at a thread on -current, it looks like this is probably the > case. It's not a straight merge from head as other bits have changed, > but you could test http://people.freebsd.org/~gavin/189373_7.diff > (warning: compile tested only) Tested the patch, it solves the problem. The system now boots cleanly. Im using the PC as normal with no ill effects with this new kernel. -- Guido Falsi