kernel-packages team mailing list archive

[Michael Sharman <1464969@xxxxxxxxxxxxxxxxxx>]

msharman@laptop-msharman:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
N56VM.214
08/28/2012

Thanks, for some reason it didn't occur to me to check for out dated
BIOS. I've updated the BIOS to the 214 version which indeed has made a
significant change. Ubuntu now attachs to the phone with the file
manager when it is plugged in. Add if I eject the phone (to avoid the
device can not be claimed error in Shotwell) then Shotwell is now able
to read the previews of the photos and import the photos - which is much
better.

However, it isn't stable, I gave the mtp-detect process above a go after
a reboot and the result is better but there were some errors I've
attached the output as the file "mtp-detect-out.txt" and also there are
still errors in the dmesg I've attached the complete dmesg output as
"dmesg-out.txt"

Interestingly after repeating the above mtp-detect hangs as it attempts
to reset the device:

msharman@laptop-msharman:~$ killall gvfs-mtp-volume-monitor
msharman@laptop-msharman:~$ killall gvfs-gphoto2-volume-monitor
msharman@laptop-msharman:~$ mtp-detect

(output attached as mtp-detect-out.txt)

dmesg output:

[   51.197549] usb 1-4: USB disconnect, device number 3
[   54.520400] usb 1-4: new high-speed USB device number 4 using xhci_hcd
[   54.649665] usb 1-4: New USB device found, idVendor=04e8, idProduct=6860
[   54.649672] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   54.649676] usb 1-4: Product: SAMSUNG_Android
[   54.649679] usb 1-4: Manufacturer: SAMSUNG
[   54.649682] usb 1-4: SerialNumber: 2410ba56
[  131.389969] usb 1-4: usbfs: process 2263 (pool) did not claim interface 0 before use
[  131.501544] usb 1-4: reset high-speed USB device number 4 using xhci_hcd
[  131.630174] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88022409da48
[  131.630180] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88022409da00
[  131.630184] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88022409da90
[  131.630628] usb 1-4: usbfs: process 2263 (pool) did not claim interface 0 before use
[  131.630712] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use
[  131.630828] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use
[  131.630841] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use
[  131.630856] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use
[  131.630872] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use
[  131.630900] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use
[  131.631012] usb 1-4: usbfs: process 2263 (pool) did not claim interface 0 before use


msharman@laptop-msharman:~$ mtp-detect
Unable to open ~/.mtpz-data for reading, MTPZ disabled.
libmtp version: 1.1.8

Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
   Found 1 device(s):
   Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 10
Attempting to connect device(s)

Seems to hang here.

For reference my list of steps is now:

1. Plug in device

2. Click "Eject" when notification about device attached appears
(otherwise will get an error about device being claimed).

3. Kill gvfs processes because they stop mtp-detect from working.
msharman@laptop-msharman:~$ killall gvfs-gphoto2-volume-monitor
msharman@laptop-msharman:~$ killall gvfs-mtp-volume-monitor 

5. Make sure phone is unlocked and then run mtp-detect
 
Works but has errors.

5. Make sure phone is unlocked and then run mtp-detect a second time.

This time it hangs.

