Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp2287537pxb; Fri, 29 Jan 2021 20:09:07 -0800 (PST) X-Google-Smtp-Source: ABdhPJw1hMfz0HUzN70YYYD6J2cqSA8DnZB1uAxQE9yNahrsDIKrYDjp6O+J8fLoUSFkf0v8go92 X-Received: by 2002:a05:6402:d05:: with SMTP id eb5mr8277319edb.143.1611979747424; Fri, 29 Jan 2021 20:09:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611979747; cv=none; d=google.com; s=arc-20160816; b=ftLQHCY9vhemmavk/nHbOyp+aVOspuLRXM2oI8D5BvuigHIWnTaXrxFqPvFU/E3o8H a2zaQwvobxNboEXr13YEQMzoNSnPAXCFTg0jThtjYdDDbI+xOWiNsQw75Jqv4woMDrNY DIGO9Q1ThjYoDERskdvKc7H3p+MNWQ2qvuKKQFTS7NFRezD+qIf8EeYxWzoMpQh/UHGx 7wSTOaAJGrRgR3BAYnzPexpMr6qU+H7caKcocFKRjahbVpirtIGkHHVQ5scBXNjdMhPP WO9P7x9+JdsXQlgkKAF8B2k+HDsiabccJ/Lx0miQ5Cg0Olxrks9MfJigDWzDSnp+dKu7 UGXA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=03whUntc8KWgWwxaQVmYFN71FeSnyqMeiAdzLOx9jzE=; b=Y0wZOPeYXn0PD1+pjb3jIMtSIxsYAlxiwlQT8dshkY7hbXpWG0Zu66mtf7b463OSG/ RRHotqFFIqsqB1nH4R08BPH4BkeHnxj/Ih581ApLbgk96bklbj3gdgFzg7SF3a/NI/GQ 0NmprWlp1ibTnkoN6dDu/8lEqKcLYi6sGPWT1YrckszHTERCxm+5RLwyOyvQtDfywpX9 ykIfcUpsYwtqeOYHj8060gFJ8EJV1/CRbzPafOwisaZ/U18YmLk9wB6G0ivwcvNOSiEy kpkmHuoCN/oGGtSzDEDiItVIJD02fnXdRznZ1RYJRuKz6WUs/XITI3tU7/9UB2bBhA6d JJGA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id t7si6334604edr.333.2021.01.29.20.08.27; Fri, 29 Jan 2021 20:09:07 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233602AbhA3DnB (ORCPT + 99 others); Fri, 29 Jan 2021 22:43:01 -0500 Received: from magic.merlins.org ([209.81.13.136]:41460 "EHLO mail1.merlins.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233560AbhA3Dfh (ORCPT ); Fri, 29 Jan 2021 22:35:37 -0500 Received: from [172.58.39.25] (port=59580 helo=sauron.svh.merlins.org) by mail1.merlins.org with esmtpsa (Cipher TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92 #3) id 1l5fcS-0005BV-1m by authid with srv_auth_plain; Fri, 29 Jan 2021 18:04:12 -0800 Received: from merlin by sauron.svh.merlins.org with local (Exim 4.92) (envelope-from ) id 1l5fcR-00008T-Dt; Fri, 29 Jan 2021 18:04:11 -0800 Date: Fri, 29 Jan 2021 18:04:11 -0800 From: Marc MERLIN To: Bjorn Helgaas Cc: nouveau@lists.freedesktop.org, Mika Westerberg , LKML , Linux PCI Subject: Re: 5.9.11 still hanging 2mn at each boot and looping on nvidia-gpu 0000:01:00.3: PME# enabled (Quadro RTX 4000 Mobile) Message-ID: <20210130020411.GZ29348@merlins.org> References: <20210129005626.GP29348@merlins.org> <20210129212032.GA99457@bjorn-Precision-5520> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210129212032.GA99457@bjorn-Precision-5520> X-Sysadmin: BOFH X-URL: http://marc.merlins.org/ X-Broken-Reverse-DNS: no host name for IP address 172.58.39.25 X-SA-Exim-Connect-IP: 172.58.39.25 X-SA-Exim-Mail-From: marc_nouveau@merlins.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 29, 2021 at 03:20:32PM -0600, Bjorn Helgaas wrote: > > For comparison the intel iwlwifi driver is very clear about firmware > > it's trying to load, if it can't and what exact firmware you need to > > find on the internet (filename) > > I guess you're referring to this in iwl_request_firmware()? > > IWL_ERR(drv, "check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git\n"); Yes :) > How can we fix this in nouveau so we don't have the debug this again? > I don't really know how firmware loading works, but "git grep -A5 > request_firmware drivers/gpu/drm/nouveau/" shows that we generally > print something when request_firmware() fails. Well, have a look at https://pastebin.com/dX19aCpj do you see any warning whatsoever? > But I didn't notice those messages in your logs, so I'm probably > barking up the wrong tree. you're not It seems that newer kernels are a bit better: [ 189.304662] nouveau 0000:01:00.0: pmu: firmware unavailable [ 189.312455] nouveau 0000:01:00.0: disp: destroy running... [ 189.316552] nouveau 0000:01:00.0: disp: destroy completed in 1us [ 189.320326] nouveau 0000:01:00.0: disp ctor failed, -12 [ 189.324214] nouveau: probe of 0000:01:00.0 failed with error -12 So, it probably got better, but that message got displayed after the 2mn hang that having the firmware, stops from happening. whichever developer with the right hardware can probably easily reproduce this by removing the firmware and looking at the boot messages. At the very least, it should print something more clear "driver will not function properly", and a URL to where one can get the driver, would be awesome. > So maybe the wakeups are related to having vs not having the nouveau > firmware? I'm still curious about that, and it smells like a bug to > me, but probably something to do with nouveau where I have no hope of > debugging it. Right. Honestly, given the time I've lost with this, and now that it seems gone with the firmware, I'm happy to leave well enough alone :) I'm not sure how you are involved with the driver, but are you able to help improve the dmesg output? Thanks, Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Home page: http://marc.merlins.org/ | PGP 7F55D5F27AAF9D08