[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1606221229130.1818-100000@iolanthe.rowland.org>
Date: Wed, 22 Jun 2016 12:30:00 -0400 (EDT)
From: Alan Stern <stern@...land.harvard.edu>
To: Joseph Salisbury <joseph.salisbury@...onical.com>
cc: rtatiya@...eaurora.org, Greg KH <gregkh@...uxfoundation.org>,
Robert Ancell <robert.ancell@...onical.com>,
"mathias.nyman@...ux.intel.com" <mathias.nyman@...ux.intel.com>,
<chasemetzger15@...il.com>, <baolu.lu@...ux.intel.com>,
<oneukum@...e.com>, <kborer@...il.com>, <jun.li@...escale.com>,
USB list <linux-usb@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [v4.2-rc1 Regression] usb: Enable LPM for USB 2.01+ full-speed
devices
On Wed, 22 Jun 2016, Joseph Salisbury wrote:
> Hi Rupesh,
>
> A kernel bug report was opened against Ubuntu [0]. After a kernel
> bisect, it was found that reverting the following commit resolved this bug:
>
> commit a8425292816ceaa8c49e29d2114e85d85a73e080
> Author: Rupesh Tatiya <rtatiya@...eaurora.org>
> Date: Tue Apr 14 16:36:55 2015 +0530
>
> usb: Enable LPM for USB 2.01+ full-speed devices
>
>
> The regression was introduced as of v4.2-rc1.
>
> I was hoping to get your feedback, since you are the patch author. Do
> you think gathering any additional data will help diagnose this issue,
> or would it be best to submit a revert request?
Another option is to add a NO_LPM quirks entry for the troublesome
device.
Alan Stern
Powered by blists - more mailing lists