linux-kernel - Re: [PATCH] Revert "xhci: Limit USB2 port wake support for AMD Promontory hosts"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 18 Sep 2017 11:06:29 +0300
From:   Mathias Nyman <mathias.nyman@...el.com>
To:     Kai-Heng Feng <kai.heng.feng@...onical.com>,
        Mathias Nyman <mathias.nyman@...ux.intel.com>
Cc:     Greg KH <gregkh@...uxfoundation.org>, Lars_Chang@...edia.com.tw,
        USB list <linux-usb@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        "Tsai, Nicholas" <nicholas.tsai@....com>,
        Nehal Shah <Nehal-bakulchandra.Shah@....com>,
        Ramkumar Subramaniyan <ramkumar.ks@....com>
Subject: Re: [PATCH] Revert "xhci: Limit USB2 port wake support for AMD
 Promontory hosts"

On 16.09.2017 07:49, Kai-Heng Feng wrote:
> On Mon, Aug 28, 2017 at 9:56 PM, Kai-Heng Feng
> <kai.heng.feng@...onical.com> wrote:
>> On Mon, Aug 28, 2017 at 6:14 PM, Mathias Nyman
>> <mathias.nyman@...ux.intel.com> wrote:
>>> On 28.08.2017 12:29, Greg KH wrote:
>>>
>>> Adding more people who were involved in the original patch.
>>>
>>> Users are now seeing the unresponsive USB2 ports with Promontory hosts.
>>> Is there any update on a better way to solve the original issue.
>>>
>>> To me a "dead" USB2 port seems like a much worse issue for a user
>>> than a BIOS disabled port waking up on plug/unplug (wake on
>>> connect/disconnect),
>>> so I'm myself in favor of doing this revert.
>>
>> At least I can't find "Disable USB2" on my ASUS PRIME B350M-A, so the
>> new behavior is quite surprising.
>>
>>>
>>> But there was a strong push from Promontory developers to get the original
>>> fix in,
>>> and I would like to get some comment from them before I do anything about
>>> it.
>>
>> You looped them to the mail thread which I reported the regression two
>> weeks ago, and there is no response since then...
>
> Still no response from AMD and ASMedia guys.
>
> I don't like to use out-of-tree patches for myself, but probably it's
> the only way here?

I'll revert it and send it forward now since rc1 is out

-Mathias