From owner-freebsd-current@FreeBSD.ORG Sat Sep 13 11:37:29 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 2855A4D3 for ; Sat, 13 Sep 2014 11:37:29 +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 B2EBDDCE for ; Sat, 13 Sep 2014 11:37:28 +0000 (UTC) Received: from localhost (saper@localhost [127.0.0.1]) by m.saper.info (8.14.9/8.14.9) with ESMTP id s8DBbO7k075475 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 13 Sep 2014 11:37:25 GMT (envelope-from saper@saper.info) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=saper.info; s=Sep2014; t=1410608245; bh=kp/ZZABGyCxwoj42KpF6xso8dPK/BoiY/UOn5od85d0=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=WywJt9TTHbKtzpO9lU2BTTMpQ9Syl5J1ZyODzHYqoq0byuG2p2ddMEqUt7hN3wNw0 iYOhbLyFUdCYzPrGgNKaXPYZbhxj28HAUkneHf8r1n6APAi2b0IXa61rIrpHvENYkT f9DrbpgvTrSSqYcHUW8w5YYRPRTzqOrQ08vSeddA= Date: Sat, 13 Sep 2014 11:37:24 +0000 (UTC) From: Marcin Cieslak To: Kevin Oberman Subject: Re: panic: resource_list_alloc: resource entry is busy In-Reply-To: Message-ID: References: <1749648.0eHaTPXHUy@ralph.baldwin.cx> <1584874.3FXdLuYUQI@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 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 11:37:29 -0000 On Fri, 12 Sep 2014, Kevin Oberman wrote: > On Fri, Sep 12, 2014 at 1:57 PM, Marcin Cieslak wrote: > >> Please note I originally loaded "i915.ko", not "i915kms.ko" >> >> >> Unfortunately, "kldunload i915kms" makes my screen blank >> and probably crashes the system (disk activity stops after >> a short while and there is no response to the keyboard input). >> >> //Marcin >> >> > That explains most of it. You need i915kms. It is conflicting with i915 > which already has the IRQ allocated. > > The black screen is expected. Once KMS starts talking to the graphics > system, syscons can no longer talk to the display, so you get a black > screen. To have a working display, you must enable vt(4). Add "kern.vty=vt" > to /boot/loader.conf to enable vt(4) which will keep the display alive. Yes, I do have "kern.vty=vt" enabled in the loader and without i915kms loaded my system boots correctly. I can load i915kms later per hand or when starting X, but it does not work with bootloader. I think it's a known problem as of September 2nd as stated on the http://wiki.freebsd.org/Newcons page. (My machine is Sony VAIO SZ5MN). //Marcin