mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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
Subject: Re: 4.14 kernel and acpi INT3400:00: Unsupported event [0x86]
Date: Mon, 13 Nov 2017 06:54:42 +0100	[thread overview]
Message-ID: <201711130654.42223.a.miskiewicz@gmail.com> (raw)
In-Reply-To: <1510531774.2418.0.camel@intel.com>

[-- Attachment #1: Type: Text/Plain, Size: 942 bytes --]

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 )

[-- Attachment #2: acpidump.txt.gz --]
[-- Type: application/gzip, Size: 135542 bytes --]

  reply	other threads:[~2017-11-13  5:54 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 [this message]
2017-11-14 17:50     ` Brian Bian
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=201711130654.42223.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

Powered by JetHome