Received: by 2002:a25:ca44:0:0:0:0:0 with SMTP id a65csp811300ybg; Sun, 26 Jul 2020 23:24:30 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyrtEBIyPwlxOnYUB3RykNVD5RAy4VhXfA18TLeOHxzQrVG8LJandJSeeWUDmcOB1jM53vX X-Received: by 2002:aa7:d88e:: with SMTP id u14mr20165077edq.11.1595831070728; Sun, 26 Jul 2020 23:24:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1595831070; cv=none; d=google.com; s=arc-20160816; b=sLDGYnetBkm86v6mHnvDKcioKzZhQ257fYr431wdSfrwMMhmg02hG5YqnaJzcXURGX JDrTb0ULaXoLIjvjrYc+zqD3ZJEu8W6nMKKnA1vnATP+NvfrNWm88oKiYFV+jkD6tnzg 5Ui5/GnjgYk+0CagAZJgo3XkRaxzuHXRxVnMqL9AJvwtud3LsfE4LwmeZXtctdq4604G mBHDz4zM1vg7d26O8ZfTUCUzRLre7XzDLpUptuPztVVWtKSVKktX6EXSBpiEamTOulXq YsNi293z7s70v3LFTfRvO0B2V30VLoK7TOdf/sB4X+BlIO0+vA/YhAEzTGk8wl7f6hXX HeEA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:organization:references:in-reply-to:date:cc:to:from :subject:message-id:ironport-sdr:ironport-sdr; bh=XkUwQbzfNmGnTsDr3IytTcBJ7fFWZdjTUAbCkbTgQSY=; b=eCbFkiGC9lJFsjUEBK/OAse4j5wqR4YdjDcc6Aofp9KrSUHd4wWNV6XJ5D7t9QF43o m7SvYyDZYD/0fA/N8LpBEUWF+sX6vIYAvaKEReIqpLWUL4cVYJ2Agx/VjT+MAPuh8v8x 2u7vOfZobGU++I/3FDYDbAmijdUcfU6A2t36BzqwI85CfVJ4rza6KAev/X3axk550GA+ RvZiKlsh0UAy6SWD0Aw9h5Pu0hzL1iktT1Gybl79vB4RjAjBOPr95sCM4MMNH0SFl4os H8YuSu9pKIWk48Lq1GN698JsvtlLe6loRBMPZ5zT3fWEzOLHXjxGPbvWDaZT7/7OFMba D0og== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h11si5320211edn.481.2020.07.26.23.23.58; Sun, 26 Jul 2020 23:24:30 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-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-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726163AbgG0GW2 (ORCPT + 99 others); Mon, 27 Jul 2020 02:22:28 -0400 Received: from mga14.intel.com ([192.55.52.115]:53448 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726116AbgG0GW2 (ORCPT ); Mon, 27 Jul 2020 02:22:28 -0400 IronPort-SDR: MvcTnF2hWmXyCFnEXmgTJE26gNESBiL0nmOuZHRt1oIaPo1V/j3ijT0oSnghb/chPZz7Ky2/UX tH/NuqzPoE1w== X-IronPort-AV: E=McAfee;i="6000,8403,9694"; a="150139875" X-IronPort-AV: E=Sophos;i="5.75,401,1589266800"; d="scan'208";a="150139875" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Jul 2020 23:22:28 -0700 IronPort-SDR: cVcA1MbSggbVlEp+p7dXxBiOAuCwWtJzSAgPMiIwkSTcLQQvmiyiUKeDcV/LuesgJvzUyMFGYb smB9QGXQIS4Q== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.75,401,1589266800"; d="scan'208";a="433786627" Received: from bfarkas-mobl.ger.corp.intel.com ([10.249.254.210]) by orsmga004.jf.intel.com with ESMTP; 26 Jul 2020 23:22:26 -0700 Message-ID: <80afa796cefcc78f8a56059b279d6d424bc00d5e.camel@intel.com> Subject: Re: iwlwifi: Direct firmware load for iwl-debug-yoyo.bin failed with error -2 From: Luciano Coelho To: Kalle Valo , Sedat Dilek Cc: Shahar S Matityahu , Johannes Berg , Emmanuel Grumbach , Intel Linux Wireless , linux-wireless@vger.kernel.org Date: Mon, 27 Jul 2020 09:22:25 +0300 In-Reply-To: <87mu3magfp.fsf@tynnyri.adurom.net> References: <87mu3magfp.fsf@tynnyri.adurom.net> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.3-1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Sun, 2020-07-26 at 10:22 +0300, Kalle Valo wrote: > Sedat Dilek writes: > > > Hi, > > > > I am seeing this failed/error message for a long time: > > > > [Sat Jul 25 13:03:28 2020] iwlwifi 0000:01:00.0: Direct firmware load > > for iwl-debug-yoyo.bin failed with error -2 > > > > So, I started to look for the file "iwl-debug-yoyo.bin" in [1], but failed. > > AFAICS this is a file for debugging purposes? > > > > Why do I see such a message as an end-user w/o iwlwifi-debugging enabled? > > For some end-users I can imagine this looks scary and they will look > > into their cupboards and below their beds but will not find any > > monsters. > > > > I found a rename from an ini file to bin here: > > commit 8d9e982bf9bf ("iwlwifi: dbg_ini: rename external debug > > configuration file") > > > > Is "iwl-debug-yoyo.bin" a binary or as before an ini (text) file I > > have to configure somehow. > > > > Does this need to be guarded by some "ifdef CONFIG_IWLWIFI_DEBUG" in > > "drivers/net/wireless/intel/iwlwifi/iwl-dbg-tlv.c"? > > > > Or does drivers/net/wireless/intel/iwlwifi/Makefile needs some tuning > > - as said I have no iwlwifi debugging enabled via Kconfig? > > ... > > iwlwifi-objs += iwl-dbg-tlv.o > > > > Please enlighten me/us? > > > > Thanks. > > > > Regards, > > - Sedat - > > > > [1] https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/ > > [2] https://git.kernel.org/linus/e8d9e982bf9bf0e6f99099f1f09a37563b2b95b5 > > > > > From my dmesg-output: > > > > [Sa Jul 25 13:03:28 2020] iwlwifi 0000:01:00.0: can't disable ASPM; OS > > doesn't have ASPM control > > [Sa Jul 25 13:03:28 2020] iwlwifi 0000:01:00.0: loaded firmware > > version 18.168.6.1 6000g2b-6.ucode op_mode iwldvm > > [Sa Jul 25 13:03:28 2020] iwlwifi 0000:01:00.0: Direct firmware load > > for iwl-debug-yoyo.bin failed with error -2 > > There's an RFC patch about this: > > https://patchwork.kernel.org/patch/11625759/ > > I think that should be applied. Intel folks, should I take that directly > to wireless-drivers-next? As I wrote in the other thread, yes, please. Go ahead and merge it. -- Cheers, Luca.