From: Jonathan Nieder <jrnieder@gmail.com>
To: Holger Hoffstaette <holger.hoffstaette@googlemail.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, sarah.a.sharp@linux.intel.com
Subject: [regression] external HDD in USB3 enclosure cannot be dynamically removed (Re: Linux 3.7.5)
Date: Mon, 28 Jan 2013 12:46:39 -0800 [thread overview]
Message-ID: <20130128204639.GB7759@google.com> (raw)
In-Reply-To: <pan.2013.01.28.20.33.44.918987@googlemail.com>
Hi Holger,
Holger Hoffstaette wrote:
>> On Mon, Jan 28, 2013 at 12:42:16PM +0100, Holger Hoffstaette wrote:
>>> Apologies for being late but I'm afraid I just found at least one
>>> regression in this release.
>>>
>>> I have an external HDD in an USB3 enclosure for the occasional backup. I
>>> turn it on, it gets registered as sdX, I mount it/use it/unmount it and
>>> turn it off, which worked fine with kernels including 3.7.4. With 3.7.5
>
> FWIW it didn't really work with 3.7.4 either - just didn't notice before.
>
>>> the kernel seems no longer notified of the changed device power status;
>>> nothing in dmesg and the device stays in the list of SCSI devices as
>>> e.g. shown by lsscsi. This is repeatable. Turning the device back
>>> on/using it works fine, it's just that I cannot dynamically remove it
>>> any longer.
[...]
> No, current 3.8-rc5 did not work either. I first found 3.7.2 OK and 3.7.3
> bad. Bisecting found:
>
> --snip--
> f7965c0846d74b270e246c1470ca955d5078eb07 is the first bad commit
> commit f7965c0846d74b270e246c1470ca955d5078eb07
> Author: Sarah Sharp <sarah.a.sharp@linux.intel.com>
> Date: Wed Nov 14 17:58:04 2012 -0800
>
> USB: Handle warm reset failure on empty port.
>
> commit 65bdac5effd15d6af619b3b7218627ef4d84ed6a upstream.
[...]
> Reverting this from 3.7.3 all the way to 3.8-rc5 makes USB 3.0
> disconnection/power-off device removal work again. Verified both on the
> bisection box and by now also the original machine.
Thanks for tracking this down. Forwarding to relevant people.
Hope that helps,
Jonathan
next prev parent reply other threads:[~2013-01-28 20:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 4:56 Linux 3.7.5 Greg KH
2013-01-28 4:57 ` Greg KH
[not found] ` <pan.2013.01.28.11.42.16.556318@googlemail.com>
2013-01-28 14:39 ` Greg KH
[not found] ` <pan.2013.01.28.20.33.44.918987@googlemail.com>
2013-01-28 20:46 ` Jonathan Nieder [this message]
2013-02-12 0:40 ` [regression] external HDD in USB3 enclosure cannot be dynamically removed (Re: Linux 3.7.5) Sarah Sharp
2013-02-12 0:54 ` Jonathan Nieder
2013-02-12 8:36 ` Holger Hoffstätte
2013-02-12 10:35 ` Holger Hoffstätte
2013-02-12 20:42 ` Sarah Sharp
2013-02-13 8:28 ` Holger Hoffstätte
2013-02-13 17:16 ` Matthias Schniedermeyer
2013-02-13 19:33 ` Sarah Sharp
2013-02-13 20:04 ` Matthias Schniedermeyer
2013-02-13 21:08 ` Sarah Sharp
2013-02-13 21:31 ` Greg KH
2013-02-13 22:12 ` Sarah Sharp
2013-03-01 16:48 ` Greg KH
2013-03-05 22:10 ` Stable backport request, Was: " Sarah Sharp
2013-03-06 2:11 ` Greg KH
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=20130128204639.GB7759@google.com \
--to=jrnieder@gmail.com \
--cc=holger.hoffstaette@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sarah.a.sharp@linux.intel.com \
--cc=stable@vger.kernel.org \
/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).