USB key generates ioctl_internal_command errors

USB key generates ioctl_internal_command errors

[David Härdeman]

Whenever I insert my Iomega Mini 1Gb USB key, I get a stream of 
ioctl_internal_command errors. The device works just fine (mounting, 
copying files, unmounting, etc), but the messages are annoying...

usb 1-4: new high speed USB device using ehci_hcd and address 4
scsi8 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
austin:/home/david# dmesg 
usb 1-4: new high speed USB device using ehci_hcd and address 4
scsi8 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
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)
sda: Write Protect is off
sda: Mode Sense: 00 00 00 00
sda: assuming drive cache: write through
 sda: sda1
Attached scsi removable disk sda at scsi8, channel 0, id 0, lun 0
usb-storage: device scan complete
ioctl_internal_command: <8 0 0 0> return code = 8000002
   : Current: sense key=0x0
    ASC=0x0 ASCQ=0x0
ioctl_internal_command: <8 0 0 0> return code = 8000002
   : Current: sense key=0x0
    ASC=0x0 ASCQ=0x0
ioctl_internal_command: <8 0 0 0> return code = 8000002
   : Current: sense key=0x0
    ASC=0x0 ASCQ=0x0
ioctl_internal_command: <8 0 0 0> return code = 8000002
   : Current: sense key=0x0
    ASC=0x0 ASCQ=0x0
ioctl_internal_command: <8 0 0 0> return code = 8000002
   : Current: sense key=0x0
    ASC=0x0 ASCQ=0x0
[...]

And this goes on and on...approx one message per second if hal is 
running, otherwise only the first two ioctl_internal_command messages 
are shown. I assume that hal is doing some kind of polling on the device 
which triggers the error message. What does the error mean and how do I 
fix it? I've seen some other posts on the list with similar error 
messages but found no answers...

//David

PS
Please CC me on any replies

Re: USB key generates ioctl_internal_command errors

[Pete Zaitcev]

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

Re: USB key generates ioctl_internal_command errors

[David Härdeman]

[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]

On Wed, Nov 16, 2005 at 06:34:24PM -0800, Pete Zaitcev wrote:
>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:

Thanks for the pointer, and yes, it is harmless, but it floods the 
console with the messages which hides other (potentially important) 
messages...following your example I've made a patch which fixes the 
problem. It's trivial so I hope It'll find it's way into the kernel 
soon.

Re,
David Härdeman

Signed-off-by: David Härdeman <david@2gen.com>


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: usb-iomega-umini-is-unusual.patch --]
[-- Type: text/plain; charset=utf-8, Size: 623 bytes --]

--- linux-2.6.14.2/drivers/usb/storage/unusual_devs.h.orig	2005-11-11 06:33:12.000000000 +0100
+++ linux-2.6.14.2/drivers/usb/storage/unusual_devs.h	2005-11-17 22:10:47.000000000 +0100
@@ -1086,6 +1086,15 @@
 		US_SC_DEVICE, US_PR_DEVICE, NULL,
 		US_FL_GO_SLOW ),
 
+/*
+ * David Härdeman <david@2gen.com>
+ * The key makes the SCSI stack print confusing (but harmless) messages
+ */
+UNUSUAL_DEV(  0x4146, 0xba01, 0x0100, 0x0100,
+		"Iomega",
+		"Micro Mini 1GB",
+		US_SC_DEVICE, US_PR_DEVICE, NULL, US_FL_NOT_LOCKABLE ),
+
 #ifdef CONFIG_USB_STORAGE_SDDR55
 UNUSUAL_DEV(  0x55aa, 0xa103, 0x0000, 0x9999, 
 		"Sandisk",