mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Thorpe <jonthorp@bigpond.net.au>
To: linux-kernel@vger.kernel.org
Subject: sd.c - "Spinning up disk..." on usb-storage flash reader
Date: Tue, 9 Mar 2004 11:36:51 +1100	[thread overview]
Message-ID: <20040309113651.129e284e.jonthorp@bigpond.net.au> (raw)

Greetings,

I recently upgraded to 2.6.3 from 2.4.25 and whilst most things work, there is a problem that I'm having with a Scanlogic/Cypress SL11R-IDE CompactFlash/SmartMedia reader.

When I run the reader with a CompactFlash card, the SCSI disk (sd.c) is attempting to "spin up" the SmartMedia socket, which does not contain media. If I were to insert a SmartMedia card, the problem goes away.

Below are some relevant logs from the kernel:

--
scsi14 : SCSI emulation for USB Mass Storage devices
  Vendor: ScanLogi  Model: SL11R-IDE         Rev: 0074
  Type:   Direct-Access                      ANSI SCSI revision: 02
sdc: Spinning up disk..........................................................................................
.............not responding...
sdc : READ CAPACITY failed.
sdc : status=1, message=00, host=0, driver=08 
Current sd: sense = 70  2
Raw sense data:0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x00 
sdc: assuming Write Enabled
sdc: assuming drive cache: write through
sdc: Spinning up disk..........................................................................................
.............not responding...
sdc : READ CAPACITY failed.
sdc : status=1, message=00, host=0, driver=08 
Current sd: sense = 70  2
Raw sense data:0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x00 
sdc: assuming Write Enabled
sdc: assuming drive cache: write through
sdc: Spinning up disk..........................................................................................
.............not responding...
sdc : READ CAPACITY failed.
sdc : status=1, message=00, host=0, driver=08 
Current sd: sense = 70  2
Raw sense data:0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x00 
sdc: assuming Write Enabled
sdc: assuming drive cache: write through
 sdc:<3>Buffer I/O error on device sdc, logical block 0
Buffer I/O error on device sdc, logical block 0
 unable to read partition table
 sdc:<3>Buffer I/O error on device sdc, logical block 0
 unable to read partition table
Attached scsi removable disk sdc at scsi14, channel 0, id 0, lun 0
  Vendor: ScanLogi  Model: SL11R-IDE         Rev: 0074
  Type:   Direct-Access                      ANSI SCSI revision: 02
sdd: Unit Not Ready, sense:
Current : sense = 70  0
Raw sense data:0x70 0x00 0x00 0x00 0x00 0x00 0x00 0x00 
SCSI device sdd: 500737 512-byte hdwr sectors (256 MB)
sdd: assuming Write Enabled
sdd: assuming drive cache: write through
SCSI error: host 14 id 0 lun 1 return code = 8000002
  Sense class 7, sense error 0, extended sense 0
SCSI device sdd: 500737 512-byte hdwr sectors (256 MB)
sdd: assuming Write Enabled
sdd: assuming drive cache: write through
SCSI device sdd: 500737 512-byte hdwr sectors (256 MB)
sdd: assuming Write Enabled
sdd: assuming drive cache: write through
--

I have two of these readers, one with slightly newer firmware which does not have this problem.

Are there any checks that I can incorporate into sd.c to see if the device is removable? The 2.4.2x kernel seemed a little more robust with checking whether or not the device was removable (i.e. USB flash memory readers), perhaps a little friendlier to firmware bugs.

Any assistance would be appreciated.

Please CC as I am not subscribed to the list: jthorpe at bigpond dot net dot au.

Thanks,
Jonathan

                 reply	other threads:[~2004-03-09  0:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20040309113651.129e284e.jonthorp@bigpond.net.au \
    --to=jonthorp@bigpond.net.au \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®