mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Neil Horman <nhorman@tuxdriver.com>,
	Ming Lei <ming.lei@canonical.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: firmware: new "platform microcode" warning in v3.13-rc1+
Date: Sun, 01 Dec 2013 18:32:05 +0100	[thread overview]
Message-ID: <1385919125.7199.17.camel@x41.thuisdomein> (raw)

0) Booting v3.13-rc1 and v3.13-rc2 triggers two new warnings on an
(outdated, I'm afraid) ThinkPad X41:
    [...]
    <6>[   16.746119] libipw: 802.11 data/management/control stack, git-1.1.13
    <6>[   16.746125] libipw: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
    <4>[   16.761998] platform microcode: Direct firmware load failed with error -2
    <4>[   16.762022] platform microcode: Falling back to user helper
    <6>[   16.787885] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
    <6>[   16.787895] ipw2200: Copyright(c) 2003-2006 Intel Corporation
    <6>[   16.788741] ipw2200: Detected Intel PRO/Wireless 2915ABG Network Connection
    [...]

(I've added the surrounding lines because they suggest this is about the
firmware for that wireless device. Please note that this device appears
to work no worse than it did under v3.12.)

1) These warnings can be traced back to commit 3e358ac2bb5b ("firmware:
Be a bit more verbose about direct firmware loading failure").

2) Is there something I'm supposed to do to silence these warnings? If
so, what would that be? If not, can these messages perhaps be downgraded
to dev_info or dev_notice?


Paul Bolle


             reply	other threads:[~2013-12-01 17:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-01 17:32 Paul Bolle [this message]
2013-12-24  1:15 ` Ming Lei
2013-12-24 14:32   ` Takashi Iwai

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=1385919125.7199.17.camel@x41.thuisdomein \
    --to=pebolle@tiscali.nl \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@canonical.com \
    --cc=nhorman@tuxdriver.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

all inboxes | Powered by JetHome®