From: "Winkler, Tomas" <tomas.winkler@intel.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Usyskin, Alexander" <alexander.usyskin@intel.com>
Subject: RE: Could not read FW version, FW version command failed -5
Date: Thu, 5 Sep 2019 13:00:18 +0000 [thread overview]
Message-ID: <5B8DA87D05A7694D9FA63FD143655C1B9DCB0429@hasmsx108.ger.corp.intel.com> (raw)
In-Reply-To: <857e1cae-dbcb-4a47-2f43-5e0a1aa4fe65@molgen.mpg.de>
> Dear Tomas,
>
>
> Testing Fedora 30 with Linux 5.2.11 on an old Dell OptiPlex 980, Linux
> log the message below.
>
> [ 15.964298] mei mei::55213584-9a29-4916-badf-0fb7ed682aeb:01: Could
> not read FW version
> [ 15.964301] mei mei::55213584-9a29-4916-badf-0fb7ed682aeb:01: FW
> version command failed -5
>
> The prints happen in `drivers/misc/mei/bus-fixup.c`.
>
> ret = 0;
> bytes_recv = __mei_cl_recv(cldev->cl, buf, sizeof(buf), 0,
> MKHI_RCV_TIMEOUT);
> if (bytes_recv < 0 || (size_t)bytes_recv < MKHI_FWVER_LEN(1)) {
> /*
> * Should be at least one version block,
> * error out if nothing found
> */
> dev_err(&cldev->dev, "Could not read FW version\n");
> return -EIO;
> }
>
> The Web is full of these messages, so it does seem like a normal
> condition on certain devices. Do you know the reason? Do older Intel
> MEs support this?
Wow, this quite an old system ~ 2009, the FW version has a bit different format there, it was overlooked, will look at that ASAP, thanks for the report.
Tomas
prev parent reply other threads:[~2019-09-05 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 14:50 Could not read FW version, FW version command failed -5 Paul Menzel
2019-09-05 13:00 ` Winkler, Tomas [this message]
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=5B8DA87D05A7694D9FA63FD143655C1B9DCB0429@hasmsx108.ger.corp.intel.com \
--to=tomas.winkler@intel.com \
--cc=alexander.usyskin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
/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;
as well as URLs for NNTP newsgroup(s).