From: Brian Bian <brian.bian@linux.intel.com>
To: arekm@maven.pl
Cc: Zhang Rui <rui.zhang@intel.com>,
Brian Bian <brian.bian@linux.intel.com>,
Eduardo Valentin <edubezval@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: 4.14 kernel and acpi INT3400:00: Unsupported event [0x86]
Date: Tue, 14 Nov 2017 09:50:38 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.20.1711140940360.3973@bbian-trusty> (raw)
In-Reply-To: <201711130654.42223.a.miskiewicz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
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 )
>
next prev parent reply other threads:[~2017-11-14 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 22:25 Arkadiusz Miskiewicz
2017-11-13 0:09 ` Zhang Rui
2017-11-13 5:54 ` Arkadiusz Miskiewicz
2017-11-14 17:50 ` Brian Bian [this message]
2017-11-15 6:10 ` Zhang Rui
2018-01-20 17:53 ` Arkadiusz Miskiewicz
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=alpine.DEB.2.20.1711140940360.3973@bbian-trusty \
--to=brian.bian@linux.intel.com \
--cc=arekm@maven.pl \
--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
all inboxes | Powered by JetHome®