Can not connect to Nexus 4 device (Android 5.1)

Bug #1439694 reported by Benedikt
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I can not connect to an nexus 4 device with current vivid. I see the following messages in syslog:

Apr 2 15:16:39 benediktZ50-70 kernel: [ 3492.132021] usb 1-3: new high-speed USB device number 16 using xhci_hcd
Apr 2 15:16:39 benediktZ50-70 kernel: [ 3492.261235] usb 1-3: New USB device found, idVendor=18d1, idProduct=4ee7
Apr 2 15:16:39 benediktZ50-70 kernel: [ 3492.261241] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 2 15:16:39 benediktZ50-70 kernel: [ 3492.261243] usb 1-3: Product: Nexus 4
Apr 2 15:16:39 benediktZ50-70 kernel: [ 3492.261245] usb 1-3: Manufacturer: LGE
Apr 2 15:16:39 benediktZ50-70 kernel: [ 3492.261248] usb 1-3: SerialNumber: 007a279647d4254f
Apr 2 15:16:39 benediktZ50-70 kernel: [ 3492.276487] usb 1-3: USB disconnect, device number 16
Apr 2 15:16:39 benediktZ50-70 kernel: [ 3492.548230] usb 1-3: new high-speed USB device number 17 using xhci_hcd
Apr 2 15:16:39 benediktZ50-70 kernel: [ 3492.677291] usb 1-3: New USB device found, idVendor=18d1, idProduct=4ee7
Apr 2 15:16:39 benediktZ50-70 kernel: [ 3492.677296] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 2 15:16:39 benediktZ50-70 kernel: [ 3492.677298] usb 1-3: Product: Nexus 4
Apr 2 15:16:39 benediktZ50-70 kernel: [ 3492.677300] usb 1-3: Manufacturer: LGE
Apr 2 15:16:39 benediktZ50-70 kernel: [ 3492.677301] usb 1-3: SerialNumber: 007a279647d4254f
Apr 2 15:16:39 benediktZ50-70 kernel: [ 3492.689716] usb 1-3: USB disconnect, device number 17
Apr 2 15:16:39 benediktZ50-70 kernel: [ 3492.960443] usb 1-3: new high-speed USB device number 18 using xhci_hcd
Apr 2 15:16:40 benediktZ50-70 kernel: [ 3493.089519] usb 1-3: New USB device found, idVendor=18d1, idProduct=4ee7
Apr 2 15:16:40 benediktZ50-70 kernel: [ 3493.089524] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 2 15:16:40 benediktZ50-70 kernel: [ 3493.089526] usb 1-3: Product: Nexus 4
Apr 2 15:16:40 benediktZ50-70 kernel: [ 3493.089528] usb 1-3: Manufacturer: LGE
Apr 2 15:16:40 benediktZ50-70 kernel: [ 3493.089529] usb 1-3: SerialNumber: 007a279647d4254f
Apr 2 15:16:40 benediktZ50-70 mtp-probe: checking bus 1, device 18: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3"
Apr 2 15:16:40 benediktZ50-70 mtp-probe: bus: 1, device: 18 was not an MTP device
Apr 2 15:16:40 benediktZ50-70 kernel: [ 3493.103095] usb 1-3: USB disconnect, device number 18
Apr 2 15:16:40 benediktZ50-70 kernel: [ 3493.372719] usb 1-3: new high-speed USB device number 19 using xhci_hcd
Apr 2 15:16:40 benediktZ50-70 kernel: [ 3493.501867] usb 1-3: New USB device found, idVendor=18d1, idProduct=4ee7
Apr 2 15:16:40 benediktZ50-70 kernel: [ 3493.501872] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 2 15:16:40 benediktZ50-70 kernel: [ 3493.501874] usb 1-3: Product: Nexus 4
Apr 2 15:16:40 benediktZ50-70 kernel: [ 3493.501876] usb 1-3: Manufacturer: LGE
Apr 2 15:16:40 benediktZ50-70 kernel: [ 3493.501877] usb 1-3: SerialNumber: 007a279647d4254f
Apr 2 15:16:40 benediktZ50-70 kernel: [ 3493.525156] usb 1-3: USB disconnect, device number 19
Apr 2 15:16:40 benediktZ50-70 kernel: [ 3493.796966] usb 1-3: new high-speed USB device number 20 using xhci_hcd
Apr 2 15:16:40 benediktZ50-70 kernel: [ 3493.925705] usb 1-3: New USB device found, idVendor=18d1, idProduct=4ee7
Apr 2 15:16:40 benediktZ50-70 kernel: [ 3493.925709] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 2 15:16:40 benediktZ50-70 kernel: [ 3493.925711] usb 1-3: Product: Nexus 4
Apr 2 15:16:40 benediktZ50-70 kernel: [ 3493.925712] usb 1-3: Manufacturer: LGE
Apr 2 15:16:40 benediktZ50-70 kernel: [ 3493.925714] usb 1-3: SerialNumber: 007a279647d4254f
Apr 2 15:16:40 benediktZ50-70 kernel: [ 3493.937356] usb 1-3: USB disconnect, device number 20
Apr 2 15:16:41 benediktZ50-70 kernel: [ 3494.209206] usb 1-3: new high-speed USB device number 21 using xhci_hcd
Apr 2 15:16:41 benediktZ50-70 kernel: [ 3494.338672] usb 1-3: New USB device found, idVendor=18d1, idProduct=4ee7
Apr 2 15:16:41 benediktZ50-70 kernel: [ 3494.338677] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 2 15:16:41 benediktZ50-70 kernel: [ 3494.338679] usb 1-3: Product: Nexus 4
Apr 2 15:16:41 benediktZ50-70 kernel: [ 3494.338681] usb 1-3: Manufacturer: LGE
Apr 2 15:16:41 benediktZ50-70 kernel: [ 3494.338682] usb 1-3: SerialNumber: 007a279647d4254f
Apr 2 15:16:41 benediktZ50-70 mtp-probe: checking bus 1, device 21: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3"
Apr 2 15:16:41 benediktZ50-70 mtp-probe: bus: 1, device: 21 was not an MTP device
Apr 2 15:16:41 benediktZ50-70 kernel: [ 3494.351098] usb 1-3: USB disconnect, device number 21