As before I tried updating to the most recent mainline kernel 4.1rc7 but
the same symptoms were present the dmesg output was different again
(I've attached this as dmesg-out-41.rc7.txt)

** Attachment added: "dmesg output kernel 3.19.0-20"
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464969/+attachment/4415376/+files/dmesg-out.txt

-- 
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/1464969

Title:
  Unable to import photos from Samsung Galaxy Note 3

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm having trouble accessing photos or files on my Samsung Galaxy Note
  3 phone.

  Plugging in phone and using Shotwell, then clikcing on the
  SMASUNG_Android camera cause a "Could not claim USB device (-53)"
  error, which when dismissed just displays a "Starting import please
  wait" message indefinitely.

  In an attempt to figure out what is going wrong I've been using the
  mtp-detect command as per
  https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556

  So this is a log of what I've done:

  (running kernel is 3.19.0-20-generic)

  1. Unplug and plug in Samsung Galaxy Note 3 and get dmesg output:

  [   25.386168] usb 1-2: USB disconnect, device number 2
  [   28.245983] usb 1-2: new high-speed USB device number 4 using xhci_hcd
  [   28.375245] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860
  [   28.375247] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
  [   28.375249] usb 1-2: Product: SAMSUNG_Android
  [   28.375250] usb 1-2: Manufacturer: SAMSUNG
  [   28.375251] usb 1-2: SerialNumber: 2410ba56

  2. Kill any gvfs processes that might interfere with with mtp-detect

  msharman@laptop-msharman:~$ killall gvfs-gphoto2-volume-monitor
  msharman@laptop-msharman:~$ killall gvfs-mtp-volume-monitor

  3. Make sure phone is unlocked and run mtp-detect:
  msharman@laptop-msharman:~$ mtp-detect
  Unable to open ~/.mtpz-data for reading, MTPZ disabled.
  libmtp version: 1.1.8

  Listing raw device(s)
  Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
     Found 1 device(s):
     Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 4
  Attempting to connect device(s)
  PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
  LIBMTP libusb: Attempt to reset device
  LIBMTP PANIC: failed to open session on second attempt
  Unable to open raw device 0
  OK.

  4. Check dmesg output:
  msharman@laptop-msharman:~$ dmesg | tail
  [   28.375250] usb 1-2: Manufacturer: SAMSUNG
  [   28.375251] usb 1-2: SerialNumber: 2410ba56
  [   88.552728] usb 1-2: reset high-speed USB device number 4 using xhci_hcd
  [   88.681995] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800b8731348
  [   88.681999] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800b8731300
  [   88.682000] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800b8731390
  [  217.756010] usb 1-2: reset high-speed USB device number 4 using xhci_hcd
  [  217.885218] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800b8731348
  [  217.885227] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800b8731300
  [  217.885230] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800b8731390

  It looks like there could be an xhci related kernel bug?

  So I tried using a newer mainline kernel: http://kernel.ubuntu.com
  /~kernel-ppa/mainline/v4.0-vivid/linux-
  image-4.0.0-040000-generic_4.0.0-040000.201504121935_amd64.deb

  With this kernel I get different dmesg output but the mtp-detect still
  fails (following the exact same procedure as above but I'm just
  showing the differences here)

  (running kernel 4.0.0)

  msharman@laptop-msharman:~$ mtp-detect
  Unable to open ~/.mtpz-data for reading, MTPZ disabled.
  libmtp version: 1.1.8

  Listing raw device(s)
  Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
     Found 1 device(s):
     Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 4
  Attempting to connect device(s)
  PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
  LIBMTP libusb: Attempt to reset device
  inep: usb_get_endpoint_status(): No such device
  outep: usb_get_endpoint_status(): No such device
  libusb_open() failed!: No such device
  LIBMTP PANIC: Could not init USB on second attempt
  Unable to open raw device 0
  OK.

  msharman@laptop-msharman:~$ dmesg | tail
  [  212.229605] usb 2-2: Product: SAMSUNG_Android
  [  212.229608] usb 2-2: Manufacturer: SAMSUNG
  [  212.229610] usb 2-2: SerialNumber: 2410ba56
  [  215.164011] usb 2-2: USB disconnect, device number 2
  [  215.503911] usb 1-2: new high-speed USB device number 5 using xhci_hcd
  [  215.634182] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860
  [  215.634189] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
  [  215.634193] usb 1-2: Product: SAMSUNG_Android
  [  215.634196] usb 1-2: Manufacturer: SAMSUNG
  [  215.634198] usb 1-2: SerialNumber: 2410ba56

  So upgrading to kernel 4.0 hasdone something it's fixed the xhci_hcd
  related errors but the mtp-detect is still failing (I've tried gphoto2
  -L as well and got similar results).

  So I'm not which package the bug is in: could kernel, libmtp, libusb
  or somethings else ?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-20-generic 3.19.0-20.20
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   msharman   1487 F...m pulseaudio
   /dev/snd/controlC0:  msharman   1487 F.... pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Jun 14 16:59:23 2015
  InstallationDate: Installed on 2012-10-21 (966 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Beta amd64(20120926)
  JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found.
  MachineType: ASUSTeK COMPUTER INC. N56VM
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=74f18c4b-8b58-4e8b-9dfe-83f9b08086da ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-20-generic N/A
   linux-backports-modules-3.19.0-20-generic  N/A
   linux-firmware                             1.143.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-06-11 (2 days ago)
  WifiSyslog:
   
  dmi.bios.date: 03/01/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VM.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VM.204:bd03/01/2012:svnASUSTeKCOMPUTERINC.:pnN56VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N56VM
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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