Date: Tue, 09 Feb 2016 15:29:48 +0200 From: Arto Pekkanen <isoa@kapsi.fi> To: freebsd-x11@freebsd.org Cc: owner-freebsd-x11@freebsd.org Subject: Re: Testing drm-i915-update-38 (c6d9af5) with patched i915_gem.c, encouraging results. Message-ID: <f1e66303d83aad49147cb83cb5237a2f@kapsi.fi> In-Reply-To: <4cafc77ad57d53684808a0611b0305e2@kapsi.fi> References: <4cafc77ad57d53684808a0611b0305e2@kapsi.fi>
next in thread | previous in thread | raw e-mail | index | archive | help
For some reason I was not able to attach the diff to the previous message, so I will try to attach it here. Arto Pekkanen kirjoitti 08.02.2016 05:09: > Hi again. > > I realized that previously the drm-i915-update-38 (c6d9af5) kernel > crashed because of a BUG_ON trap in i915_gem.c, not because of actual > code fault. > > Then I found the following discussion in GitHub: > https://github.com/freebsd/freebsd-base-graphics/issues/2 > > There the user myfreeweb "McGyver'd" the BUG_ON trap away by replacing > it with WARN_ON -macro. I wanted to see if the driver would work, so I > did the same. > > Attached is the diff that replaces BUG_ON with WARN_ON in i915_gem.c > and thus makes the kernel not crash while playing games/openarena. > > The results: > - kernel boots > - vt console works > - LVDS + 2 monitors on HDMI2 and HDMI3, all work with native > resolutions, > NOTE: this is an IMPROVEMENT! Previously X.org would HANG if I > enabled more than 2 monitors! > - video playback is perfect, no tearing, minimal CPU use, tested with > - www/chromium > - multimedia/mpv (with VAAPI enabled in multimedia/mpv and > multimedia/ffmpeg) > - games/openarena works just fine > > In fact, I can actually run games/openarena at the same time with > www/chromium wathing https://www.youtube.com/watch?v=5xkNy9gfKOg (full > HD tearing test video), with some stuttering on both ... but this is > to be expected, because the kernel has to serve 2 OpenGL pipes at the > same time which is problematic. > > And because I can now use 3 outputs at the same time, I am very > impressed. > > I see many warnings like this in dmesg: > Feb 8 04:33:15 leno kernel: error: > [drm:pid1073:i915_gem_object_move_to_inactive] *ERROR* WARN ON: > obj->base.write_domain & ~I915_GEM_GPU_DOMAINS > > The frequency between these errors is about one second when I run > games/openarena. With www/chromium I do not see these warnings. > > The only real gripe I have is that the FreeBSD 11 -based kernel does > not detect my Intel Wifi chip, yet stock FreeBSD 10.2 was able to do > that. Should I report this as a regression somewhere? The problem with > reporting this is that I am running FreeBSD 10.2 userland, and I feel > like the developers might not want to deal with that. > > I will leave the laptop on while I sleep, leave it running the Tearing > Test -video mentioned above. If it crashes I will post core dump etc. -- Arto Pekkanen From owner-freebsd-x11@freebsd.org Wed Feb 10 09:14:07 2016 Return-Path: <owner-freebsd-x11@freebsd.org> Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7AF15AA3D21 for <freebsd-x11@mailman.ysv.freebsd.org>; Wed, 10 Feb 2016 09:14:07 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 69269CE9 for <freebsd-x11@freebsd.org>; Wed, 10 Feb 2016 09:14:07 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 692DBAA3D20; Wed, 10 Feb 2016 09:14:07 +0000 (UTC) Delivered-To: x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 68CB5AA3D1F for <x11@mailman.ysv.freebsd.org>; Wed, 10 Feb 2016 09:14:07 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org (portscout.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5C705CE8 for <x11@freebsd.org>; Wed, 10 Feb 2016 09:14:07 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org ([127.0.1.123]) by portscout.freebsd.org (8.15.2/8.15.2) with ESMTP id u1A9E7jR009159 for <x11@freebsd.org>; Wed, 10 Feb 2016 09:14:07 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.freebsd.org (8.15.2/8.15.2/Submit) id u1A9E7wo009158; Wed, 10 Feb 2016 09:14:07 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201602100914.u1A9E7wo009158@portscout.freebsd.org> X-Authentication-Warning: portscout.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Wed, 10 Feb 2016 09:14:07 +0000 From: portscout@FreeBSD.org To: x11@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support <freebsd-x11.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-x11>, <mailto:freebsd-x11-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-x11/>; List-Post: <mailto:freebsd-x11@freebsd.org> List-Help: <mailto:freebsd-x11-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-x11>, <mailto:freebsd-x11-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 10 Feb 2016 09:14:07 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/x11@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ x11-servers/xephyr | 1.17.4 | 1.18.1 ------------------------------------------------+-----------------+------------ x11-servers/xorg-dmx | 1.17.4 | 1.18.1 ------------------------------------------------+-----------------+------------ x11-servers/xorg-server | 1.17.4 | 1.18.1 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f1e66303d83aad49147cb83cb5237a2f>