1. 01 9月, 2006 3 次提交
  2. 27 8月, 2006 1 次提交
    • A
      [PATCH] unusual_devs update for UCR-61S2B · 94918ff6
      Alan Stern 提交于
      The existing unusual_devs entry for the UCR-61S2B appears to have too
      wide a revision range.  It matches at least one device that doesn't
      respond to the initialization sequence.  Perhaps the sequence needs to
      be updated, or perhaps something else can be done.  For now, this patch
      (as764) restricts the range to include only the revision mentioned in
      the original comment.
      
      This resolves (for now!) Bugzilla entry #6950.
      Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      94918ff6
  3. 12 8月, 2006 1 次提交
  4. 03 8月, 2006 3 次提交
  5. 13 7月, 2006 7 次提交
  6. 01 7月, 2006 1 次提交
  7. 22 6月, 2006 4 次提交
  8. 28 4月, 2006 2 次提交
  9. 21 3月, 2006 4 次提交
  10. 01 3月, 2006 1 次提交
  11. 14 2月, 2006 5 次提交
  12. 01 2月, 2006 2 次提交
  13. 05 1月, 2006 5 次提交
  14. 24 11月, 2005 1 次提交
    • D
      [PATCH] USB: fix USB key generates ioctl_internal_command errors issue · 63dc3ff3
      David Hrdeman 提交于
      On Wed, Nov 16, 2005 at 06:34:24PM -0800, Pete Zaitcev wrote:
      >On Wed, 16 Nov 2005 23:52:32 +0100, David Hrdeman <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.
      Signed-off-by: NDavid Hrdeman <david@2gen.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      63dc3ff3