From owner-freebsd-current@freebsd.org Wed Sep 18 22:56:47 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 44B8DE9024 for ; Wed, 18 Sep 2019 22:56:47 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc13.plala.or.jp (msc13.plala.or.jp [IPv6:2400:7800:0:502e::23]) by mx1.freebsd.org (Postfix) with ESMTP id 46Yb2Q38cfz3NB1; Wed, 18 Sep 2019 22:56:45 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from localhost ([2400:4050:9320:7a00::8]) by msc12.plala.or.jp with ESMTP id <20190918225124.BQZW7266.msc12.plala.or.jp@localhost>; Thu, 19 Sep 2019 07:51:24 +0900 Date: Thu, 19 Sep 2019 07:50:38 +0900 (JST) Message-Id: <20190919.075038.1687549947501964479.ish@amail.plala.or.jp> To: zeising@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: hang up with r352239 and r352386 with i5-7500 From: Masachika ISHIZUKA In-Reply-To: <5fa15ee8-a1cb-37e7-b954-c50b1cd0a8d9@freebsd.org> References: <20190917.235930.528406816270492485.ish@amail.plala.or.jp> <20190918.171520.1850897233083712866.ish@amail.plala.or.jp> <5fa15ee8-a1cb-37e7-b954-c50b1cd0a8d9@freebsd.org> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; mvir-ac12; Thu, 19 Sep 2019 07:51:24 +0900 X-Rspamd-Queue-Id: 46Yb2Q38cfz3NB1 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-5.99 / 15.00]; NEURAL_HAM_MEDIUM(-0.99)[-0.995,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Wed, 18 Sep 2019 22:56:47 -0000 >>>>>>>> Can you please use absolute paths to i915kms.ko anyway, just to test? >> [snip] >> >> Now, drm-current-kmod is working fine on r352467 by your patch. >> > > Hi! > I just updated the port with the fix I suggested earlier, hopefully it > works. It will take some time before it shows up as packages, but > there is no problems building drm-current-kmod from ports even if > packages are used for the rest of the system. It is good working drm-current-kmod-4.16.g20190918 in port tree. Thank you very much. -- Masachika ISHIZUKA