From owner-freebsd-current@FreeBSD.ORG Sat Sep 13 08:59:42 2014 Return-Path: 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 ESMTPS id 2BDC6AA8; Sat, 13 Sep 2014 08:59:42 +0000 (UTC) Received: from mout.gmx.com (mout.gmx.com [74.208.4.200]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E8088EFF; Sat, 13 Sep 2014 08:59:41 +0000 (UTC) Received: from [157.181.98.237] ([157.181.98.237]) by mail.gmx.com (mrgmxus001) with ESMTPSA (Nemesis) id 0M7pUE-1YFLem3e1A-00vMQU; Sat, 13 Sep 2014 10:59:25 +0200 Message-ID: <54140711.7020001@gmx.com> Date: Sat, 13 Sep 2014 10:57:53 +0200 From: dt71@gmx.com User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:32.0) Gecko/20100101 Firefox/32.0 SeaMonkey/2.29 MIME-Version: 1.0 To: John Baldwin , Marcin Cieslak Subject: Re: Xorg causes panics with "multiple" drivers (Was: panic: resource_list_alloc: resource entry is busy) References: <1584874.3FXdLuYUQI@ralph.baldwin.cx> <3819796.R7BYA2qqa8@ralph.baldwin.cx> In-Reply-To: <3819796.R7BYA2qqa8@ralph.baldwin.cx> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:t3L2GnBA6jfdku/DPTjMuwrkOqhVtRl1zU1VRAfwsTYOJ9kif/N t8d/6bBnirATpFM1c88wEDL91QbugWQpsO4fxjEYevPkH7+1eVEbN2q68kJejQGzmkNN9zU wxaTaOY8h7Jtk+L/QMUOtel02X8fy2R65oQ1KhrmsfZLSKMKv2DrMfPzIISO0wkETdzJN8Y QeddO7GGL8RRjh7K7KbCg== X-UI-Out-Filterresults: notjunk:1; Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Sep 2014 08:59:42 -0000 John Baldwin wrote on 09/12/2014 23:06: > X loaded i915kms automatically and > i915 and i915kms do not get along. i915 had already allocated the IRQ > when i915kms tried to alloc the same IRQ causing the issue. Who is to blame? The user who tried to manually load an unsupported combination of modules, or the system, which should have handled things gracefully (whether by automatically unloading the first driver, or producing a soft-error upon loading the 2nd driver)? On a side-note, I also had a "resource_list_alloc: resource entry is busy" panic right after switching from the 10.0-supported Xorg to the "new" Xorg; I exited Xorg, enabled "FreeBSD_new_Xorg", ran "pkg upgrade", then ran "startx", and got the panic. Surely this wasn't my fault!