linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Paul Zimmerman <pauldzim@gmail.com>
Cc: David Heinzelmann <heinzelmann.david@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	<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: Mon, 20 Jan 2020 10:23:11 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44L0.2001201016300.16814-100000@netrider.rowland.org> (raw)
In-Reply-To: <20200119211145.7dcc86ec@EliteBook>

On Sun, 19 Jan 2020, Paul Zimmerman wrote:

> I reported this regression last week (see
> https://lore.kernel.org/linux-usb/20200115153714.03d5b3aa@EliteBook/T/#u)
> but I got no response to my email. Today I have retested with 5.5-rc7
> and verified that the problem still exists. So I am resending with a
> different subject line to see if anyone responds.
> 
> The $subject patch causes a regression on my HP EliteBook laptop with a
> built-in USB bluetooth adapter. About 50% of the time, a suspend/resume
> cycle will cause the bluetooth adapter to stop working.
> 
> The dmesg log below shows two suspend/resume cycles. At time 63.928 you can
> see the bluetooth adapter being successfully resumed, and at time 140.969
> you can see it fail. After reverting the patch, the bluetooth adapter
> resumes 100% of the time.
> 
> I also included below a lsusb -v of the bluetooth adapter. Is there any
> other debugging info you'd like me to send?

It looks like your dmesg log was made without enabling debugging 
messages in usbcore.  Can you collect another log with debugging 
messages turned on?

	echo 'module usbcore =p' >/sys/kernel/debug/dynamic_debug/control

Also, it might not hurt to collect and post a usbmon trace for a bad
suspend-resume cycle.

Alan Stern


  reply	other threads:[~2020-01-20 15:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2020-01-20 20:52     ` Paul Zimmerman
2020-01-22  2:31 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
2020-01-31 15:37         ` Alan Stern

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=Pine.LNX.4.44L0.2001201016300.16814-100000@netrider.rowland.org \
    --to=stern@rowland.harvard.edu \
    --cc=gregkh@linuxfoundation.org \
    --cc=heinzelmann.david@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=pauldzim@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).