From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.1 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8071CC48BD1 for ; Wed, 9 Jun 2021 13:47:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6C143610A2 for ; Wed, 9 Jun 2021 13:47:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234928AbhFINtK (ORCPT ); Wed, 9 Jun 2021 09:49:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57370 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236585AbhFINtK (ORCPT ); Wed, 9 Jun 2021 09:49:10 -0400 Received: from mail.kapsi.fi (mail.kapsi.fi [IPv6:2001:67c:1be8::25]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 652A5C061574 for ; Wed, 9 Jun 2021 06:47:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kapsi.fi; s=20161220; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Date: Message-ID:Subject:From:Cc:To:Sender:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=+fk3mv9ffvCqAu4Aewr2SlJtqBKj6DnprNXAVOj855w=; b=zjandDfYHqshA7iQHT9Fql8buv a3IbpUXDMy0SFjosB2lKVD0NffpbFgfSGaFC1p1cHp620iis+R/zW3zTaiRVBAs/89xH3L/sR1ied /oN4jf1rLBq+hsWc3p6iCdo4YXvBtmKO91h/oIyz/mX8NLbFFW1AOFqXxFyaWbqCB/OqEo6yd1J7N x3aCnnbfAtr7hBINDKw5KAXSKgeIuDVWrMjR6g7Dum/m72icrQ+tM8jznnS+gSaV+RVSaqmo/1aG2 gjHs62MSQ9QQGsfB7wLExY98Rqm4MvzWPlH91PVV5ZFDfIEsrUrBdl4BU7s3QFYW5p6GG1C5lGDt9 qK8blIiA==; Received: from dsl-hkibng22-54f986-236.dhcp.inet.fi ([84.249.134.236] helo=[192.168.1.10]) by mail.kapsi.fi with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1lqyY0-0002vZ-TE; Wed, 09 Jun 2021 16:47:08 +0300 To: christian.koenig@amd.com Cc: matthew.auld@intel.com, ray.huang@amd.com, dri-devel , nouveau@lists.freedesktop.org, linux-tegra From: Mikko Perttunen Subject: Trouble with TTM patches w/nouveau in linux-next Message-ID: <2e4987b0-7fc9-d217-450c-943de430dbd1@kapsi.fi> Date: Wed, 9 Jun 2021 16:47:08 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 84.249.134.236 X-SA-Exim-Mail-From: cyndis@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false Precedence: bulk List-ID: X-Mailing-List: linux-tegra@vger.kernel.org Hi, I'm observing nouveau not initializing recently on linux-next on my Tegra186 Jetson TX2 board. Specifically it looks like BO allocation is failing when initializing the sync subsystem: [ 21.858149] nouveau 17000000.gpu: DRM: failed to initialise sync subsystem, -28 I have been bisecting and I have found two patches that affect this. Firstly, things first break on d02117f8efaa drm/ttm: remove special handling for non GEM drivers starting to return error code -12. Then, at d79025c7f5e3 drm/ttm: always initialize the full ttm_resource v2 the error code changes to the above -28. If I checkout one commit prior to d79025c7f5e3 and revert d02117f8efaa, things work again. There are a bunch of other TTM commits between this and HEAD, so reverting these on top of HEAD doesn't work. However, I checked that both yesterday's and today's nexts are also broken. Thank you, Mikko From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.1 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3690CC48BCF for ; Wed, 9 Jun 2021 14:20:52 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 75297613B9 for ; Wed, 9 Jun 2021 14:20:51 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 75297613B9 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kapsi.fi Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=nouveau-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id CE87F6E3F0; Wed, 9 Jun 2021 14:20:50 +0000 (UTC) X-Greylist: delayed 2015 seconds by postgrey-1.36 at gabe; Wed, 09 Jun 2021 14:20:49 UTC Received: from mail.kapsi.fi (mail.kapsi.fi [IPv6:2001:67c:1be8::25]) by gabe.freedesktop.org (Postfix) with ESMTPS id D3EF86E3F0 for ; Wed, 9 Jun 2021 14:20:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kapsi.fi; s=20161220; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Date: Message-ID:Subject:From:Cc:To:Sender:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=+fk3mv9ffvCqAu4Aewr2SlJtqBKj6DnprNXAVOj855w=; b=zjandDfYHqshA7iQHT9Fql8buv a3IbpUXDMy0SFjosB2lKVD0NffpbFgfSGaFC1p1cHp620iis+R/zW3zTaiRVBAs/89xH3L/sR1ied /oN4jf1rLBq+hsWc3p6iCdo4YXvBtmKO91h/oIyz/mX8NLbFFW1AOFqXxFyaWbqCB/OqEo6yd1J7N x3aCnnbfAtr7hBINDKw5KAXSKgeIuDVWrMjR6g7Dum/m72icrQ+tM8jznnS+gSaV+RVSaqmo/1aG2 gjHs62MSQ9QQGsfB7wLExY98Rqm4MvzWPlH91PVV5ZFDfIEsrUrBdl4BU7s3QFYW5p6GG1C5lGDt9 qK8blIiA==; Received: from dsl-hkibng22-54f986-236.dhcp.inet.fi ([84.249.134.236] helo=[192.168.1.10]) by mail.kapsi.fi with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1lqyY0-0002vZ-TE; Wed, 09 Jun 2021 16:47:08 +0300 To: christian.koenig@amd.com From: Mikko Perttunen Message-ID: <2e4987b0-7fc9-d217-450c-943de430dbd1@kapsi.fi> Date: Wed, 9 Jun 2021 16:47:08 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 MIME-Version: 1.0 Content-Language: en-US X-SA-Exim-Connect-IP: 84.249.134.236 X-SA-Exim-Mail-From: cyndis@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false Subject: [Nouveau] Trouble with TTM patches w/nouveau in linux-next X-BeenThere: nouveau@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Nouveau development list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-tegra , nouveau@lists.freedesktop.org, ray.huang@amd.com, matthew.auld@intel.com, dri-devel Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: nouveau-bounces@lists.freedesktop.org Sender: "Nouveau" Hi, I'm observing nouveau not initializing recently on linux-next on my Tegra186 Jetson TX2 board. Specifically it looks like BO allocation is failing when initializing the sync subsystem: [ 21.858149] nouveau 17000000.gpu: DRM: failed to initialise sync subsystem, -28 I have been bisecting and I have found two patches that affect this. Firstly, things first break on d02117f8efaa drm/ttm: remove special handling for non GEM drivers starting to return error code -12. Then, at d79025c7f5e3 drm/ttm: always initialize the full ttm_resource v2 the error code changes to the above -28. If I checkout one commit prior to d79025c7f5e3 and revert d02117f8efaa, things work again. There are a bunch of other TTM commits between this and HEAD, so reverting these on top of HEAD doesn't work. However, I checked that both yesterday's and today's nexts are also broken. Thank you, Mikko _______________________________________________ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.1 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B6475C48BDF for ; Wed, 9 Jun 2021 13:47:17 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id CC5F8610A2 for ; Wed, 9 Jun 2021 13:47:16 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org CC5F8610A2 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kapsi.fi Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=dri-devel-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 337676E3F9; Wed, 9 Jun 2021 13:47:16 +0000 (UTC) Received: from mail.kapsi.fi (mail.kapsi.fi [IPv6:2001:67c:1be8::25]) by gabe.freedesktop.org (Postfix) with ESMTPS id 3C4376E3D3 for ; Wed, 9 Jun 2021 13:47:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kapsi.fi; s=20161220; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Date: Message-ID:Subject:From:Cc:To:Sender:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=+fk3mv9ffvCqAu4Aewr2SlJtqBKj6DnprNXAVOj855w=; b=zjandDfYHqshA7iQHT9Fql8buv a3IbpUXDMy0SFjosB2lKVD0NffpbFgfSGaFC1p1cHp620iis+R/zW3zTaiRVBAs/89xH3L/sR1ied /oN4jf1rLBq+hsWc3p6iCdo4YXvBtmKO91h/oIyz/mX8NLbFFW1AOFqXxFyaWbqCB/OqEo6yd1J7N x3aCnnbfAtr7hBINDKw5KAXSKgeIuDVWrMjR6g7Dum/m72icrQ+tM8jznnS+gSaV+RVSaqmo/1aG2 gjHs62MSQ9QQGsfB7wLExY98Rqm4MvzWPlH91PVV5ZFDfIEsrUrBdl4BU7s3QFYW5p6GG1C5lGDt9 qK8blIiA==; Received: from dsl-hkibng22-54f986-236.dhcp.inet.fi ([84.249.134.236] helo=[192.168.1.10]) by mail.kapsi.fi with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1lqyY0-0002vZ-TE; Wed, 09 Jun 2021 16:47:08 +0300 To: christian.koenig@amd.com From: Mikko Perttunen Subject: Trouble with TTM patches w/nouveau in linux-next Message-ID: <2e4987b0-7fc9-d217-450c-943de430dbd1@kapsi.fi> Date: Wed, 9 Jun 2021 16:47:08 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 84.249.134.236 X-SA-Exim-Mail-From: cyndis@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-tegra , nouveau@lists.freedesktop.org, ray.huang@amd.com, matthew.auld@intel.com, dri-devel Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" Hi, I'm observing nouveau not initializing recently on linux-next on my Tegra186 Jetson TX2 board. Specifically it looks like BO allocation is failing when initializing the sync subsystem: [ 21.858149] nouveau 17000000.gpu: DRM: failed to initialise sync subsystem, -28 I have been bisecting and I have found two patches that affect this. Firstly, things first break on d02117f8efaa drm/ttm: remove special handling for non GEM drivers starting to return error code -12. Then, at d79025c7f5e3 drm/ttm: always initialize the full ttm_resource v2 the error code changes to the above -28. If I checkout one commit prior to d79025c7f5e3 and revert d02117f8efaa, things work again. There are a bunch of other TTM commits between this and HEAD, so reverting these on top of HEAD doesn't work. However, I checked that both yesterday's and today's nexts are also broken. Thank you, Mikko