USB MTP device disconnected automatically

[sk]

On connecting an android device in MTP mode to my ubuntu laptop, it showed up as an MTP device. After some time it stopped showing the device. On connecting and dis-connecting the device multiple times, dmesg doesn't show any output (Didn't get the dmesg output this time). Even after rebooting the device is not detected. Tried reboot multiple times. dmesg shows that the device was detected and immediately disconnected.

[ 2.505545] usb 2-1.4: new high-speed USB device number 4 using ehci_hcd
[ 2.599906] usb 2-1.4: New USB device found, idVendor=04e8, idProduct=6860
[ 2.599921] usb 2-1.4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 2.599932] usb 2-1.4: Product: SAMSUNG_Android
[ 2.599939] usb 2-1.4: Manufacturer: SAMSUNG
[ 2.599946] usb 2-1.4: SerialNumber: 4df1a23921e85f5d
[ 2.652289] usb 2-1.4: USB disconnect, device number 4

Same thing works on windows dual boot on same machine. So don't think it is a hardware issue. Also had the same issue on my office machine as well. Was working properly on 12.04 on office machine.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-18-generic 3.5.0-18.29
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: sree 2640 F.... pulseaudio
 /dev/snd/controlC0: sree 2640 F.... pulseaudio
Date: Sun Nov 11 01:16:30 2012
HibernationDevice: RESUME=/dev/sda6
InstallationDate: Installed on 2010-10-14 (758 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: LENOVO 20041
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=3e51c732-6111-4252-a7c3-9a4697c1ace6 ro vga=792 splash crashkernel=384M-2G:64M,2G-:128M splash
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-18-generic N/A
 linux-backports-modules-3.5.0-18-generic N/A
 linux-firmware 1.95
SourcePackage: linux
UpgradeStatus: Upgraded to quantal on 2012-09-07 (64 days ago)
dmi.bios.date: 01/29/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 29CN17WW(V1.05)
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: LENOVO
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnLENOVO:bvr29CN17WW(V1.05):bd01/29/2010:svnLENOVO:pn20041:pvrLenovoG460:rvnLENOVO:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: 20041
dmi.product.version: Lenovo G460
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[sk (sreekumar-r84-live)]

Attaching complete dmesg

[sk (sreekumar-r84-live)]

Thanks brad-figg or confirming. Is there a way to manually disable or reset the bot, at least temporarily?

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.7 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc5-raring/

[sk (sreekumar-r84-live)]

The bug exists with upstream kernel as well.
sree@sree-laptop:~$ dmesg | grep " usb 2-1.4"
[ 2.384640] usb 2-1.4: new high-speed USB device number 4 using ehci_hcd
[ 2.478106] usb 2-1.4: New USB device found, idVendor=04e8, idProduct=6860
[ 2.478115] usb 2-1.4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 2.478122] usb 2-1.4: Product: SAMSUNG_Android
[ 2.478127] usb 2-1.4: Manufacturer: SAMSUNG
[ 2.478132] usb 2-1.4: SerialNumber: 4df1a23921e85f5d
[ 2.531339] usb 2-1.4: USB disconnect, device number 4
sree@sree-laptop:~$ uname -a
Linux sree-laptop 3.7.0-030700rc5-generic #201211110835 SMP Sun Nov 11 13:35:49 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

[penalvch (penalvch)]

sk, as per http://download.lenovo.com/express/ddfm.html an update is available for your BIOS (29CN38WW). If you update to this, does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Vadim Peretokin (vperetokin)]

I'm having the same issue - unable to mount my Android phone because it gets disconnected immediately:

Nov 14 19:08:36 gooseberry kernel: [94970.949576] usb 1-1.3: new high-speed USB device number 56 using ehci-pci
Nov 14 19:08:36 gooseberry kernel: [94971.042204] usb 1-1.3: New USB device found, idVendor=04e8, idProduct=6860
Nov 14 19:08:36 gooseberry kernel: [94971.042210] usb 1-1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Nov 14 19:08:36 gooseberry kernel: [94971.042213] usb 1-1.3: Product: Android
Nov 14 19:08:36 gooseberry kernel: [94971.042215] usb 1-1.3: Manufacturer: Android
Nov 14 19:08:36 gooseberry kernel: [94971.042217] usb 1-1.3: SerialNumber: 00193bfe6f686e
Nov 14 19:08:36 gooseberry kernel: [94971.097927] usb 1-1.3: USB disconnect, device number 56

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Vadim Peretokin, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]