From: Paul Bolle <pebolle@tiscali.nl>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: v3.14-rc1+: new error: "nsc-ircc, Wrong chip version ff"
Date: Sun, 16 Mar 2014 22:41:35 +0100 [thread overview]
Message-ID: <1395006095.2002.8.camel@x41> (raw)
Rafael,
0) Ever since v3.14-rc1 I've noticed two new boot messages on an,
outdated, ThinkPad X41:
nsc-ircc, Found chip at base=0x164e
nsc-ircc, Wrong chip version ff
The first is printed at info level, so I would have ignored it, but the
second is printed at error level.
1) I've finally managed to bisect these messages to commit 202317a573b2
("ACPI / scan: Add acpi_device objects for all device nodes in the
namespace"). That's a rather big commit, so I've not even bothered to
try to revert it on top on v3.14-rc6.
2) What should I do to make that error go away?
Paul Bolle
next reply other threads:[~2014-03-16 21:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-16 21:41 Paul Bolle [this message]
2014-03-17 0:02 ` v3.14-rc1+: new error: "nsc-ircc, Wrong chip version ff" Rafael J. Wysocki
2014-03-17 12:33 ` Paul Bolle
2014-03-17 13:24 ` Rafael J. Wysocki
2014-03-18 14:00 ` Bjørn Mork
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=1395006095.2002.8.camel@x41 \
--to=pebolle@tiscali.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael.j.wysocki@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox