Bug 2597 - USB MemoryStick reader needs manual driver reload or device access to list partitions
Summary: USB MemoryStick reader needs manual driver reload or device access to list pa...
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: Drivers
Classification: Unclassified
Component: USB (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Greg Kroah-Hartman
URL:
Keywords:
Depends on:
Blocks: USB
  Show dependency tree
 
Reported: 2004-04-26 12:27 UTC by Christoph Budziszewski
Modified: 2006-07-10 13:20 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.2
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Christoph Budziszewski 2004-04-26 12:27:37 UTC
Distribution: gentoo
Hardware Environment: Sony Laptop with internal SonyMemoryStick-Slot
Software Environment: all usb and scsi are modules
lsusb
Bus 003 Device 002: ID 054c:0069 Sony Corp. Memorystick MSC-U03 Reader
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

lsusb -v
Bus 003 Device 002: ID 054c:0069 Sony Corp. Memorystick MSC-U03 Reader
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 Interface
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        16
  idVendor           0x054c Sony Corp.
  idProduct          0x0069 Memorystick MSC-U03 Reader
  bcdDevice            1.09
  iManufacturer           1 Sony
  iProduct                2 USB Memory Stick Slot
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xc0
      Self Powered
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      5 SFF-8070i
      bInterfaceProtocol      0
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               none
        wMaxPacketSize         64
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               none
        wMaxPacketSize         64
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               none
        wMaxPacketSize          2
        bInterval               1
  Language IDs: (length=4)
     0409 English(US)


Problem Description:

The MemoryStick is not recognised when inseted.
After boot, (w/o Memorystick in the Slot) I have only the /dev/sda Device.
(Booting with Stick in the Slot I also have the /dev/sda1 )
When I insert the Stick in the slot nothing happens. I still don't have the
/dev/sda1, as expected. 
I tried to unload and reload the sd_mod , and /dev/sda1 appears.
also a 'touch /dev/sda' reveals the /dev/sda1 
Same thing happens when ejecting the Stick: the /dev/sda1 stays availeble (but
empty) , but 'touch /dev/sda' removes the /dev/sda1 .
/dev/sda seems to be always there.



Steps to reproduce:
1. reboot (w/ or w/o stick)
2. test if /desv/sda1 exists
3. reload the modules or accessing the device corrects the status.
Comment 1 Adrian Bunk 2006-03-17 04:34:00 UTC
Is this issue still present in recent 2.6 kernels?
Comment 2 Adrian Bunk 2006-07-10 13:20:27 UTC
Please reopen this bug if it's still present in kernel 2.6.17.

Note You need to log in before you can comment on or make changes to this bug.