From: Atri Bhattacharya <A.Bhattacharya@ulg.ac.be>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [RFC 0/4] Intel Integrated Sensor Hub Support (ISH)
Date: Fri, 03 Jun 2016 01:13:00 +0200 [thread overview]
Message-ID: <1464909180.2065.1.camel@ulg.ac.be> (raw)
In-Reply-To: <1464908239.2722.7.camel@aim.com>
On Fri, 2016-06-03 at 00:57 +0200, Atri Bhattacharya wrote:
> I see messages like this on the journal when rotating my laptop:
>
> Jun 03 00:48:38 tp-yoga260 kernel: thinkpad_acpi: unknown possible
> thermal alarm or keyboard event received
> Jun 03 00:48:38 tp-yoga260 kernel: thinkpad_acpi: unhandled HKEY
> event 0x60f0
> Jun 03 00:48:38 tp-yoga260 kernel: thinkpad_acpi: please report the
> conditions when this event happened to ibm-acpi-devel@lists.sourcefor
> ge.net
> Jun 03 00:48:40 tp-yoga260 kernel: SFW2-INext-DROP-DEFLT IN=wlp4s0
> OUT= MAC=33:33:00:00:00:fb:a8:bb:cf:1d:c3:da:86:dd
> SRC=fe80:0000:0000:0000:aabb:cfff:fe1d:c3da
> DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=208 TC=0 HOPLIMIT=255
> FLOWLBL=311501 PROTO=UDP SPT=5353 DPT=5353 LEN=168
>
>
Actually, these show up even when rotation is working, i.e. before a
suspend/wakeup cycle. So probably just a red herring...
--
Atri Bhattacharya
IFPA, Institut de Physique Bât B5a, AGO Department
Université de Liège, Sart Tilman, 4000 Liège, Belgium
Phone: +32 4 366 36 38
Fri 3 Jun 01:11:27 CEST 2016
Sent from openSUSE Tumbleweed (20160531)
next prev parent reply other threads:[~2016-06-02 23:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 4:27 [RFC 0/4] Intel Integrated Sensor Hub Support (ISH) Srinivas Pandruvada
2016-05-31 4:27 ` [RFC 1/4] Documentation: hid: Intel ISH HID document Srinivas Pandruvada
2016-05-31 4:27 ` [RFC 2/4] hid: intel_ish-hid: ISH Transport layer Srinivas Pandruvada
2016-05-31 4:27 ` [RFC 3/4] hid: intel-ish-hid: ipc layer Srinivas Pandruvada
2016-05-31 4:27 ` [RFC 4/4] hid: intel-ish-hid: ISH HID client driver Srinivas Pandruvada
2016-06-01 13:36 ` [RFC 0/4] Intel Integrated Sensor Hub Support (ISH) Atri Bhattacharya
2016-06-02 3:27 ` Srinivas Pandruvada
2016-06-02 7:48 ` Atri Bhattacharya
2016-06-02 16:49 ` Srinivas Pandruvada
2016-06-02 19:42 ` Atri Bhattacharya
2016-06-02 20:00 ` Srinivas Pandruvada
2016-06-02 21:44 ` Pandruvada, Srinivas
2016-06-02 22:29 ` Atri Bhattacharya
2016-06-02 22:48 ` Srinivas Pandruvada
2016-06-02 22:57 ` Atri Bhattacharya
2016-06-02 23:13 ` Atri Bhattacharya [this message]
2016-06-03 2:50 ` Atri Bhattacharya
2016-06-03 4:01 ` Srinivas Pandruvada
2016-06-03 3:08 ` Atri Bhattacharya
2016-06-03 4:02 ` Srinivas Pandruvada
2016-06-06 6:47 ` Srinivas Pandruvada
2016-06-09 21:45 ` Grant Likely
2016-06-09 21:54 ` Srinivas Pandruvada
2016-06-10 9:44 ` Grant Likely
2016-06-10 13:55 ` Srinivas Pandruvada
2016-06-10 14:26 ` Bastien Nocera
2016-06-10 14:45 ` Srinivas Pandruvada
2016-06-10 15:04 ` Bastien Nocera
2016-06-10 15:23 ` Srinivas Pandruvada
2016-06-10 15:27 ` Bastien Nocera
2016-06-14 13:44 ` Grant Likely
2016-06-14 15:12 ` Bastien Nocera
2016-06-14 16:08 ` Grant Likely
2016-06-14 17:01 ` Bastien Nocera
2016-06-14 21:33 ` Grant Likely
2016-06-10 14:02 ` Grant Likely
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=1464909180.2065.1.camel@ulg.ac.be \
--to=a.bhattacharya@ulg.ac.be \
--cc=linux-iio@vger.kernel.org \
--cc=srinivas.pandruvada@linux.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).