From owner-freebsd-x11@freebsd.org Mon Nov 20 16:31:37 2017 Return-Path: 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 34E75DF0604 for ; Mon, 20 Nov 2017 16:31:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 1D21263EFD for ; Mon, 20 Nov 2017 16:31:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 19B48DF0603; Mon, 20 Nov 2017 16:31:37 +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 1942BDF0602 for ; Mon, 20 Nov 2017 16:31:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 0795963EFC for ; Mon, 20 Nov 2017 16:31:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vAKGVaAe049472 for ; Mon, 20 Nov 2017 16:31:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 223195] graphics/mesa-dri: update to 17.3.0 Date: Mon, 20 Nov 2017 16:31:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jbeich@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: x11@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Nov 2017 16:31:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223195 Jan Beich changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #188000|0 |1 is obsolete| | --- Comment #10 from Jan Beich --- Created attachment 188140 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D188140&action= =3Dedit rc5 https://lists.freedesktop.org/archives/mesa-announce/2017-November/000376.h= tml --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-x11@freebsd.org Wed Nov 22 10:33:41 2017 Return-Path: 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 076C4DE716A for ; Wed, 22 Nov 2017 10:33:41 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) 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 E18B375CCE for ; Wed, 22 Nov 2017 10:33:40 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: by mailman.ysv.freebsd.org (Postfix) id DDD33DE7168; Wed, 22 Nov 2017 10:33:40 +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 DD734DE7167 for ; Wed, 22 Nov 2017 10:33:40 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mx.nsu.ru (mx.nsu.ru [84.237.50.39]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8E4F575CCD for ; Wed, 22 Nov 2017 10:33:40 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from [84.237.50.47] (helo=regency.nsu.ru) by mx.nsu.ru with esmtp (Exim 4.72) (envelope-from ) id 1eHS1T-0008Em-Ta for x11@freebsd.org; Wed, 22 Nov 2017 17:12:51 +0700 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.14.2/8.14.2) with ESMTP id vAMAM0EE098403 for ; Wed, 22 Nov 2017 16:22:00 +0600 (NOVT) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.14.2/8.14.2/Submit) id vAMALtcv098338 for x11@freebsd.org; Wed, 22 Nov 2017 17:21:55 +0700 (+07) (envelope-from danfe) Date: Wed, 22 Nov 2017 17:21:55 +0700 From: Alexey Dokuchaev To: x11@freebsd.org Subject: [patch] x11-servers/xorg-server: glamor: Fix dashed line rendering (from upstream) Message-ID: <20171122102155.GA97343@regency.nsu.ru> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="FL5UXtIhxfXey3p5" Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4.2.1i X-KLMS-Rule-ID: 3 X-KLMS-Message-Action: skipped X-KLMS-AntiSpam-Status: not scanned, whitelist X-KLMS-AntiPhishing: not scanned, whitelist X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.705, not scanned, whitelist X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Nov 2017 10:33:41 -0000 --FL5UXtIhxfXey3p5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi there, May I commit the attached patch? It fixes displaying dashed and dotted lines in 2D applications (e.g. bounding boxes around active widgets e.g. buttons) which are drawn as solid lines without this patch. Found via openSUSE's xorg-x11-server package. ./danfe --FL5UXtIhxfXey3p5 Content-Type: text/plain; charset=koi8-r Content-Disposition: attachment; filename="patch-glamor_glamor__dash.c" Content-Transfer-Encoding: 8bit From: Eric Anholt Date: Wed Mar 15 17:51:46 2017 -0700 Subject: [PATCH]glamor: Fix dashed line rendering. Patch-mainline: fe0b297420fc1de8a7fab28457d0864b3182e967 References: boo#1021803 Signed-off-by: Max Staudt We were binding the screen pixmap as the dash and sampling its alpha, which is usually just 1.0 (no dashing at all). Please cherry-pick this to active stable branches. Signed-off-by: Eric Anholt Reviewed-by: Keith Packard Reviewed-by: Michel Dänzer --- glamor/glamor_dash.c.orig 2016-07-18 19:08:16 UTC +++ glamor/glamor_dash.c @@ -146,7 +146,7 @@ glamor_dash_setup(DrawablePtr drawable, GCPtr gc) goto bail; dash_pixmap = glamor_get_dash_pixmap(gc); - dash_priv = glamor_get_pixmap_private(pixmap); + dash_priv = glamor_get_pixmap_private(dash_pixmap); if (!GLAMOR_PIXMAP_PRIV_HAS_FBO(dash_priv)) goto bail; --FL5UXtIhxfXey3p5-- From owner-freebsd-x11@freebsd.org Wed Nov 22 23:57:25 2017 Return-Path: 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 6CAF2DF8F9C for ; Wed, 22 Nov 2017 23:57:25 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ua0-x231.google.com (mail-ua0-x231.google.com [IPv6:2607:f8b0:400c:c08::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2B08A70B86 for ; Wed, 22 Nov 2017 23:57:25 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-ua0-x231.google.com with SMTP id l25so11743881uag.8 for ; Wed, 22 Nov 2017 15:57:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:from:date:message-id:subject:to; bh=cGop8BdWB2nS0PSj7i2J94N6pDwLLHYhZlTt+fe5usA=; b=sBv3QW59qpOBFQoqmVJ7YQ8JzBlhGIhW9KBl7jDPWfRi6VdzlFqKz8ejGcNeiCH+RK zZwjgbOWvIl5UVANjq9DRHJGdftwBZK6SqTiwWDT1NuAEH7I8ZbMvGsaoZFXY2wr5mlr mjqGXKuR1rNd2ufPcCUeUamNi0ySFd22jouzESrQwWBu8mKBjjccABVtlhTysMTswHqs fKIjxThT0LOPr7YJSrtyYTMyctIbIAplJZsk70XkKOT6FGlItM02bji2/XQ5LfM/UWx6 UNIDzj3j5BucAkLFoKubQ+NeIe8TsTGef6aiTBM2S3chcf+6IjpkgRBYViFX9fhOpOys /pEg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=cGop8BdWB2nS0PSj7i2J94N6pDwLLHYhZlTt+fe5usA=; b=e9nAGURiORPlbVaTXubjDjbcX0OhCa5HkHopc8F9nxC5FMRzG13KkGAQEoM+LNl7IM v1E7F+6gY7FMHsZAeCB2cII26bwNA9nXeh9OZZauOq6adSmY8TEAr+0FwvSHApLgrSGq ajFMvVJwJ2PfpC22iGwm4zDGSak8zb8Ua+pKUvWeCSFmLwmwz2GJucjfHBNl/y0KxudC 21ldFSjdJrwPzVZfpjUyJlaffUcqWr1qv323FIHL2HWBhAdxCRjr2XVjkYA1l2UmevJ3 akrg79QRFVpgleE0QMDatIRlIMXfctGGWsX/Qq6PvNPtDbO1Z7n/uTzazG13vLPy/7Aa d1+g== X-Gm-Message-State: AJaThX7th+/m19VV94o6tsHwsrS1nIhyqLe5ndef8MMuaWyxLkW0mg9w rrtFEijpYHuI+gxz28EiGN2vbVsPAGlhEiuN8/CUSDHR X-Google-Smtp-Source: AGs4zMbu+nq3SVRvrFvxwvwEjRJWEpuEG1huE0PZRgscyV1LtyjGzQgEdUdizH86D2sdJRQ8kcth2KUo2hx0k2Ze63Q= X-Received: by 10.176.73.45 with SMTP id z42mr18309418uac.71.1511395043911; Wed, 22 Nov 2017 15:57:23 -0800 (PST) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.103.147.156 with HTTP; Wed, 22 Nov 2017 15:57:23 -0800 (PST) From: Kevin Oberman Date: Wed, 22 Nov 2017 15:57:23 -0800 X-Google-Sender-Auth: xzhFwyUJ1iysfLR0HzGTcj0S2nA Message-ID: Subject: Poor video performance since last mesa update To: x11-list freebsd Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Nov 2017 23:57:25 -0000 Since the last update to mesa on my Ivy Bridge system I have been getting very poor video performance for high resolution video. I'm not seeing he CPUs saturated, but the video is jerky... lots of dropped frames when playing full-resolution 1080p from youtube as well as with mpv. xine is worse with the image getting blocky and with serious color artifacts. If I play the same video H.264 codec) but set the view at half resolution, it plays correctly. It was fine until the update to 17.2.4. FresBSD 11.1 with all ports up to date. Here is what mediainfo says about the mp4: Format : AVC Format/Info : Advanced Video Codec Format profile : High@L4 Format settings : CABAC / 2 Ref Frames Format settings, CABAC : Yes Format settings, ReFrames : 2 frames Codec ID : avc1 Codec ID/Info : Advanced Video Coding Duration : 4 min 41 s Bit rate : 7 302 kb/s Width : 1 920 pixels Height : 1 080 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 25.000 FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 8 bits Scan type : Progressive Bits/(Pixel*Frame) : 0.141 Stream size : 245 MiB (95%) Is this a known issue or should I open a bug report? I've seen no similar reports. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 From owner-freebsd-x11@freebsd.org Fri Nov 24 09:32:02 2017 Return-Path: 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 8FD19DDE204 for ; Fri, 24 Nov 2017 09:32:02 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f51.google.com (mail-lf0-f51.google.com [209.85.215.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 14FBE6CC69; Fri, 24 Nov 2017 09:32:01 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f51.google.com with SMTP id m1so24727074lfj.9; Fri, 24 Nov 2017 01:32:01 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:cc:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=OQwOCEmn6OucHZbIEMd2GQ6cYwncy8vlvm+SItwfyf8=; b=mdNwcgYM8qgIqKeblNvbr5Ix5Nsf7if/hdbiOPov9U0RGuaAP0RTOdJk4FPqYH8uyH CnBRzDSiLFlBhNReOCkTzQ/7BL2wQLVa5W0uUFz8h46UwRd4WNXtkIFh9xY4ZLD402gh fUiyAdHevE9cglptIm7d4Yp06qdsbeBa+l9qkWINzciJJfPpl+l0TjKf+Ws018qJVFxZ BYa+RzerJzeMRZUWIgrZNbstpCp3wFkmgtgVvmL12foS9Uzy1pB2SE2yW4mW+wGd1B+7 0lzCuT1urboVBy9X7Kv1MD69ZzwADAshhC9B0Om9Vkx9+KYeysAvfvPyCu+zDrRpX0ne P0gw== X-Gm-Message-State: AJaThX7rQG+wbeXJmgaZ9T9lri8f89A4FVg+ANIzIp3LU7zEX30yJHYZ Y2n9Ll2Fap7HC+LKzm0pYrcpNc7T X-Google-Smtp-Source: AGs4zMaSsvYsYrjAZwXH1hsrIFRuhYV8n29YmALQwdKlMHAPzg/XjHA1nylgcWEQUtbFc2Sr8vvzoQ== X-Received: by 10.25.37.82 with SMTP id l79mr6121642lfl.81.1511515913887; Fri, 24 Nov 2017 01:31:53 -0800 (PST) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id z10sm4460096ljb.75.2017.11.24.01.31.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 Nov 2017 01:31:53 -0800 (PST) To: Alexey Dokuchaev , freebsd-x11 From: Andriy Gapon Subject: couple of nvidia-driver issues Cc: "Conrad E. Meyer" Message-ID: <07b9dbda-60ef-3643-308f-18a05e8ca958@FreeBSD.org> Date: Fri, 24 Nov 2017 11:31:51 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Nov 2017 09:32:02 -0000 I have reported a couple of nvidia-driver issues in the FreeBSD section of the nVidia developer forum, but no replies so far. Well, the first issue is not with the driver, but with a utility that comes with it, nvidia-smi: https://devtalk.nvidia.com/default/topic/1026589/freebsd/nvidia-smi-query-gpu-spins-forever-on-freebsd-head-amd64-/ I wonder if I am the only one affected or if I see the problem because I am on head or something else. I am pretty sure that the problem is caused by a programming bug related to strtok_r. The second issue is with the FreeBSD support for the kernel driver: https://devtalk.nvidia.com/default/topic/1026645/freebsd/panic-related-to-nvkms_timers-lock-sx-lock-/ I would like to get some feedback on my analysis. I am testing this patch right now: https://people.freebsd.org/~avg/extra-patch-src_nvidia-modeset_nvidia-modeset-freebsd.c Also, what's the best place or who are the best people with whom to discuss such issues? Thank you! -- Andriy Gapon