From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev problems
Date: Sun, 07 Mar 2004 14:28:26 +0000 [thread overview]
Message-ID: <1078669706.1170.37.camel@pim> (raw)
In-Reply-To: <200403071315.02925.michal@cihar.com>
On Sun, 2004-03-07 at 15:20, Michal Èihaø wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Sunday 07 of March 2004 15:05, Kay Sievers wrote:
> > Whats in dmesg? I have the following for my cheap 4slot-reader:
>
> [connect reader]
>
> USB Mass Storage device found at 21
> usb 1-2: USB disconnect, address 21
> usb 1-2: new full speed USB device using address 22
> scsi34 : SCSI emulation for USB Mass Storage devices
> Vendor: Apacer Model: Mega Steno Rev: 1.03
> Type: Direct-Access ANSI SCSI revision: 02
> Attached scsi removable disk sda at scsi34, channel 0, id 0, lun 0
> Vendor: Apacer Model: Mega Steno Rev: 1.03
> Type: Direct-Access ANSI SCSI revision: 02
> Attached scsi removable disk sdb at scsi34, channel 0, id 0, lun 1
> Vendor: Apacer Model: Mega Steno Rev: 1.03
> Type: Direct-Access ANSI SCSI revision: 02
> Attached scsi removable disk sdc at scsi34, channel 0, id 0, lun 2
> WARNING: USB Mass Storage data integrity not assured
>
> [now I read from /dev/sda]
>
> USB Mass Storage device found at 22
> SCSI device sda: 15680 512-byte hdwr sectors (8 MB)
> sda: assuming Write Enabled
> sda: assuming drive cache: write through
> SCSI device sda: 15680 512-byte hdwr sectors (8 MB)
> sda: assuming Write Enabled
> sda: assuming drive cache: write through
> sda: sda1
>
> > sdb: Spinning up disk....ready
>
> This doesn't happen to me. Related kernel code is in drivers/scsi/sd.c:
>
> /*
> * If manual intervention is required, or this is an
> * absent USB storage device, a spinup is meaningless.
> */
> if (SRpnt->sr_sense_buffer[2] = NOT_READY &&
> SRpnt->sr_sense_buffer[12] = 4 /* not ready */ &&
> SRpnt->sr_sense_buffer[13] = 3) {
> break; /* manual intervention required */
>
> /*
> * Issue command to spin up drive when not ready
> */
> } else if (SRpnt->sr_sense_buffer[2] = NOT_READY) {
> unsigned long time1;
> if (!spintime) {
> printk(KERN_NOTICE "%s: Spinning up disk...",
> diskname);
> }
>
Ah, nice to know.
You may access you device with your apacer.sh to revalidate. (?)
Just create a temporary node, access and remove it.
Kay
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&opÌk
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-03-07 14:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 12:15 udev problems Michal Čihař
2004-03-07 12:29 ` Kay Sievers
2004-03-07 12:47 ` Michal Čihař
2004-03-07 13:10 ` Michal Čihař
2004-03-07 13:44 ` Kay Sievers
2004-03-07 13:49 ` Michal Čihař
2004-03-07 14:05 ` Kay Sievers
2004-03-07 14:16 ` Kay Sievers
2004-03-07 14:20 ` Michal Čihař
2004-03-07 14:28 ` Kay Sievers [this message]
2004-03-07 14:30 ` Michal Čihař
2004-03-07 14:41 ` Kay Sievers
2004-03-07 14:43 ` Michal Čihař
2004-03-07 15:11 ` Michal Čihař
2004-03-07 15:28 ` Michal Čihař
2004-03-07 15:46 ` Michal Čihař
2005-04-18 18:13 ` clemens
2005-04-18 20:49 ` Greg KH
2005-04-18 21:02 ` David Zeuthen
2005-04-18 21:12 ` Greg KH
2005-04-18 21:27 ` clemens
2005-04-18 21:36 ` Kay Sievers
2005-04-19 7:36 ` clemens
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=1078669706.1170.37.camel@pim \
--to=kay.sievers@vrfy.org \
--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).