USB-device triggers endless device checking [SOLVED]

hermanr · 2011-05-25 11:40:15

After installing Arch Linux on my computer (Intel P67 chipset), an endless loop of warning/error messages about a USB-device fills up my messages.log (and slows down my computer a little bit).

Three sample iterations (but it loops through all device numbers constantly):

May 25 12:18:06 localhost kernel: [ 5327.110029] usb 3-1.3: new full speed USB device using ehci_hcd and address 6
May 25 12:18:06 localhost mtp-probe: checking bus 3, device 6: "/sys/devices/pci0000:00/0000:00:1d.0/usb3/3-1/3-1.3"
May 25 12:18:06 localhost mtp-probe: bus: 3, device: 6 was not an MTP device
May 25 12:18:06 localhost mtp-probe: checking bus 3, device 6: "/sys/devices/pci0000:00/0000:00:1d.0/usb3/3-1/3-1.3"
May 25 12:18:06 localhost mtp-probe: bus: 3, device: 6 was not an MTP device
May 25 12:18:06 localhost kernel: [ 5327.436153] usb 3-1.3: USB disconnect, address 6

May 25 12:18:06 localhost kernel: [ 5327.622942] usb 3-1.3: new full speed USB device using ehci_hcd and address 7
May 25 12:18:06 localhost mtp-probe: checking bus 3, device 7: "/sys/devices/pci0000:00/0000:00:1d.0/usb3/3-1/3-1.3"
May 25 12:18:06 localhost mtp-probe: bus: 3, device: 7 was not an MTP device
May 25 12:18:06 localhost mtp-probe: checking bus 3, device 7: "/sys/devices/pci0000:00/0000:00:1d.0/usb3/3-1/3-1.3"
May 25 12:18:06 localhost mtp-probe: bus: 3, device: 7 was not an MTP device
May 25 12:18:07 localhost kernel: [ 5327.947972] usb 3-1.3: USB disconnect, address 7

May 25 12:18:07 localhost kernel: [ 5328.132607] usb 3-1.3: new full speed USB device using ehci_hcd and address 8
May 25 12:18:07 localhost mtp-probe: checking bus 3, device 8: "/sys/devices/pci0000:00/0000:00:1d.0/usb3/3-1/3-1.3"
May 25 12:18:07 localhost mtp-probe: bus: 3, device: 8 was not an MTP device
May 25 12:18:07 localhost mtp-probe: checking bus 3, device 8: "/sys/devices/pci0000:00/0000:00:1d.0/usb3/3-1/3-1.3"
May 25 12:18:07 localhost mtp-probe: bus: 3, device: 8 was not an MTP device
May 25 12:18:07 localhost kernel: [ 5328.459533] usb 3-1.3: USB disconnect, address 8

The device that triggers these messages is a ColorVision Spyder (color calibration). When I unplug the Spyder, the messages loop stops; and when I plug the device in again, it resumes. See also http://lists.fedoraproject.org/pipermai … 99834.html for a Fedora-user experiencing the same problems.

The system is up to date with all packages; the kernel is the standard kernel26. As far as I'm aware of, this problem does not occur on my Ubuntu install (10.10, 11.04).

I guess the 'lsusb -v' output for the Spyder may be relevant:

Bus 003 Device 053: ID 085c:0300 ColorVision, Inc. 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x085c ColorVision, Inc.
  idProduct          0x0300 
  bcdDevice            1.06
  iManufacturer           1 
  iProduct                2 
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           25
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          4 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              5 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              10
Device Status:     0x000a
  (Bus Powered)
  Remote Wakeup Enabled

Can I stop this somehow (short of unplugging the Spyder when I'm in Arch)? Should I file a bug report, and where? Your help will be greatly appreciated.

(Btw, this is my first post here. Apart from this problem, my experiences with Arch are great.)

Last edited by hermanr (2012-02-12 15:45:11)

ewaller · 2011-05-25 17:24:40

Do you have a file called /etc/udev/rules.d/libmtp.rules on your system?
Is your Device listed in that file?

I assume you have installed libmtp. Yes?

BTW, I have no idea what i'm doing here. I've never used mtp stuff -- USB problems piqued my interest.

hermanr · 2011-05-25 18:12:51

Thanks for your interest in my topic.

ewaller wrote:

Do you have a file called /etc/udev/rules.d/libmtp.rules on your system?
Is your Device listed in that file?
I assume you have installed libmtp. Yes?

Libmtp is installed on my system as a dependency of banshee; I have no use for it. The libmtp.rules file is installed in /lib/udev/rules.d (not in /etc/udev/rules.d), but my device is not listed in this file (or in any other).

I have tried to make a specific udev rule for my device in /etc/udev/rules.d/22-color.rules:

SUBSYSTEM==”usb_device”, SYSFS{idVendor}==”085c″, SYSFS{idProduct}==”0300″, MODE=”660″, GROUP=”scanner”

This line was suggested on some other site for the use of the Spyder under Linux. My knowledge of udev is very limited, but it was worth trying. It did not work, however.

wladimir · 2011-11-11 12:06:28

I have the same problem. In my case, the device (Philips AMBX) also isn't listed specifically in the mtp rules file. However, the last line has a catch-all condition that somehow includes it:

# Autoprobe vendor-specific, communication and PTP devices
ENV{ID_MTP_DEVICE}!="1", ATTR{bDeviceClass}=="00|02|06|ef|ff", PROGRAM="mtp-probe /sys$env{DEVPATH} $attr{busnum} $attr{devnum}", RESULT=="1", SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"

Commenting out this line solved the issue. It seems that the mtp-probe tool is not completely safe an disconnects some kinds of devices. It would be better if it somehow remembered that a device is not a MTP device and doesn't try again and again...

Giniu · 2011-11-12 18:08:57

I've also hit same issue with Spyder 3, decided to remove libmtp and it works. I also know that if you rename the mtp-probe file before plugging the device in, it will work. Maybe the problem is not with udev, but in mtp-probe file itself? Ubuntu guys fight with same issue - there are some other proposed solutions in that thread: https://bugs.launchpad.net/ubuntu/+sour … bug/874293 - especially - as noted in http://sourceforge.net/tracker/?func=de … tid=809061 - the libmtp 1.1.1 (released in October) should have the issue fixed.

Last edited by Giniu (2011-11-12 18:12:00)

iosonofabio · 2011-11-16 15:21:02

I also had to fight for this issue. I got an USB from a friend and it just didn't generate any /dev/sdx resource. After eliminating libmtp - which includes uninstalling VLC - and rebooting, everything works again.

hermanr · 2012-02-12 15:43:19

Giniu wrote:

the libmtp 1.1.1 (released in October) should have the issue fixed.

Yes, it does seem to be fixed now!

Arch Linux

#1 2011-05-25 11:40:15

USB-device triggers endless device checking [SOLVED]

#2 2011-05-25 17:24:40

Re: USB-device triggers endless device checking [SOLVED]

#3 2011-05-25 18:12:51

Re: USB-device triggers endless device checking [SOLVED]

#4 2011-11-11 12:06:28

Re: USB-device triggers endless device checking [SOLVED]

#5 2011-11-12 18:08:57

Re: USB-device triggers endless device checking [SOLVED]

#6 2011-11-16 15:21:02

Re: USB-device triggers endless device checking [SOLVED]

#7 2012-02-12 15:43:19

Re: USB-device triggers endless device checking [SOLVED]

Board footer