From owner-freebsd-x11@freebsd.org Tue Dec 5 14:03:09 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 CD902E6AD3B for ; Tue, 5 Dec 2017 14:03:09 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AF6BA7BD13; Tue, 5 Dec 2017 14:03:09 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id D18C310E7A; Tue, 5 Dec 2017 14:03:08 +0000 (UTC) Date: Tue, 5 Dec 2017 14:03:08 +0000 From: Alexey Dokuchaev To: Andriy Gapon Cc: freebsd-x11 , "Conrad E. Meyer" Subject: Re: couple of nvidia-driver issues Message-ID: <20171205140308.GA94043@FreeBSD.org> References: <07b9dbda-60ef-3643-308f-18a05e8ca958@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <07b9dbda-60ef-3643-308f-18a05e8ca958@FreeBSD.org> User-Agent: Mutt/1.9.1 (2017-09-22) 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: Tue, 05 Dec 2017 14:03:09 -0000 On Fri, Nov 24, 2017 at 11:31:51AM +0200, Andriy Gapon wrote: > > 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. I'll try to reproduce it and report back. > 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 Unfortunately, I'm not an expert on kernel locking primitives to give you a proper review, let's see what others have to say. > Also, what's the best place or who are the best people with whom to > discuss such issues? Yes, this is a problem now: since Christian Zander had left nVidia, he could not tell me who'd be their next liaison to talk to from FreeBSD community. :-( ./danfe