mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@kernel.org>
To: Gabriele Mazzotta <gabriele.mzt@gmail.com>
Cc: aduggan@synaptics.com, benjamin.tissoires@redhat.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-input@vger.kernel.org,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Peter Hutterer <peter.hutterer@who-t.net>,
	Cameron Gutman <aicommander@gmail.com>,
	Thorsten Leemhuis <linux@leemhuis.info>,
	Nick Dyer <nick@shmanahar.org>,
	Christopher Heiny <cheiny@synaptics.com>
Subject: Re: Crash caused by hid-rmi and no longer working touchscreen
Date: Mon, 10 Apr 2017 15:18:03 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LSU.2.20.1704101515380.28004@cbobk.fhfr.pm> (raw)
In-Reply-To: <b79b88c8-770a-13f6-5668-c3a94254e5e0@gmail.com>


[ a couple more people from "the other regression thread" added to CC ]

On Mon, 10 Apr 2017, Gabriele Mazzotta wrote:

> Hi,
> 
> I'm having troubles with hid-rmi using 4.11-rc6. I'm getting some
> "rmi_hid_read_block: timeout elapsed" errors and ultimately the
> crash you can see at the end of this mail. I will reply to this
> mail with a full log that shows all the errors.
> 
> The problem seems to be caused by commit 279967a65b320d174a507498ae
> ("HID: rmi: Handle all Synaptics touchpads using hid-rmi").
> 
> My laptop has a Synaptics touchpad and a Synaptics touchscreen.
> Because of that commit, hid-rmi is used for both the devices, while
> it has always been used only for the touchpad. Needless to say that
> the touchscreen no longer works.
> 
> If I revert that commit, everything goes back to normal.

Alright, given this is a second regression cause by this switch, I suggest 
to revert this one for 4.11 still, and work on fixing this properly for 
4.12.

If noone raises any objections (a few more people added to Cc), I'll queue 
a 4.11-rc revert tomorrow.

-- 
Jiri Kosina
SUSE Labs

  parent reply	other threads:[~2017-04-10 13:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-10 13:14 Gabriele Mazzotta
2017-04-10 13:15 ` Gabriele Mazzotta
2017-04-10 13:18 ` Jiri Kosina [this message]
2017-04-10 18:38   ` Dmitry Torokhov
2017-04-10 19:41     ` Andrew Duggan

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.LSU.2.20.1704101515380.28004@cbobk.fhfr.pm \
    --to=jikos@kernel.org \
    --cc=aduggan@synaptics.com \
    --cc=aicommander@gmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=cheiny@synaptics.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=gabriele.mzt@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=nick@shmanahar.org \
    --cc=peter.hutterer@who-t.net \
    /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®