From: Mark Lord <lkml@rtr.ca>
To: linux-kernel@vger.kernel.org, gregkh@suse.de, linux-usb@vger.kernel.org
Subject: Re: Enable CONFIG_USB_SUSPEND by default or some mobile HD can't be unplugged safely
Date: Fri, 02 Jan 2009 10:51:05 -0500 [thread overview]
Message-ID: <495E37E9.80903@rtr.ca> (raw)
In-Reply-To: <495E37BC.1040101@rtr.ca>
Mark Lord wrote:
> Tino Keitel wrote:
>> On Fri, Jan 02, 2009 at 00:03:43 +0800, Yan Li wrote:
>>> Hello List,
>>>
>>> By default CONFIG_USB_SUSPEND is not enabled and today I got bite by
>>> this when I got a new WDC My Book hard drive. I have no way to unplug
>>> it safely, according to it's manual, with a kernel that doesn't have
>>> CONFIG_USB_SUSPEND=y.
>>>
>>> On it's manual read "you should unplug and remove the device only when
>>> the light is off." On Linux unmounting it won't turn it's light off
>>> and I can feel it's motor is still running. The only way to unplug it
>>> properly on a Linux system, as to my knowledge, is to echo `suspend'
>>> to `/sys/bus/usb/devices/$DEV/power/level'. And one has to have
>>> CONFIG_USB_SUSPEND=y to do this.
>>
>> With a WD My Passport drive (2,5"), I need to use sg_start --stop --pc=3
>> to stop the disk before unplugging it. Maybe this works with your
>> drive, too. This is also required by some Firewire hard disks. Maybe
>> the eject command should be extended to use this method, as it is used
>> also by HAL to eject hotplug devices.
> ..
>
> Incidently, the WD Passport drives support SG_IO,
> so things like hdparm and smartctl can work with them as well.
..
s/SG_IO/SG_IO+SAT/
next prev parent reply other threads:[~2009-01-02 15:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-01 16:03 Enable CONFIG_USB_SUSPEND by default or some mobile HD can't be unplugged safely Yan Li
2009-01-01 16:07 ` [PATCH] enable CONFIG_USB_SUSPEND by default Yan Li
2009-01-01 17:29 ` Enable CONFIG_USB_SUSPEND by default or some mobile HD can't be unplugged safely Alan Stern
2009-01-02 13:23 ` Yan Li
2009-01-01 17:32 ` Alexander E. Patrakov
2009-01-01 17:45 ` Alan Stern
2009-01-02 13:37 ` Yan Li
2009-01-02 13:46 ` Alexander E. Patrakov
2009-01-01 19:09 ` Robert Hancock
2009-01-02 9:56 ` Tino Keitel
2009-01-02 14:00 ` Yan Li
2009-01-02 14:08 ` Tino Keitel
2009-01-02 14:28 ` Yan Li
2009-01-02 16:04 ` Alan Stern
2009-01-03 2:33 ` Yan Li
2009-01-02 15:50 ` Mark Lord
2009-01-02 15:51 ` Mark Lord [this message]
2009-01-02 18:15 ` Tino Keitel
2009-01-03 2:24 ` Yan Li
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=495E37E9.80903@rtr.ca \
--to=lkml@rtr.ca \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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).