From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752682AbdECO6z (ORCPT ); Wed, 3 May 2017 10:58:55 -0400 Received: from mx2.suse.de ([195.135.220.15]:58933 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751275AbdECO6s (ORCPT ); Wed, 3 May 2017 10:58:48 -0400 Date: Wed, 3 May 2017 16:58:42 +0200 From: Joerg Roedel To: Alex Henrie Cc: Greg KH , Mathias Nyman , linux-usb@vger.kernel.org, LKML Subject: Re: I'd like to donate a MacBook Pro Message-ID: <20170503145842.GE5077@suse.de> References: <20170501100645.GA32063@kroah.com> <20170503115804.GA20910@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 03, 2017 at 08:35:47AM -0600, Alex Henrie wrote: > 2017-05-03 5:58 GMT-06:00 Greg KH : > > On Tue, May 02, 2017 at 10:55:09PM -0600, Alex Henrie wrote: > >> Today I ran a regression test to determine which commit made the > >> keyboard stop working entirely. The last commit that worked for me was > >> c09e22d5370739e16463c113525df51b5980b1d5. After that, there is a long > >> series of commits where the screen stays black, and after that, I > >> start getting errors like the one above. > > > > So git bisect said that commit was a good change, what one was the "bad" > > commit that git bisect pointed at? > > The commit right after that, but it's not clear whether the screen > blanking problem was part of the same bug or just another bug that was > introduced at about the same time. That would be 39ab9555c24110671f8dc671311a26e5c985b592: iommu: Add sysfs bindings for struct iommu_device And it introduced a regression when iommu-sysfs entries are accessed. This is fixed in a7fdb6e648fb. Does that commit fix the screen blanking problem? Joerg