From: Paul Zimmerman <pauldzim@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: David Heinzelmann <heinzelmann.david@gmail.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [REGRESSION][BISECTED] 5.5-rc suspend/resume failure caused by patch a4f55d8b8c14 ("usb: hub: Check device descriptor before resusciation")
Date: Thu, 30 Jan 2020 14:16:57 -0700 [thread overview]
Message-ID: <482da576-e945-b804-3d36-65aee142e645@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.2001231035250.1518-100000@iolanthe.rowland.org>
Hi Alan,
On 1/23/20 8:50 AM, Alan Stern wrote:
> On Wed, 22 Jan 2020, Paul Zimmerman wrote:
>
>>> Still, since there was no real connection change at the port, there's
>>> no reason to call hub_port_connect_change() here. Let's see if the
>>> patch below fixes your problem.
>>>
>>> Alan Stern
>>>
>>>
>>>
>>> Index: usb-devel/drivers/usb/core/hub.c
>>> ===================================================================
>>> --- usb-devel.orig/drivers/usb/core/hub.c
>>> +++ usb-devel/drivers/usb/core/hub.c
>>> @@ -1216,11 +1216,6 @@ static void hub_activate(struct usb_hub
>>> #ifdef CONFIG_PM
>>> udev->reset_resume = 1;
>>> #endif
>>> - /* Don't set the change_bits when the device
>>> - * was powered off.
>>> - */
>>> - if (test_bit(port1, hub->power_bits))
>>> - set_bit(port1, hub->change_bits);
>>>
>>> } else {
>>> /* The power session is gone; tell hub_wq */
>>>
>>
>> I can confirm this fixes the issue for me, I did a couple dozen
>> suspend/resume cycles without seeing a failure.
>>
>> I see the code you removed was added by Lan Tianyu in commit
>> ad493e5e5805 ("usb: add usb port auto power off mechanism"). I
>
> No, not really. The set_bit() call was added by me in a much earlier
> commit (8808f00c7adf, merged in 2008). Lan Tianyu merely added the
> "if" test, so that set_bit() doesn't always get called. Now with this
> change, set_bit() never gets called.
>
>> wonder if your patch would break that? I don't know what that is
>> or how to test it.
>
> While some code review by people who are familiar with this material
> wouldn't hurt, I don't think you need to worry about any additional
> testing.
>
>> In any case:
>> Tested-by: Paul Zimmerman <pauldzim@gmail.com>
>
> Thank you. I'll submit the patch soon.
>
> Alan Stern
Ping? Unfortunately 5.5 was released with this regression, do you plan
to submit this patch soon?
--
Paul
next prev parent reply other threads:[~2020-01-30 21:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 2:31 [REGRESSION][BISECTED] 5.5-rc suspend/resume failure caused by patch a4f55d8b8c14 ("usb: hub: Check device descriptor before resusciation") Paul Zimmerman
2020-01-22 19:31 ` Alan Stern
2020-01-22 23:54 ` Paul Zimmerman
2020-01-23 15:50 ` Alan Stern
2020-01-30 21:16 ` Paul Zimmerman [this message]
2020-01-31 15:37 ` Alan Stern
-- strict thread matches above, loose matches on Subject: below --
2020-01-15 22:37 Regression caused by patch a4f55d8b8c14 "usb: hub: Check device descriptor before resusciation" Paul Zimmerman
2020-01-20 4:11 ` [REGRESSION][BISECTED] 5.5-rc suspend/resume failure caused by patch a4f55d8b8c14 ("usb: hub: Check device descriptor before resusciation") Paul Zimmerman
2020-01-20 15:23 ` Alan Stern
2020-01-20 20:52 ` Paul Zimmerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=482da576-e945-b804-3d36-65aee142e645@gmail.com \
--to=pauldzim@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heinzelmann.david@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox