From owner-freebsd-x11@freebsd.org Sun Jun 12 11:23:58 2016 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 786A2AF0B0C for ; Sun, 12 Jun 2016 11:23:58 +0000 (UTC) (envelope-from bengta@sics.se) Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (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 EFA8424F1 for ; Sun, 12 Jun 2016 11:23:57 +0000 (UTC) (envelope-from bengta@sics.se) Received: by mail-lf0-x22b.google.com with SMTP id u74so69513573lff.2 for ; Sun, 12 Jun 2016 04:23:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sics-se.20150623.gappssmtp.com; s=20150623; h=from:to:subject:in-reply-to:references:user-agent:date:message-id :mime-version; bh=U19UJ9L1MH3qBV3RBcZmlCm2Zj6KGPscCfpGGz/FrXE=; b=qmyIQM0r+bGrAZUJ5mZHFXFNr+Q3rzQ0d/cP6rL24Ew8nFUUwQoSGh0bV/9ZTWnrwM hVGIzGeBPt5/sRqhdKfRlIdOF7LHm93RmFOQz6OdUf904NnoKcnpgtoQvMAw+FtB8BhQ /okQ6PHDRypknxienQ9touEK8r9cerw4gnEX7fSgq/vDGXLpEBCM0z38dnCP37urxbAz aP0G1A92PpHBcIGgTbvrhOe8sZFkyIhgXZJyEDYt4GoitAaqqL8UMCx1+Z6kBsBBO/5c WfG3HxNGLsQij+uXj4F1nydfmNZsULP0ZxWYrxZRt0uIJ/AatThBL+YYKHEMwBQUcVGW s4xA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:in-reply-to:references :user-agent:date:message-id:mime-version; bh=U19UJ9L1MH3qBV3RBcZmlCm2Zj6KGPscCfpGGz/FrXE=; b=TN/dcxjNzsuU9jDvuuF6xFp37P8W/UEWI35U3bi/bDJBm2R0dOHAicSHW2kCBIkl6K Cjl9W+uv3niRFS4kowpShfggq/ICSvkEHXAIrkmBvbgaWP/g0ZA6Ryzw2Y3LD26tmRH4 jAPcBX97lCTd9p1VGQKFeycTdIpDOYie7a8kwKqjzwaeI1uBzJa0CCw3onDDxtezXRIp +oKllgTijmgaK6D6o2aA44ZP/24sCrQGZP1st/u1sMGPFztEW2N1hRSMBeC2HuvINCEq MUrRLd6yXz/A/HpnXvuIHOxXQUtvvZ/9fPE9WYS5oAItAH4Nl8pwcvBd4qK64NwbYSuO BeEQ== X-Gm-Message-State: ALyK8tLDvW4fhtfvg36qrOReMu4tJyHDNdh9l6zg3Oac5egx7Rn7CmWVG91H5xnbyqoJUvD/ X-Received: by 10.46.33.147 with SMTP id h19mr2597280lji.45.1465730635942; Sun, 12 Jun 2016 04:23:55 -0700 (PDT) Received: from P142s.sics.se (62-20-223-105-no193.tbcn.telia.com. [62.20.223.105]) by smtp.gmail.com with ESMTPSA id 204sm2192027ljf.7.2016.06.12.04.23.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 12 Jun 2016 04:23:54 -0700 (PDT) Received: from P142s.sics.se (localhost [127.0.0.1]) by P142s.sics.se (8.15.2/8.15.2) with ESMTPS id u5CBMmBw001765 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 12 Jun 2016 13:22:48 +0200 (CEST) (envelope-from bengta@P142s.sics.se) Received: (from bengta@localhost) by P142s.sics.se (8.15.2/8.15.2/Submit) id u5CBMmvr001764; Sun, 12 Jun 2016 13:22:48 +0200 (CEST) (envelope-from bengta@P142s.sics.se) From: Bengt Ahlgren To: freebsd-x11@freebsd.org Subject: Re: x11/nvidia-driver versions 358.16 and above - lockup when X server starts In-Reply-To: <570ED4B7.6050703@kapsi.fi> (Arto Pekkanen's message of "Thu, 14 Apr 2016 02:22:31 +0300") References: <570ED4B7.6050703@kapsi.fi> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix) Date: Sun, 12 Jun 2016 13:22:48 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jun 2016 11:23:58 -0000 Arto Pekkanen writes: > On 08.04.2016 22:18, Bengt Ahlgren wrote: >> There seems to be a locking problem in the newer nvidia drivers (358.16 >> and above that have the new nvidia-modeset.ko module). These are not in >> the ports tree, but a port patch is being worked on to update it: >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201340 >> >> With a WITNESS kernel, my system always locks up when the X server >> starts after printing this: >> >> Apr 8 19:44:11 ivy kernel: acquiring duplicate lock of same type: >> "os.lock_sx" >> Apr 8 19:44:11 ivy kernel: 1st os.lock_sx @ nvidia_os.c:593 >> Apr 8 19:44:11 ivy kernel: 2nd os.lock_sx @ nvidia_os.c:593 >> Apr 8 19:44:11 ivy kernel: KDB: stack backtrace: >> Apr 8 19:44:11 ivy kernel: db_trace_self_wrapper() at >> db_trace_self_wrapper+0x2b/frame 0xfffffe06651c7410 >> Apr 8 19:44:11 ivy kernel: kdb_backtrace() at >> kdb_backtrace+0x39/frame 0xfffffe06651c74c0 >> Apr 8 19:44:11 ivy kernel: witness_checkorder() at >> witness_checkorder+0xe24/frame 0xfffffe06651c7550 >> Apr 8 19:44:11 ivy kernel: _sx_xlock() at _sx_xlock+0x75/frame >> 0xfffffe06651c7590 >> Apr 8 19:44:11 ivy kernel: os_acquire_mutex() at >> os_acquire_mutex+0x32/frame 0xfffffe06651c75b0 >> Apr 8 19:44:11 ivy kernel: _nv014117rm() at _nv014117rm+0x18/frame >> 0xfffffe000a188e60 >> Apr 8 19:44:11 ivy kernel: dmapbase() at 0xfffff80011527800 >> >> The X server gets at least this far: >> >> [ 164.014] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32 >> [ 164.014] (==) NVIDIA(0): RGB weight 888 >> [ 164.014] (==) NVIDIA(0): Default visual is TrueColor >> [ 164.014] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0) >> [ 164.015] (**) NVIDIA(0): Enabling 2D acceleration >> >> Without WITNESS, it locks up perhaps 1/3 of the time, and works fine >> afterways if it didn't. I run FreeBSD 10.3-PRERELEASE amd64 r296673 on >> a desktop with a Z77 motherboard and a GeForce GTX 550 Ti. >> >> Is there anything that the FreeBSD community can do with this info? I >> have submitted a problem report to NVIDIA. >> >> Bengt > At this point I'd just follow the mentioned bugzilla link and wait for > answer from nVidia. If you get a reply from nVidia, posting it to > bugzilla might help. > > You could also discuss this in the nVidia forums, but I am not sure that > helps. Just for the record: I believe the locking issue I reported has been solved. I have provided the fix to nvidia, and it is also included in the port update patch found at: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201340 This nvidia driver port update (to version 364.19) would benefit from wider testing so that it finally can be committed to the ports tree! There might also be some people on this list that has more insights into the issues with the VT console? Bengt