From: "David Härdeman" <david@2gen.com>
To: linux-kernel@vger.kernel.org
Subject: USB key generates ioctl_internal_command errors
Date: Wed, 16 Nov 2005 23:52:32 +0100 [thread overview]
Message-ID: <20051116225231.GA28302@hardeman.nu> (raw)
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
next reply other threads:[~2005-11-16 22:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 22:52 David Härdeman [this message]
[not found] <mailman.1132184643.7273.linux-kernel2news@redhat.com>
2005-11-17 2:34 ` USB key generates ioctl_internal_command errors Pete Zaitcev
2005-11-17 21:28 ` David Härdeman
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=20051116225231.GA28302@hardeman.nu \
--to=david@2gen.com \
--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