Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753253AbdDJSiI (ORCPT ); Mon, 10 Apr 2017 14:38:08 -0400 Received: from mail-pf0-f196.google.com ([209.85.192.196]:36257 "EHLO mail-pf0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751949AbdDJSiG (ORCPT ); Mon, 10 Apr 2017 14:38:06 -0400 Date: Mon, 10 Apr 2017 11:38:02 -0700 From: Dmitry Torokhov To: Jiri Kosina Cc: Gabriele Mazzotta , aduggan@synaptics.com, benjamin.tissoires@redhat.com, "linux-kernel@vger.kernel.org" , linux-input@vger.kernel.org, Peter Hutterer , Cameron Gutman , Thorsten Leemhuis , Nick Dyer , Christopher Heiny Subject: Re: Crash caused by hid-rmi and no longer working touchscreen Message-ID: <20170410183802.GA39262@dtor-ws> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1339 Lines: 40 On Mon, Apr 10, 2017 at 03:18:03PM +0200, Jiri Kosina wrote: > > [ 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. Yes, we also have this: https://bugzilla.kernel.org/show_bug.cgi?id=195287 so reverting seems prudent at this time. Thanks. -- Dmitry