Ubuntu

0489:c001 Kernel regression Android Phone will not mount as USB drive Ubuntu 12.10 Beta2

Reported by albert fishnets on 2012-10-12
42
This bug affects 8 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned

Bug Description

I updated my laptop to ubuntu 12.10 beta 2 to take it for a test drive. When I try to mount my android phone to manage my music and pictures the phone is not detected by the system and does not mount. This action was "plug-and-play" in 12.04, I would plug in the exact same USB cord on the exact same phone into the exact same port and the phone would respond by asking to have USB enabled. Then Ubuntu 12.04 would mount the phone as a drive and it would show up in Rhythumbox with the addition of a .ls_audio_player file in the phones root directory.

The phone still mounts using the same cord on the same port in ubuntu 12.04 and windows 7 on the same machine, but when I switch to 12.10 Beta 2 the phone is not detected. I tried a different phone, but my girl friend and house mates phone also will not mount in ubuntu 12.10 beta 2.

To reproduce:

1.) Plug USB cord into computer.

2.) Plug cord into phone.

3.) Phone does not register cord but does get power to charge.

Perform same steps with exact same hardware in Ubuntu 12.04 and phone responds asking to engage USB mode and as soon as button is pressed, phone mounts automatically as a USB drive in Unity.

Any ideas?

Tried in live disk on desktop machine. Got the same results.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-17-generic 3.5.0-17.28
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic i686
ApportVersion: 2.6.1-0ubuntu3
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mateo 1897 F.... pulseaudio
Date: Fri Oct 12 05:36:56 2012
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta i386 (20121010)
MachineType: ASUSTeK Computer INC. 1005PE
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=67e22f9e-8935-41d7-b493-4e1946e0c2f4 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-17-generic N/A
 linux-backports-modules-3.5.0-17-generic N/A
 linux-firmware 1.94
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/29/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1103
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1005P
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1103:bd04/29/2010:svnASUSTeKComputerINC.:pn1005PE:pvrx.x:rvnASUSTeKComputerINC.:rn1005P:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1005PE
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

Brad Figg (brad-figg) on 2012-10-12
Changed in linux (Ubuntu):
status: New → Confirmed
Joseph Salisbury (jsalisbury) wrote :

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

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

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.6-quantal/

tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: kernel-da-key

Attempted test with newer kernel. No change. Same issue presist. Further more, the newer kernel would not allow any USB plug and play devices to mount including SD card and thumb drive. Also killed bluetooth support.

tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Confirmed

albert fishnets, thank you for reporting this and helping make Ubuntu better. Could you please plug the USB phone in, unplug all other USB devices, execute the following in a terminal, and post the results to this report:
lsusb

If the device does not show in Quantal, please perform the above from a Precise environment.

As well, could you please test the newest mainline kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6.2-quantal/ following https://wiki.ubuntu.com/Kernel/MainlineBuilds ?

Thank you for your understanding.

tags: added: regression-release
tags: added: kernel-bug-exists-upstream-v3.6-quantal needs-upstream-testing
removed: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Confirmed → Incomplete

lsusb with only the phone plugged in issues:

Bus 001 Device 003: ID 13d3:5111 IMC Networks Integrated Webcam
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

It issues the same when no devices are plugged in.

Kernel test install 3.6.2 produces the same results. Phone is not detected. Other USB devices do work and are mounted. lsusb with new kernel produces the same code as when nothing is plugged in:

Bus 001 Device 002: ID 13d3:5111 IMC Networks Integrated Webcam
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

tags: added: kernel-bug-exists-upstream-v3.6.2-quantal
removed: needs-upstream-testing

albert fishnets, thank you for testing the newest mainline kernel. In addition to providing the information requested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065964/comments/4 :
>"If the device does not show in Quantal, please perform the above from a Precise environment."

the next step is to perform a kernel bisect from Precise to Quantal linux-image-3.5.0-17-generic, in order to identify the offending commit(s). Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Thank you for your understanding.

lsusb from Ubuntu 12.04 Precise with phone mounted:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 058f:6335 Alcor Micro Corp. SD/MMC Card Reader
Bus 001 Device 003: ID 13d3:5111 IMC Networks Integrated Webcam
Bus 001 Device 005: ID 0489:c001 Foxconn / Hon Hai

Here is lsusb from ubuntu 12.04 precise with phone not mounted:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 058f:6335 Alcor Micro Corp. SD/MMC Card Reader
Bus 001 Device 003: ID 13d3:5111 IMC Networks Integrated Webcam

