From nobody Fri Jan 21 02:24:50 2022 X-Original-To: stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 52CEA19666AC; Fri, 21 Jan 2022 02:24:50 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Jg39t1z8Sz4m4G; Fri, 21 Jan 2022 02:24:50 +0000 (UTC) (envelope-from danfe@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1642731890; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=HtogBRZl4abwCbCjHTi/LYXKbOqi/z/RJbP+vfbsZlI=; b=PB7aALLjdJMz43klvXsh0NP8unSgMPcv5ElNPqywax+LLsim9V8puQ5kXaKy/UBTX9UIyI ke+/ydxCtRD70Vn4pR0L7g8aOCDcD2YymWkUffs7vHVOFBXEXVRq09sITnHOh0cYyTsF7O nj/8mmv6qLwZuoW3/fXsTXmpvTRqazj2XS0DlErX9VCPM+EAMZLRHzHmvttQN3Tvzv0NR6 B6WzB2AHX5dc6P4yo4/OvWw4c31x4nvRdkt2gsvm+rfJEo6PICNwefHOJcohZbi181Pj58 2f019a13Vb+xBDlDIWQbTzw+NV7p2DMiqdmqP6SI8oUu7cPirY8JaoR0oJry/A== Received: by freefall.freebsd.org (Postfix, from userid 1033) id 2B0D12AF1; Fri, 21 Jan 2022 02:24:50 +0000 (UTC) Date: Fri, 21 Jan 2022 02:24:50 +0000 From: Alexey Dokuchaev To: Ultima Cc: Andriy Gapon , x11@freebsd.org, freebsd-stable List Subject: Re: nvidia driver crash Message-ID: References: <0db4cfd1-363e-eeee-96d8-22d80bd9dc95@FreeBSD.org> List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1642731890; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=HtogBRZl4abwCbCjHTi/LYXKbOqi/z/RJbP+vfbsZlI=; b=DrPlSZArkBewZYfATzpzgJP5JaMFB98CRqzQcCw6qjJ33L6mUIoy+Y2bXh0BX/2b+ZRmVp JHL2QdZ4AIIRUqud7TKEsIkjhVtxVXUdkRJCUQ5jcWE9bjei4mRs+rhtb/HbY3ED1T0+N5 xp87aW/PjCm3RjYoqI/D+i4N6V2K1QuOuyPiSxCxFkxasD83VAcJl6XRh4Rj5g5ZNgiPLV +NefyBncCXXUZtu1Js39Ml57EHZPR7E01sq9MJEVpma5Oe/z/U7UP1RYA2AUg34IRZk/zT avgIEFEyoBzkzvzP/cDltx/IVjJaMt5dwLtyHqPRhupDDAh3CodWcZmyPAV8Qw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1642731890; a=rsa-sha256; cv=none; b=C79wNkwwVkLSHetEcKdI9N9rfLGbakDfny9iihacIvHFH2adPi6Z5X1ihQRA4Yie0u2K3B Rz7hK4mFZD1EQs0OYDXJCbbXUXowEWAbJpZTAaxJ1MgTFksbAyOF5N2FMGv7yNNjsaNiZl wNlxYJmfxU6AReI/IqBXJvQGdykBr7VEihIW1emr6Np5Y5IAIbe87oxSeim4bvco0qwLDv S7oKpfA3ZV2m+CJS+zt5/G9AU8eYZWoCfrw2twOO13IJ414HkLxLrwJ5rFdevgyNFZfIuf 9ChVL84ZXCbFQ3LO9y1iNaC38Hc+KcDBmaejmm+oMSc1xO9vPKmcwBcE5F6wrg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On Thu, Jan 20, 2022 at 03:38:56PM -0800, Ultima wrote: > Hey Alexey and Andriy, > > Just so happens I'm currently with Nvidia in the networking department. I > opened an internal bug linking to 251015. I don't know anyone in the GPU > department, but at least now it may get some visibility. Thank you! Note that there are several crash/panic reports about those proprietary Resource Manager bits, PR 251015 is just one of them and is likely not exactly the same issue Andriy's seeing. Comments #7 and #9, however, contain pointers to other possibly related bugs. ./danfe