lkml.org 
[lkml]   [2005]   [Nov]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: USB key generates ioctl_internal_command errors
On Wed, 16 Nov 2005 23:52:32 +0100, David Härdeman <david@2gen.com> wrote:

> usb-storage: waiting for device to settle before scanning
> Vendor: I0MEGA Model: UMni1GB*IOM2K4 Rev: 1.01
> Type: Direct-Access ANSI SCSI revision: 02
> SCSI device sda: 2048000 512-byte hdwr sectors (1049 MB)
> sda: Write Protect is off
> sda: Mode Sense: 00 00 00 00
> sda: assuming drive cache: write through
> ioctl_internal_command: <8 0 0 0> return code = 8000002
> : Current: sense key=0x0
> ASC=0x0 ASCQ=0x0
> SCSI device sda: 2048000 512-byte hdwr sectors (1049 MB)

I think it's harmless. I saw things like that, and initially I plugged
them with workarounds like this:

/*
* Pete Zaitcev <zaitcev@yahoo.com>, from Patrick C. F. Ernzer, bz#162559.
* The key does not actually break, but it returns zero sense which
* makes our SCSI stack to print confusing messages.
*/
UNUSUAL_DEV( 0x0457, 0x0150, 0x0100, 0x0100,
"USBest Technology", /* sold by Transcend */
"USB Mass Storage Device",
US_SC_DEVICE, US_PR_DEVICE, NULL, US_FL_NOT_LOCKABLE ),
But perhaps we want the SCSI stack to do something about it, dunno.

If you're nervous about messages, use ub, it's mostly silent :-)

-- Pete
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-11-17 03:37    [from the cache]
©2003-2011 Jasper Spaans. Advertise on this site