All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Luca Coelho <luciano.coelho@intel.com>,
	Shahar S Matityahu <shahar.s.matityahu@intel.com>,
	Johannes Berg <johannes.berg@intel.com>,
	Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
	Intel Linux Wireless <linuxwifi@intel.com>,
	linux-wireless@vger.kernel.org
Subject: Re: iwlwifi: Direct firmware load for iwl-debug-yoyo.bin failed with error -2
Date: Sun, 26 Jul 2020 10:22:50 +0300	[thread overview]
Message-ID: <87mu3magfp.fsf@tynnyri.adurom.net> (raw)
In-Reply-To: <CA+icZUWoycCvAAs5H0sigHTB+GGhX5NRVonYqKg7BRLB97dGkA@mail.gmail.com> (Sedat Dilek's message of "Sat, 25 Jul 2020 14:11:32 +0200")

Sedat Dilek <sedat.dilek@gmail.com> 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?

-- 
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2020-07-26  7:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-25 12:11 iwlwifi: Direct firmware load for iwl-debug-yoyo.bin failed with error -2 Sedat Dilek
2020-07-26  7:22 ` Kalle Valo [this message]
2020-07-27  6:22   ` Luciano Coelho
2020-07-27 17:52     ` Sedat Dilek
2020-07-28 13:13   ` Sedat Dilek
2020-07-28 21:23     ` Sedat Dilek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mu3magfp.fsf@tynnyri.adurom.net \
    --to=kvalo@codeaurora.org \
    --cc=emmanuel.grumbach@intel.com \
    --cc=johannes.berg@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linuxwifi@intel.com \
    --cc=luciano.coelho@intel.com \
    --cc=sedat.dilek@gmail.com \
    --cc=shahar.s.matityahu@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.