I will test with a new upstream kernel shortly.
---
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
DistroRelease: Ubuntu 15.04
InstallationDate: Installed on 2014-12-21 (102 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141218)
Package: linux (not installed)
Tags: vivid
Uname: Linux 4.0.0-rc6+ x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
_MarkForUpload: True

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1439694

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Benedikt (benedikt-klotz) wrote : JournalErrors.txt

apport information

tags: added: apport-collected vivid
description: updated
Revision history for this message
Benedikt (benedikt-klotz) wrote : ProcEnviron.txt

apport information

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem.

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Benedikt (benedikt-klotz) wrote :
Download full text (10.7 KiB)

correction:

This issue does only occur if the usb debugging mode of android is used. In the normal mtp mode I only see a bunch of warnings, but it seems to work as expected :

[ 125.037365] usb 1-3: new high-speed USB device number 6 using xhci_hcd
[ 125.166184] usb 1-3: New USB device found, idVendor=18d1, idProduct=4ee1
[ 125.166187] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 125.166190] usb 1-3: Product: Nexus 4
[ 125.166191] usb 1-3: Manufacturer: LGE
[ 125.166193] usb 1-3: SerialNumber: 007a279647d4254f
[ 126.191381] usb 1-3: usbfs: process 1983 (ThreadWeaver::T) did not claim interface 0 before use
[ 126.362319] usb 1-3: reset high-speed USB device number 6 using xhci_hcd
[ 126.490585] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802054f5048
[ 126.490589] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802054f5000
[ 126.490591] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802054f5090
[ 126.491094] usb 1-3: usbfs: process 1983 (ThreadWeaver::T) did not claim interface 0 before use
[ 126.491120] usb 1-3: usbfs: process 1985 (ThreadWeaver::T) did not claim interface 0 before use
[ 126.491135] usb 1-3: usbfs: process 1985 (ThreadWeaver::T) did not claim interface 0 before use
[ 126.491142] usb 1-3: usbfs: process 1985 (ThreadWeaver::T) did not claim interface 0 before use
[ 126.491147] usb 1-3: usbfs: process 1985 (ThreadWeaver::T) did not claim interface 0 before use
[ 126.491153] usb 1-3: usbfs: process 1985 (ThreadWeaver::T) did not claim interface 0 before use
[ 126.491159] usb 1-3: usbfs: process 1985 (ThreadWeaver::T) did not claim interface 0 before use
[ 126.491164] usb 1-3: usbfs: process 1985 (ThreadWeaver::T) did not claim interface 0 before use
[ 126.491170] usb 1-3: usbfs: process 1985 (ThreadWeaver::T) did not claim interface 0 before use
[ 126.491176] usb 1-3: usbfs: process 1985 (ThreadWeaver::T) did not claim interface 0 before use
[ 126.491181] usb 1-3: usbfs: process 1985 (ThreadWeaver::T) did not claim interface 0 before use
[ 126.491187] usb 1-3: usbfs: process 1985 (ThreadWeaver::T) did not claim interface 0 before use
[ 126.491192] usb 1-3: usbfs: process 1985 (ThreadWeaver::T) did not claim interface 0 before use
[ 126.491197] usb 1-3: usbfs: process 1985 (ThreadWeaver::T) did not claim interface 0 before use
[ 126.491203] usb 1-3: usbfs: process 1985 (ThreadWeaver::T) did not claim interface 0 before use
[ 126.491209] usb 1-3: usbfs: process 1985 (ThreadWeaver::T) did not claim interface 0 before use
[ 126.491215] usb 1-3: usbfs: process 1985 (ThreadWeaver::T) did not claim interface 0 before use
[ 126.491220] usb 1-3: usbfs: process 1985 (ThreadWeaver::T) did not claim interface 0 before use
[ 126.491226] usb 1-3: usbfs: process 1985 (ThreadWeaver::T) did not claim interface 0 before use
[ 126.491232] usb 1-3: usbfs: process 1985 (ThreadWeaver::T) did not claim interface 0 before use
[ 126.491237] usb 1-3: usbfs: process 1985 (ThreadWeaver::T) did not claim interface 0 before use
[ 126.491243] usb 1-3: usbfs: process 1985 (ThreadWeaver::T) did not claim interface 0 bef...

Revision history for this message
penalvch (penalvch) wrote :

Benedikt, could you please boot into the default Ubuntu kernel (not a mainline one) and then execute the following:
apport-collect 1439694

Revision history for this message
Benedikt (benedikt-klotz) wrote :

After a little experimenting with different android developer settings I can no longer reproduce this issue. I think the connection loop was because of an Android usb issue and not an ubuntu kernel problem. Closing as invalid

Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.