AFT PRO-57U memory card reader not working after kernel update

I recently installed a kernel security update for Debian Linux and then rebooted. On reboot the system took about an extra 20 seconds or so to reboot compared to before (previously it took close to 10 seconds to get from the GRUB menu to the login prompt).

After the update, if I stay in the console the following messages appear on the screen every so often.

[  128.760094] usb 5-2: device not accepting address 4, error -71
[  128.816253] sd 12:0:0:0: rejecting I/O to offline device
[  128.816524] sd 12:0:0:3: [sdf] Asking for cache data failed
[  128.816534] sd 12:0:0:3: [sdf] Assuming drive cache: write through
[  128.816593] sd 12:0:0:0: [sdc] Asking for cache data failed
[  128.816597] sd 12:0:0:0: [sdc] Assuming drive cache: write through
[  128.816821] sd 12:0:0:4: [sdg] Asking for cache data failed
[  128.816887] sd 12:0:0:4: [sdg] Assuming drive cache: write through
[  128.817451] sd 12:0:0:3: [sdf] Asking for cache data failed
[  128.817512] sd 12:0:0:3: [sdf] Assuming drive cache: write through
[  128.817534] sd 12:0:0:0: [sdc] Asking for cache data failed
[  128.817538] sd 12:0:0:0: [sdc] Assuming drive cache: write through
[  128.824233] sd 12:0:0:2: [sde] Asking for cache data failed
[  128.825383] sd 12:0:0:2: [sde] Assuming drive cache: write through
[  128.826883] sd 12:0:0:2: [sde] Asking for cache data failed
[  128.828023] sd 12:0:0:2: [sde] Assuming drive cache: write through
[  128.828192] sd 12:0:0:1: [sdd] Asking for cache data failed
[  128.828198] sd 12:0:0:1: [sdd] Assuming drive cache: write through
[  128.828566] sd 12:0:0:1: [sdd] Asking for cache data failed
[  128.828571] sd 12:0:0:1: [sdd] Assuming drive cache: write through

Looking through the various logs I found that USB 5-2 is being used by my AFT PRO-57U memory card reader. When working properly the various memory cards can be read on scsi devices sdc through sdf. I disconnected the internal USB cable from the back of the card reader and rebooted. This caused the boot delay and error messages to go away.

To try to determine whether the problem was due to a sudden hardware failure of the card reader (the card reader has worked properly since I installed it at least 6 months ago) or due to the kernel upgrade, I reconnected the card reader and rebooted to an older kernel installed on a second hard drive. The problems did not occur with the older kernel and the card reader was able to read an SD card properly. This makes me believe the problem is due to the kernel upgrade.

Any suggestions on how to get the card reader working again with the upgraded kernel?

I am running Debian Wheezy. After the security update the kernel is Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.60-1+deb7u1.

The output of lsusb is:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 011 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 007 Device 003: ID 0557:2213 ATEN International Co., Ltd CS682 2-Port USB 2.0 DVI KVM Switch
Bus 005 Device 006: ID 11b0:6558 ATECH FLASH TECHNOLOGY

The relevant output of lsusb -v is:

idVendor           0x11b0 ATECH FLASH TECHNOLOGY
  idProduct          0x6558 
  bcdDevice            5.64
  iManufacturer           3 
  iProduct                4 
  iSerial                 5 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           44
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              224mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               0
        bMaxBurst               4
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               0
        bMaxBurst               4

On the debian bug tracker, someone reported a similar error of usb devices not accepting address during installation here:

https://lists.debian.org/debian-boot.../msg00259.html

In the above post, the problem went away when IOMMU was enabled in the bios setup. It usually comes disabled by default. I saw other reports of erratic behavior on motherboards that have support for IOMMU when IOMMU was not enabled. If your motherboard has an option to enable/disabel IOMMU, you might try enabling IOMMU.