public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: Kees Cook <keescook@chromium.org>,
	"Luis R. Rodriguez" <mcgrof@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: log spammed with "loading xx failed with error -2" since commit e40ba6d56b [replace call to fw_read_file_contents() with kernel version]
Date: Sat, 27 Feb 2016 17:49:38 +0100	[thread overview]
Message-ID: <56D1D3A2.70605@gmail.com> (raw)

Since this commit my system log is spammed with firmware load errors. One example:

loading /lib/firmware/updates/4.5.0-rc5-next-20160226/iwlwifi-3160-16.ucode failed with error -2
loading /lib/firmware/updates/iwlwifi-3160-16.ucode failed with error -2
loading /lib/firmware/4.5.0-rc5-next-20160226/iwlwifi-3160-16.ucode failed with error -2
-> finally load attempt from /lib/firmware/iwlwifi-3160-16.ucode succeeds

Before this commit, when a load from one path in fw_path failed, silently the next path was tried.
Only if all attempts failed an error message was printed.
Now for each single failed attempt an error message is printed what doesn't make sense.

             reply	other threads:[~2016-02-27 16:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-27 16:49 Heiner Kallweit [this message]
2016-02-27 23:15 ` log spammed with "loading xx failed with error -2" since commit e40ba6d56b [replace call to fw_read_file_contents() with kernel version] Luis R. Rodriguez
2016-02-28  0:19   ` Mimi Zohar
2016-02-28  2:27   ` Kees Cook
2016-02-28 14:10     ` Ming Lei
2016-02-28 20:57       ` Luis R. Rodriguez
2016-02-28 23:25         ` Kees Cook
2016-02-29  1:07         ` Ming Lei
2016-02-29  7:41         ` James Morris

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=56D1D3A2.70605@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=zohar@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox