log files of different OSes caused and not caused by this problem

The OSes:
1. Windows 7
2. Windows XP
3. FreeBSD 9.3
are not affected by "new high-speed USB device number" problem. They works fine.
The FreeBSD 9.3 just report about some error for umass:

Oct 18 00:30:23  kernel: (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 
24 00 
Oct 18 00:30:23  kernel: (probe0:umass-sim0:0:0:0): CAM status: CCB request 
completed with an error
Oct 18 00:30:23  kernel: (probe0:umass-sim0:0:0:0): Retrying command
Oct 18 00:30:23  kernel: (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 
24 00 
Oct 18 00:30:23  kernel: (probe0:umass-sim0:0:0:0): CAM status: CCB request 
completed with an error
Oct 18 00:30:23  kernel: (probe0:umass-sim0:0:0:0): Error 5, Retries exhausted


4. cinnamon mint 15 (3.8.0-19-generic) works fine, but kern.log file is spamed 
by this messages:

Oct 21 13:54:17 kes-desktop kernel: [ 4260.504011] usb 1-2: new high-speed USB 
device number 34 using ehci-pci
Oct 21 13:54:17 kes-desktop kernel: [ 4260.572330] hub 1-0:1.0: unable to 
enumerate USB device on port 2
Oct 21 13:54:17 kes-desktop kernel: [ 4260.788218] hub 1-0:1.0: unable to 
enumerate USB device on port 2

5. ubuntu 12.04 also is not affected.

These has problems:
1. ubuntu 14.04. It is loading too slow and after loading I can not visit sites 
that uses adobe_flash plugin. The browser is halted (see print_screen: 
ubuntu-14.04-ishalted.png).

2. cinnamon-mint-16
3. Fresh installation of 17.1

I also want to check how work mint 14 and 13, but I can not install them
due to the installer error

The detailed log messages for those systems see at attachment

It seems some bug is introduced to the new kernels. If someone give me detaided 
instructions how to use bisect and how to compile/install kernels from source I 
can complete that.
Thank you.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/88746

Title:
  ehci_hcd module causes I/O errors in USB 2.0 devices

Status in Linux:
  Invalid
Status in linux package in Ubuntu:
  Won't Fix
Status in linux-source-2.6.20 package in Ubuntu:
  Won't Fix
Status in linux-source-2.6.22 package in Ubuntu:
  Won't Fix
Status in linux source package in Hardy:
  Won't Fix
Status in linux-source-2.6.20 source package in Hardy:
  Won't Fix
Status in linux-source-2.6.22 source package in Hardy:
  Won't Fix
Status in linux source package in Intrepid:
  Won't Fix
Status in linux-source-2.6.20 source package in Intrepid:
  Won't Fix
Status in linux-source-2.6.22 source package in Intrepid:
  Won't Fix
Status in linux source package in Jaunty:
  Won't Fix
Status in linux-source-2.6.20 source package in Jaunty:
  Won't Fix
Status in linux-source-2.6.22 source package in Jaunty:
  Won't Fix
Status in linux-source-2.6.22 package in Baltix:
  Invalid
Status in linux package in Fedora:
  Invalid

Bug description:
  Certain USB devices do not work properly, or do not work at all, while
  the ehci_hcd module is loaded.

  A solution is to unload the ehci_hcd module, which is loaded every time the 
computer starts, using the command 'sudo modprobe -r ehci_hcd'. This works fine 
but unfortunatly ehci-hcd is necessary for using USB 2.0, so you lose USB 2.0 
features.
  Another solution is to disable USB 2.0 through the BIOS setup.

  With some devices it is possible to read files normally (ie. copy
  files from an USB pendrive to the computer), but the device
  disconnects abrubtly when you start writing data on the device. In
  some devices it fails after writing a certain amount of data, probably
  the size of the write cache.

  Steps to reproduce:
  1. Insert your USB 2.0 device (like a flash drive)
  2. If the device is recognised and mounted properly try copying a file to it.
  3. Comfirm with the 'dmesg' command that it isn't functioning properly. (I/O 
errors etc)
  4. Remove the USB device
  5. Unload ehci_hcd with  'sudo modprobe -r ehci_hcd'
  6. Insert your USB device again.
  7. Check that everything works. (copy some files, etc.)

  A disproportionate number of individuals report Alcor chipsets in the 
problematic behavior.  See:
  
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/62
  
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/119
  
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/299
  
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/397
  http://bugzilla.kernel.org/show_bug.cgi?id=ehci_hcd

  Noted Workarounds:
  
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/372

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/88746/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to