From owner-freebsd-current@FreeBSD.ORG Fri Sep 12 22:03:30 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 424FAA18; Fri, 12 Sep 2014 22:03:30 +0000 (UTC) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "m.saper.info", Issuer "Marcin Cieslak 2011" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CE6CDFBF; Fri, 12 Sep 2014 22:03:29 +0000 (UTC) Received: from localhost (saper@localhost [127.0.0.1]) by m.saper.info (8.14.9/8.14.9) with ESMTP id s8CM3QQa073130 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Sep 2014 22:03:27 GMT (envelope-from saper@saper.info) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=saper.info; s=Sep2014; t=1410559407; bh=iEhoIDZveAkvqrEFJgF/NjFgGQS6zPYdzXzt78x/KOA=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=iy2hLuxnvKNbFRkLHlBrzC24ElajLiis7VAXKvIyw4jZf+tsyeawt6+opfBmeFOf3 5vhNQwGGah2Bi5cUo4ZQg/nRzTTDgWQ6l/bRT+hW+Y0Gm5PGAuNTJfTYE8fadkN3pC B9w0+rAoQWUzAEHbErD51XTiVPpMiGXhCpyL3kBg= Date: Fri, 12 Sep 2014 22:03:26 +0000 (UTC) From: Marcin Cieslak To: John Baldwin Subject: Re: panic: resource_list_alloc: resource entry is busy In-Reply-To: <3819796.R7BYA2qqa8@ralph.baldwin.cx> Message-ID: References: <1584874.3FXdLuYUQI@ralph.baldwin.cx> <3819796.R7BYA2qqa8@ralph.baldwin.cx> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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: Fri, 12 Sep 2014 22:03:30 -0000 On Fri, 12 Sep 2014, John Baldwin wrote: >> Please note I originally loaded "i915.ko", not "i915kms.ko" > > Oh, that is probably your problem. 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. Would that be possible to fail with EBUSY or something instead of panic? //Marcin