From: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Brian Bian <brian.bian@linux.intel.com>,
Eduardo Valentin <edubezval@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 4.14 kernel and acpi INT3400:00: Unsupported event [0x86]
Date: Sat, 20 Jan 2018 18:53:47 +0100 [thread overview]
Message-ID: <201801201853.47715.a.miskiewicz@gmail.com> (raw)
In-Reply-To: <1510726232.2418.83.camel@intel.com>
On Wednesday 15 of November 2017, Zhang Rui wrote:
> Hi, Brian,
>
> thanks for your quick fix, as it is in merge window right now, I will
> queue it for for next -rc2.
Don't see it merged (4.15.0-rc8). Any problems with it?
>
> thanks,
> rui
>
> On Tue, 2017-11-14 at 10:50 -0700, Brian Bian wrote:
> > I have submitted a patch to suppress such messages. The INT3400
> > driver
> > currently handles 0x83 thermal-relationship-table-change event
> > only, and all other ACPI notification codes are unknown/irrelevant
> > to the INT3400 driver.
> >
> > Thanks,
> > -Brian
> >
> > On Mon, 13 Nov 2017, Arkadiusz Miskiewicz wrote:
> > > On Monday 13 of November 2017, Zhang Rui wrote:
> > > > On Sun, 2017-11-12 at 23:25 +0100, Arkadiusz Miskiewicz wrote:
> > > > > Hello.
> > > > >
> > > > > On Dell XPS 9530 and 4.14 kernel dmesg is flooded with:
> > > > >
> > > > > [ 292.580807] acpi INT3400:00: Unsupported event [0x86]
> > > > > [ 299.284648] acpi INT3400:00: Unsupported event [0x86]
> > > > > [ 305.648079] acpi INT3400:00: Unsupported event [0x86]
> > > > > [ 315.444799] acpi INT3400:00: Unsupported event [0x86]
> > > > > [ 317.432412] acpi INT3400:00: Unsupported event [0x86]
> > > > > [ 319.420239] acpi INT3400:00: Unsupported event [0x86]
> > > > > [ 321.408476] acpi INT3400:00: Unsupported event [0x86]
> > > > > [ 323.400304] acpi INT3400:00: Unsupported event [0x86]
> > > > > [ 325.388358] acpi INT3400:00: Unsupported event [0x86]
> > > > >
> > > > > What 0x86 might mean?
> > > >
> > > > please attach the acpidump output.
> > >
> > > Attached.
> > >
> > > > thanks,
> > > > rui
> > >
> > > --
> > > Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
--
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
prev parent reply other threads:[~2018-01-20 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 22:25 4.14 kernel and acpi INT3400:00: Unsupported event [0x86] Arkadiusz Miskiewicz
2017-11-13 0:09 ` Zhang Rui
2017-11-13 5:54 ` Arkadiusz Miskiewicz
2017-11-14 17:50 ` Brian Bian
2017-11-15 6:10 ` Zhang Rui
2018-01-20 17:53 ` Arkadiusz Miskiewicz [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=201801201853.47715.a.miskiewicz@gmail.com \
--to=a.miskiewicz@gmail.com \
--cc=arekm@maven.pl \
--cc=brian.bian@linux.intel.com \
--cc=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.zhang@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;
as well as URLs for NNTP newsgroup(s).