On Wed, May 03, 2017 at 08:35:47AM -0600, Alex Henrie wrote: > 2017-05-03 5:58 GMT-06:00 Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>: > > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
