From: Matthew Dharm <mdharm-usb@one-eyed-alien.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: do not disconnect
Date: Thu, 21 Oct 2004 08:05:59 +0000 [thread overview]
Message-ID: <20041021080559.GA2357@one-eyed-alien.net> (raw)
In-Reply-To: <1097995104.3180.18.camel@rivendell.home.local>
[-- Attachment #1: Type: text/plain, Size: 2320 bytes --]
On Thu, Oct 21, 2004 at 12:13:57AM -0700, Florin Andrei wrote:
> On Sun, 2004-10-17 at 04:06, Kay Sievers wrote:
> > On Sat, Oct 16, 2004 at 11:38:24PM -0700, Florin Andrei wrote:
> > > I keep my iPod hooked up to the computer via a 1394 cable, in order to
> > > recharge the battery. Once i hook it up, the iPod displays the "Do Not
> > > Disconnect" message.
> > > However, the iPod is not mounted. So, how can i put it in the correct
> > > state to disconnect it? If it was mounted, i think i could simply umount
> > > it.
> > >
> > > It looks like it gets attached to the SCSI subsystem somehow:
> > >
> > > So, how can i kick it out? Is there a way to tell the 1394 bus to detach
> > > this node, or?...
> >
> > You may try "eject".
>
> eject -s /dev/sda indeed turns the iPod into the "OK to disconnect"
> state, but the command itself hangs and does not respond to CTRL-C. I
> had to kill the xterm in order to kill eject.
>
> I'm open to suggestions.
>
> Some dmesg output:
>
> sda: Spinning up
> disk................................................................................not responding...
> sda : READ CAPACITY failed.
> sda : status=1, message=00, host=0, driver=08
> Current sd: sense key Not Ready
> Additional sense: Logical unit not ready, cause not reportable
> sda: test WP failed, assume Write Enabled
> sda: asking for cache data failed
> sda: assuming drive cache: write through
> sda:<3>Buffer I/O error on device sda, logical block 0
> Buffer I/O error on device sda, logical block 0
> Buffer I/O error on device sda, logical block 3662189
> Buffer I/O error on device sda, logical block 3662189
> Buffer I/O error on device sda, logical block 0
> unable to read partition table
These messages happened _after_ you used the eject command?
This looks like SCSI is trying to revalidate the device immediately. It
shouldn't do that -- it should only revalidate on the next open. Or, at
least, that's what I think it used to do....
Matt
--
Matthew Dharm Home: mdharm-usb@one-eyed-alien.net
Maintainer, Linux USB Mass Storage Driver
E: You run this ship with Windows?! YOU IDIOT!
L: Give me a break, it came bundled with the computer!
-- ESR and Lan Solaris
User Friendly, 12/8/1998
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-21 8:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-17 6:38 do not disconnect Florin Andrei
2004-10-17 11:06 ` Kay Sievers
2004-10-21 7:13 ` Florin Andrei
2004-10-21 8:05 ` Matthew Dharm [this message]
2004-10-21 13:09 ` Kay Sievers
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=20041021080559.GA2357@one-eyed-alien.net \
--to=mdharm-usb@one-eyed-alien.net \
--cc=linux-hotplug@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).