looks like 12.10 is failing to detect:

My SD card reader:

Bus 001 Device 002: ID 058f:6335 Alcor Micro Corp. SD/MMC Card Reader

My Android Phone:

Bus 001 Device 005: ID 0489:c001 Foxconn / Hon Hai

Both work right out of the box in 12.04

summary: - Kernel regression Android Phone will not mount as USB drive Ubuntu 12.10
- Beta2
+ 0489:c001 Kernel regression Android Phone will not mount as USB drive
+ Ubuntu 12.10 Beta2

This sounds like the same bug. I agree this one should be marked as a duplicate and merged with that one.

Ming Lei <email address hidden> wrote:

>This one should be same with 1047527
>
>https://bugs.launchpad.net/bugs/1047527
>
>--
>You received this bug notification because you are subscribed to the
>bug
>report.
>https://bugs.launchpad.net/bugs/1065964
>
>Title:
> 0489:c001 Kernel regression Android Phone will not mount as USB drive
> Ubuntu 12.10 Beta2
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065964/+subscriptions

Matt Thibault

Ming Lei, thank you for taking look as this report. It is noticed in this bug reports attachment https://launchpadlibrarian.net/119581373/CurrentDmesg.txt :
[ 188.444136] usb 1-2: >new high-speed USB device number 5 using ehci_hcd
[ 188.577153] usb 1-2: >Dual-Role OTG device on non-HNP port
[ 188.577265] usb 1-2: >can't set HNP mode: -32

However, we may not want to mark this as a duplicate for the following reasons:
+ Two different USB device vendor IDs being inputted.
+ This report is about i386, bug 1047527 is amd64.
+ This report Xorg = https://launchpad.net/ubuntu/+source/xorg/1:7.7+1ubuntu4 , while bug 1047527 is testing xorg-edgers PPA:
xorg-server 2:1.12.3+git20120709+server-1.12-branch.60e0d205-0ubuntu0ricotz~precise
+ We do not know what USB hardware the OR for bug 1047527 has because no apport-collect.

As we both know, one may experience exactly the same error messages on two different hardware, yet have two different bugs causing it.

Despite these outstanding, and potentially naive, reasons, could you, and/or albert fishnets, please provide a detailed, technical explanation for why you think this report should be marked a duplicate of bug 1047527?

Thank you for your understanding.

I don't honestly know enough about the other bug to make a call based on the reasons sited above.

"Christopher M. Penalver" <email address hidden> wrote:

>Ming Lei, thank you for taking look as this report. It is noticed in
>this bug reports attachment
>https://launchpadlibrarian.net/119581373/CurrentDmesg.txt :
>[ 188.444136] usb 1-2: >new high-speed USB device number 5 using
>ehci_hcd
>[ 188.577153] usb 1-2: >Dual-Role OTG device on non-HNP port
>[ 188.577265] usb 1-2: >can't set HNP mode: -32
>
>However, we may not want to mark this as a duplicate for the following
>reasons:
>+ Two different USB device vendor IDs being inputted.
>+ This report is about i386, bug 1047527 is amd64.
>+ This report Xorg =
>https://launchpad.net/ubuntu/+source/xorg/1:7.7+1ubuntu4 , while bug
>1047527 is testing xorg-edgers PPA:
>xorg-server
>2:1.12.3+git20120709+server-1.12-branch.60e0d205-0ubuntu0ricotz~precise
>+ We do not know what USB hardware the OR for bug 1047527 has because
>no apport-collect.
>
>As we both know, one may experience exactly the same error messages on
>two different hardware, yet have two different bugs causing it.
>
>Despite these outstanding, and potentially naive, reasons, could you,
>and/or albert fishnets, please provide a detailed, technical
>explanation
>for why you think this report should be marked a duplicate of bug
>1047527?
>
>Thank you for your understanding.
>
>--
>You received this bug notification because you are subscribed to the
>bug
>report.
>https://bugs.launchpad.net/bugs/1065964
>
>Title:
> 0489:c001 Kernel regression Android Phone will not mount as USB drive
> Ubuntu 12.10 Beta2
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065964/+subscriptions

Matt Thibault

JCarsique (julien-carsique) wrote :

Bug #1047527 is marked as fixed in 3.5.0-19.30.
I'm running 3.5.0-22 and still encountering the same issue.

JCarsique, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

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

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers