oS 13.1 problems to access phone sd memory

Hi all, I have a galaxy ace S5830i but I can not access its sd memory from my oS 13.1 (kernel 3.11.10-11-desktop, x86_64) . When I connect the usb cable, /var/log/messages shows:

2014-06-02T14:28:02.423340+08:00 caradhras kernel:  4263.059574] usb 3-2: new high-speed USB device number 25 using xhci_hcd
2014-06-02T14:28:05.385289+08:00 caradhras kernel:  4266.025268] usb 3-2: Device not responding to set address.
2014-06-02T14:28:05.586328+08:00 caradhras kernel:  4266.226061] usb 3-2: Device not responding to set address.
2014-06-02T14:28:05.787297+08:00 caradhras kernel:  4266.427205] usb 3-2: device not accepting address 25, error -71
2014-06-02T14:28:06.146249+08:00 caradhras kernel:  4266.786555] usb 3-2: new high-speed USB device number 27 using xhci_hcd
2014-06-02T14:28:06.158290+08:00 caradhras kernel:  4266.799512] usb 3-2: New USB device found, idVendor=04e8, idProduct=685e
2014-06-02T14:28:06.158327+08:00 caradhras kernel:  4266.799555] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2014-06-02T14:28:06.158333+08:00 caradhras kernel:  4266.799566] usb 3-2: Product: BCM21553-Thunderbird
2014-06-02T14:28:06.158337+08:00 caradhras kernel:  4266.799575] usb 3-2: Manufacturer: Broadcom
2014-06-02T14:28:06.158350+08:00 caradhras kernel:  4266.799598] usb 3-2: SerialNumber: 0123456789ABCDEF
2014-06-02T14:28:06.163267+08:00 caradhras kernel:  4266.803997] usb-storage 3-2:1.0: USB Mass Storage device detected
2014-06-02T14:28:06.163307+08:00 caradhras kernel:  4266.804193] scsi14 : usb-storage 3-2:1.0
2014-06-02T14:28:06.164249+08:00 caradhras kernel:  4266.804721] cdc_acm 3-2:1.1: This device cannot do calls on its own. It is not a modem.
2014-06-02T14:28:06.164276+08:00 caradhras kernel:  4266.804836] cdc_acm 3-2:1.1: ttyACM0: USB ACM device
2014-06-02T14:28:06.168499+08:00 caradhras mtp-probe: checking bus 3, device 27: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2"
2014-06-02T14:28:06.169387+08:00 caradhras mtp-probe: bus: 3, device: 27 was not an MTP device
2014-06-02T14:28:08.897407+08:00 caradhras ModemManager[4278]: <info>  Creating modem with plugin 'Generic' and '1' ports
2014-06-02T14:28:08.898001+08:00 caradhras ModemManager[4278]: <info>  Modem for device at '/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2' successfully created
2014-06-02T14:28:08.997069+08:00 caradhras ModemManager[4278]: <warn>  Modem couldn't be initialized: couldn't load current capabilities: Failed to determine modem capabilities.

and nothing else, even if I choose to enable the USB storage on the phone. No notification appears on my DE (lxde) and no sd device is created.

However, if I connect the same phone on my oS 12.3 (different laptop, still lxde), it works as expected and /var/log/messages shows:

2014-06-02T13:07:51.497338+08:00 orodruin kernel:   124.107126] usb 1-1: new high-speed USB device number 2 using ehci_hcd
2014-06-02T13:07:51.613311+08:00 orodruin kernel:   124.223102] usb 1-1: New USB device found, idVendor=04e8, idProduct=685e
2014-06-02T13:07:51.613339+08:00 orodruin kernel:   124.223109] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2014-06-02T13:07:51.613346+08:00 orodruin kernel:   124.223114] usb 1-1: Product: BCM21553-Thunderbird
2014-06-02T13:07:51.613350+08:00 orodruin kernel:   124.223118] usb 1-1: Manufacturer: Broadcom
2014-06-02T13:07:51.613354+08:00 orodruin kernel:   124.223122] usb 1-1: SerialNumber: 0123456789ABCDEF
2014-06-02T13:07:51.622306+08:00 orodruin mtp-probe: checking bus 1, device 2: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-1"
2014-06-02T13:07:51.623302+08:00 orodruin mtp-probe: bus: 1, device: 2 was not an MTP device
2014-06-02T13:07:51.689301+08:00 orodruin kernel:   124.299462] cdc_acm 1-1:1.1: This device cannot do calls on its own. It is not a modem.
2014-06-02T13:07:51.689352+08:00 orodruin kernel:   124.299607] cdc_acm 1-1:1.1: ttyACM0: USB ACM device
2014-06-02T13:07:51.690362+08:00 orodruin kernel:   124.300664] usbcore: registered new interface driver cdc_acm
2014-06-02T13:07:51.690387+08:00 orodruin kernel:   124.300667] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
2014-06-02T13:07:51.714417+08:00 orodruin dbus-daemon[491]: modem-manager[590]: <info>  (ttyACM0) opening serial port...
2014-06-02T13:07:51.715171+08:00 orodruin modem-manager[590]: <info>  (ttyACM0) opening serial port...
2014-06-02T13:07:51.732304+08:00 orodruin kernel:   124.342049] Initializing USB Mass Storage driver...
2014-06-02T13:07:51.732338+08:00 orodruin kernel:   124.342244] scsi6 : usb-storage 1-1:1.0
2014-06-02T13:07:51.732343+08:00 orodruin kernel:   124.342382] usbcore: registered new interface driver usb-storage
2014-06-02T13:07:51.732347+08:00 orodruin kernel:   124.342386] USB Mass Storage support registered.
2014-06-02T13:07:52.734288+08:00 orodruin kernel:   125.344747] scsi 6:0:0:0: Direct-Access     SAMSUNG  S5830i Card      0000 PQ: 0 ANSI: 2
2014-06-02T13:07:52.735557+08:00 orodruin kernel:   125.345600] sd 6:0:0:0: Attached scsi generic sg1 type 0
2014-06-02T13:07:52.737353+08:00 orodruin kernel:   125.347755] sd 6:0:0:0: [sdb] Attached SCSI removable disk
2014-06-02T13:07:55.749450+08:00 orodruin dbus-daemon[491]: modem-manager[590]: <warn>  Couldn't probe for capabilities, probably not a GSM or CDMA modem
2014-06-02T13:07:55.750156+08:00 orodruin modem-manager[590]: <warn>  Couldn't probe for capabilities, probably not a GSM or CDMA modem
2014-06-02T13:07:55.750770+08:00 orodruin modem-manager[590]: <info>  (ttyACM0) closing serial port...
2014-06-02T13:07:55.751355+08:00 orodruin dbus-daemon[491]: modem-manager[590]: <info>  (ttyACM0) closing serial port...
2014-06-02T13:07:55.754077+08:00 orodruin dbus-daemon[491]: modem-manager[590]: <info>  (ttyACM0) serial port closed
2014-06-02T13:07:55.754742+08:00 orodruin modem-manager[590]: <info>  (ttyACM0) serial port closed
2014-06-02T13:07:55.756790+08:00 orodruin dbus-daemon[491]: modem-manager[590]: <info>  (ttyACM0) opening serial port...
2014-06-02T13:07:55.756820+08:00 orodruin modem-manager[590]: <info>  (ttyACM0) opening serial port...
2014-06-02T13:07:59.776554+08:00 orodruin dbus-daemon[491]: modem-manager[590]: <warn>  Couldn't probe for capabilities, probably not a GSM or CDMA modem
2014-06-02T13:07:59.777899+08:00 orodruin modem-manager[590]: <warn>  Couldn't probe for capabilities, probably not a GSM or CDMA modem
2014-06-02T13:07:59.778689+08:00 orodruin dbus-daemon[491]: modem-manager[590]: <info>  (ttyACM0) closing serial port...
2014-06-02T13:07:59.779393+08:00 orodruin modem-manager[590]: <info>  (ttyACM0) closing serial port...
2014-06-02T13:07:59.786316+08:00 orodruin dbus-daemon[491]: modem-manager[590]: <info>  (ttyACM0) serial port closed
2014-06-02T13:07:59.787126+08:00 orodruin modem-manager[590]: <info>  (ttyACM0) serial port closed
2014-06-02T13:08:04.106917+08:00 orodruin su: (to root) ori on /dev/pts/0
2014-06-02T13:08:04.108152+08:00 orodruin su: pam_unix(su:session): session opened for user root by ori(uid=1000)
2014-06-02T13:08:56.291323+08:00 orodruin kernel:   188.901114] sd 6:0:0:0: [sdb] 15519744 512-byte logical blocks: (7.94 GB/7.40 GiB)
2014-06-02T13:08:56.292293+08:00 orodruin kernel:   188.902251] sd 6:0:0:0: [sdb] No Caching mode page present
2014-06-02T13:08:56.292312+08:00 orodruin kernel:   188.902258] sd 6:0:0:0: [sdb] Assuming drive cache: write through
2014-06-02T13:08:56.294749+08:00 orodruin kernel:   188.904233] sd 6:0:0:0: [sdb] No Caching mode page present
2014-06-02T13:08:56.294779+08:00 orodruin kernel:   188.904240] sd 6:0:0:0: [sdb] Assuming drive cache: write through
2014-06-02T13:08:56.296288+08:00 orodruin kernel:   188.906650]  sdb: sdb1
2014-06-02T13:08:56.978559+08:00 orodruin udisksd[1575]: Mounted /dev/sdb1 at /run/media/ori/9016-4EF8 on behalf of uid 1000

solid-hardware returns only:

# solid-hardware listen
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
Listening to add/remove events: 
Device Added:
udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2'
Device Added:
udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0'
Device Added:
udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.1'
Device Added:
udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.2'
Device Added:
udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.1/tty/ttyACM0'
Device Removed:
udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0'
Device Removed:
udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.1/tty/ttyACM0'
Device Removed:
udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.2'
Device Removed:
udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.1'
Device Removed:
udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2'

and fdisk shows only my hard-disk.

Do you have any suggestion on how to fix this issue?
Thanks.

I don’t have a definitive answer to this, but I have seen references to problematic behaviour with some Android devices when usb_modeswitch is invoked. Anyway, you could try globally disabling modeswitching in /etc/usb_modeswitch.conf by changing

DisableSwitching=0

to

DisableSwitching=1

*This won’t suit if you need to activate some types of 3G/4G wireless broadband USB dongles at a later time.

FWIW, I also note that the machine with openSUSE 13.1 is using USB 3 ports (xhci_hcd) reported, while the other is (ehci_hcd). (I don’t know whether that is affecting communication in any way.)

Thanks for the answer.
I tried to change the value for DisableSwitching in /etc/usb_modeswitch.conf but nothing has changed.
However, I do not think it may be related to the problem since no file in /usr/share/usb_modeswitch mentions the device 04e8:685e.

You may need to submit a bug report for the difference in device handling. ModemManager seems to be behaving differently.

OK, created bug https://bugzilla.novell.com/show_bug.cgi?id=881023

I hope its fate is different from other bug reports I filed…

Not that the cause of the incorrect handling has been identified yet, but if it is ModemManager-related, then a perhaps udev rule might help

# Samsung Galaxy Ace S5830i 
ACTION=="add|change", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="685e", ENV{ID_MM_DEVICE_IGNORE}="1"

This could be saved a s a custom rule eg /etc/udev/rules.d/40-galaxy.rules

You could then plug the device in again and observe

dmesg|tail

Thanks but no luck: nothing has changed, except for the reported messages (in /var/log/messages):

2014-06-03T13:07:26.281159+08:00 caradhras kernel: [17635.909408] usb 3-2: new high-speed USB device number 11 using xhci_hcd
2014-06-03T13:07:29.244124+08:00 caradhras kernel: [17638.875660] usb 3-2: Device not responding to set address.
2014-06-03T13:07:29.445158+08:00 caradhras kernel: [17639.076934] usb 3-2: Device not responding to set address.
2014-06-03T13:07:29.646165+08:00 caradhras kernel: [17639.278136] usb 3-2: device not accepting address 11, error -71
2014-06-03T13:07:30.005170+08:00 caradhras kernel: [17639.637543] usb 3-2: new high-speed USB device number 13 using xhci_hcd
2014-06-03T13:07:30.018112+08:00 caradhras kernel: [17639.650484] usb 3-2: New USB device found, idVendor=04e8, idProduct=685e
2014-06-03T13:07:30.018149+08:00 caradhras kernel: [17639.650494] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2014-06-03T13:07:30.018155+08:00 caradhras kernel: [17639.650499] usb 3-2: Product: BCM21553-Thunderbird
2014-06-03T13:07:30.018160+08:00 caradhras kernel: [17639.650503] usb 3-2: Manufacturer: Broadcom
2014-06-03T13:07:30.018165+08:00 caradhras kernel: [17639.650507] usb 3-2: SerialNumber: 0123456789ABCDEF
2014-06-03T13:07:30.021087+08:00 caradhras kernel: [17639.653845] usb-storage 3-2:1.0: USB Mass Storage device detected
2014-06-03T13:07:30.021117+08:00 caradhras kernel: [17639.654035] scsi7 : usb-storage 3-2:1.0
2014-06-03T13:07:30.022104+08:00 caradhras kernel: [17639.654748] cdc_acm 3-2:1.1: This device cannot do calls on its own. It is not a modem.
2014-06-03T13:07:30.022121+08:00 caradhras kernel: [17639.654861] cdc_acm 3-2:1.1: ttyACM0: USB ACM device
2014-06-03T13:07:30.042201+08:00 caradhras mtp-probe: checking bus 3, device 13: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2"
2014-06-03T13:07:30.042695+08:00 caradhras mtp-probe: bus: 3, device: 13 was not an MTP device

If I check via journalctl, the messages are almost the same, except for an extra “Jun 03 13:07:30 caradhras.lotr systemd-udevd[302]: specified group ‘plugdev’ unknown” just before the two entries from mtp-probe.
If I check via dmesg, the two messages from mtp-probe are missing (as well as the systemd-udevd, when compared with journalctl).

If I check via journalctl, the messages are almost the same, except for an extra “Jun 03 13:07:30 caradhras.lotr systemd-udevd[302]: specified group ‘plugdev’ unknown” just before the two entries from mtp-probe.

I don’t know if that is related or not, but in any case there shouldn’t be any rules assigning the group AFAIU. It would be interesting to know what rules you have that refer to ‘plugdev’. Run the following

fgrep -r plugdev /{etc,lib}/udev/rules.d

This is the outcome:

# fgrep -r plugdev /{etc,lib}/udev/rules.d
/etc/udev/rules.d/92-fingerprint-gui-uinput.rules:KERNEL=="uinput", MODE="0660", GROUP="plugdev"

and the file comes from the package fingerprint-gui.
However, even by uninstalling the package, nothing changes (except for the fact that systemd-udevd does not complain anymore).

No, as I mentioned before I didn’t think it was related, but I was interested in turning up the rule. (The ‘plugdev’ group is not used in openSUSE, so the rule is not correct.)

I just made a test: I used the KDE live CD of openSUSE 12.3 to boot the laptop running 13.1 and after having connected the phone (and enabled the usb storage), it worked. So, it seems that is something specific to oS 13.1 as we can exclude problems with the USB port (that should be USB-2) and the xhci_hcd module (unless something changed in such module).
This is the content of /var/log/messages taken from the live system:

2014-06-03T12:06:55.855509+00:00 linux kernel:   232.820367] usb 3-2: new high-speed USB device number 7 using xhci_hcd
2014-06-03T12:06:58.818522+00:00 linux kernel:   235.779340] usb 3-2: Device not responding to set address.
2014-06-03T12:06:59.019573+00:00 linux kernel:   235.980163] usb 3-2: Device not responding to set address.
2014-06-03T12:06:59.220513+00:00 linux kernel:   236.180853] usb 3-2: device not accepting address 7, error -71
2014-06-03T12:06:59.322509+00:00 linux kernel:   236.282754] hub 3-0:1.0: unable to enumerate USB device on port 2
2014-06-03T12:06:59.579547+00:00 linux kernel:   236.539388] usb 3-2: new high-speed USB device number 9 using xhci_hcd
2014-06-03T12:06:59.591498+00:00 linux kernel:   236.552120] usb 3-2: New USB device found, idVendor=04e8, idProduct=685e
2014-06-03T12:06:59.591541+00:00 linux kernel:   236.552130] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2014-06-03T12:06:59.591546+00:00 linux kernel:   236.552135] usb 3-2: Product: BCM21553-Thunderbird
2014-06-03T12:06:59.591550+00:00 linux kernel:   236.552140] usb 3-2: Manufacturer: Broadcom
2014-06-03T12:06:59.591553+00:00 linux kernel:   236.552144] usb 3-2: SerialNumber: 0123456789ABCDEF
2014-06-03T12:07:00.222777+00:00 linux kernel:   237.181923] Initializing USB Mass Storage driver...
2014-06-03T12:07:00.222789+00:00 linux kernel:   237.182016] scsi5 : usb-storage 3-2:1.0
2014-06-03T12:07:00.222790+00:00 linux kernel:   237.182075] usbcore: registered new interface driver usb-storage
2014-06-03T12:07:00.222791+00:00 linux kernel:   237.182076] USB Mass Storage support registered.
2014-06-03T12:07:00.222792+00:00 linux kernel:   237.182098] cdc_acm 3-2:1.1: This device cannot do calls on its own. It is not a modem.
2014-06-03T12:07:00.222793+00:00 linux kernel:   237.182139] cdc_acm 3-2:1.1: ttyACM0: USB ACM device
2014-06-03T12:07:00.222794+00:00 linux kernel:   237.182585] usbcore: registered new interface driver cdc_acm
2014-06-03T12:07:00.222794+00:00 linux kernel:   237.182587] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
2014-06-03T12:07:00.545218+00:00 linux dbus-daemon[1108]: modem-manager[1231]: <info>  (ttyACM0) opening serial port...
2014-06-03T12:07:00.545514+00:00 linux modem-manager[1231]: <info>  (ttyACM0) opening serial port...
2014-06-03T12:07:01.225484+00:00 linux kernel:   238.183595] scsi 5:0:0:0: Direct-Access     SAMSUNG  S5830i Card      0000 PQ: 0 ANSI: 2
2014-06-03T12:07:01.225644+00:00 linux kernel:   238.183769] sd 5:0:0:0: Attached scsi generic sg2 type 0
2014-06-03T12:07:01.226420+00:00 linux kernel:   238.184420] sd 5:0:0:0: [sdb] Attached SCSI removable disk
2014-06-03T12:07:04.565293+00:00 linux dbus-daemon[1108]: modem-manager[1231]: <warn>  Couldn't probe for capabilities, probably not a GSM or CDMA modem
2014-06-03T12:07:04.565672+00:00 linux dbus-daemon[1108]: modem-manager[1231]: <info>  (ttyACM0) closing serial port...
2014-06-03T12:07:04.565853+00:00 linux modem-manager[1231]: <warn>  Couldn't probe for capabilities, probably not a GSM or CDMA modem
2014-06-03T12:07:04.566049+00:00 linux modem-manager[1231]: <info>  (ttyACM0) closing serial port...
2014-06-03T12:07:04.566202+00:00 linux dbus-daemon[1108]: modem-manager[1231]: <info>  (ttyACM0) serial port closed
2014-06-03T12:07:04.566956+00:00 linux modem-manager[1231]: <info>  (ttyACM0) serial port closed
2014-06-03T12:07:04.566962+00:00 linux modem-manager[1231]: <info>  (ttyACM0) opening serial port...
2014-06-03T12:07:04.566964+00:00 linux dbus-daemon[1108]: modem-manager[1231]: <info>  (ttyACM0) opening serial port...
2014-06-03T12:07:08.584719+00:00 linux dbus-daemon[1108]: modem-manager[1231]: <warn>  Couldn't probe for capabilities, probably not a GSM or CDMA modem
2014-06-03T12:07:08.584976+00:00 linux dbus-daemon[1108]: modem-manager[1231]: <info>  (ttyACM0) closing serial port...
2014-06-03T12:07:08.585129+00:00 linux modem-manager[1231]: <warn>  Couldn't probe for capabilities, probably not a GSM or CDMA modem
2014-06-03T12:07:08.585318+00:00 linux modem-manager[1231]: <info>  (ttyACM0) closing serial port...
2014-06-03T12:07:08.585641+00:00 linux dbus-daemon[1108]: modem-manager[1231]: <info>  (ttyACM0) serial port closed
2014-06-03T12:07:08.585858+00:00 linux modem-manager[1231]: <info>  (ttyACM0) serial port closed
2014-06-03T12:07:18.564076+00:00 linux linux: Try 6/8 : /proc/fs/vmblock/dev not available. sleeping for 64 seconds
2014-06-03T12:07:32.113451+00:00 linux kernel:   269.030279] sd 5:0:0:0: [sdb] 15519744 512-byte logical blocks: (7.94 GB/7.40 GiB)
2014-06-03T12:07:32.113475+00:00 linux kernel:   269.030559] sd 5:0:0:0: [sdb] No Caching mode page present
2014-06-03T12:07:32.113479+00:00 linux kernel:   269.030563] sd 5:0:0:0: [sdb] Assuming drive cache: write through
2014-06-03T12:07:32.114423+00:00 linux kernel:   269.031266] sd 5:0:0:0: [sdb] No Caching mode page present
2014-06-03T12:07:32.114435+00:00 linux kernel:   269.031317] sd 5:0:0:0: [sdb] Assuming drive cache: write through
2014-06-03T12:07:32.117439+00:00 linux kernel:   269.034263]  sdb: sdb1

Hmmm… that might indicate a possible kernel regression at play perhaps. If you’re up to it, you might consider experimenting with kernel upgrades on the openSUSE 12.3 OS. There is a technique of bisecting kernels. I don’t have direct experience with this, although I understand the principles. Just to give you the basic idea

https://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
http://www.project-insanity.org/blog/2013/02/13/how-i-found-a-kernel-regression-using-git-bisect/

I tried to reproduce the problem in VirtualBox but there, having only USB-2 ports managed by ehci_hcd, oS 13.1 works as expected. So it seems it is something related to the kernel.
About trying bisect, there are two problems: first I have to install oS 12.3 on the laptop with oS 13.1 and there there is no free partition available. Moreover, I have no idea on how to compile and install the kernel in such a way I can still use the official one in case of problems…

You might want to start another thread if you want to pursue this task (kernel bisecting) further. That might help attract others who are experienced with this. Otherwise, sift through existing bug reports in the hope that it’s already been reported. To that end, it might be worth upgrading the kernel (in the hope that it’s already been fixed).

https://software.opensuse.org/package/kernel-desktop
*Show other versions > Show unstable packages

That’s about all I can offer

I tried with kernel-desktop-3.14.4 from the Kernel:Stable repo but with the same result.

Thanks anyway for the suggestions.

This is really strange: I was playing with Virtualbox trying to reproduce the issue, so I connected the phone via the usb cable and then attaching/detaching the device to the virtual machine (while keeping it physically connected).
If I do this, when I detach the device, then it works in the real system.
/var/log/messages contains the following lines, starting from the previous failed status as in the other logs:

2014-06-05T13:28:10.818116+08:00 caradhras kernel: [19469.157990] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2014-06-05T13:28:10.818124+08:00 caradhras kernel: [19469.157995] usb 3-2: Product: BCM21553-Thunderbird
2014-06-05T13:28:10.818128+08:00 caradhras kernel: [19469.157998] usb 3-2: Manufacturer: Broadcom
2014-06-05T13:28:10.818131+08:00 caradhras kernel: [19469.158001] usb 3-2: SerialNumber: 0123456789ABCDEF
2014-06-05T13:28:10.822011+08:00 caradhras kernel: [19469.162004] usb-storage 3-2:1.0: USB Mass Storage device detected
2014-06-05T13:28:10.822028+08:00 caradhras kernel: [19469.162092] scsi25 : usb-storage 3-2:1.0
2014-06-05T13:28:10.823006+08:00 caradhras kernel: [19469.162469] cdc_acm 3-2:1.1: This device cannot do calls on its own. It is not a modem.
2014-06-05T13:28:10.823022+08:00 caradhras kernel: [19469.162518] cdc_acm 3-2:1.1: ttyACM0: USB ACM device
2014-06-05T13:28:10.825240+08:00 caradhras mtp-probe: checking bus 3, device 14: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2"
2014-06-05T13:28:10.825900+08:00 caradhras mtp-probe: bus: 3, device: 14 was not an MTP device
2014-06-05T13:28:27.242009+08:00 caradhras kernel: [19485.599426] usb 3-2: usbfs: process 1486 (gvfs-gphoto2-vo) did not claim interface 0 before use
2014-06-05T13:28:27.682033+08:00 caradhras kernel: [19486.040491] usb 3-2: usbfs: process 1486 (gvfs-gphoto2-vo) did not claim interface 0 before use
2014-06-05T13:28:27.682069+08:00 caradhras kernel: [19486.040526] usb 3-2: usbfs: process 1486 (gvfs-gphoto2-vo) did not claim interface 0 before use
2014-06-05T13:28:34.488060+08:00 caradhras kernel: [19492.853463] usb 3-2: reset high-speed USB device number 14 using xhci_hcd
2014-06-05T13:28:34.500041+08:00 caradhras kernel: [19492.865275] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880128a7f880
2014-06-05T13:28:34.500085+08:00 caradhras kernel: [19492.865288] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880128a7f840
2014-06-05T13:28:34.500092+08:00 caradhras kernel: [19492.865296] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88013dedec80
2014-06-05T13:28:34.500097+08:00 caradhras kernel: [19492.865303] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88013dedec40
2014-06-05T13:28:34.500101+08:00 caradhras kernel: [19492.865310] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880151e298c0
2014-06-05T13:28:34.501017+08:00 caradhras kernel: [19492.866797] cdc_acm 3-2:1.1: This device cannot do calls on its own. It is not a modem.
2014-06-05T13:28:34.501039+08:00 caradhras kernel: [19492.866998] cdc_acm 3-2:1.1: ttyACM0: USB ACM device
2014-06-05T13:28:34.502021+08:00 caradhras kernel: [19492.867706] usb-storage 3-2:1.0: USB Mass Storage device detected
2014-06-05T13:28:34.505034+08:00 caradhras kernel: [19492.868558] scsi26 : usb-storage 3-2:1.0
2014-06-05T13:28:35.506060+08:00 caradhras kernel: [19493.873088] scsi 26:0:0:0: Direct-Access     SAMSUNG  S5830i Card      0000 PQ: 0 ANSI: 2
2014-06-05T13:28:35.507032+08:00 caradhras kernel: [19493.873672] sd 26:0:0:0: Attached scsi generic sg2 type 0
2014-06-05T13:28:35.509668+08:00 caradhras kernel: [19493.875222] sd 26:0:0:0: [sdb] Attached SCSI removable disk
2014-06-05T13:30:01.249637+08:00 caradhras /usr/sbin/cron[7869]: pam_unix(crond:session): session opened for user root by (uid=0)
2014-06-05T13:30:01.252847+08:00 caradhras systemd[1]: Starting Session 24 of user root.
2014-06-05T13:30:01.253447+08:00 caradhras systemd[1]: Started Session 24 of user root.
2014-06-05T13:30:01.274584+08:00 caradhras /USR/SBIN/CRON[7869]: pam_unix(crond:session): session closed for user root
2014-06-05T13:32:29.394029+08:00 caradhras kernel: [19728.017928] sd 26:0:0:0: [sdb] 15519744 512-byte logical blocks: (7.94 GB/7.40 GiB)
2014-06-05T13:32:29.395030+08:00 caradhras kernel: [19728.018549] sd 26:0:0:0: [sdb] No Caching mode page found
2014-06-05T13:32:29.395055+08:00 caradhras kernel: [19728.018560] sd 26:0:0:0: [sdb] Assuming drive cache: write through
2014-06-05T13:32:29.396041+08:00 caradhras kernel: [19728.019609] sd 26:0:0:0: [sdb] No Caching mode page found
2014-06-05T13:32:29.396062+08:00 caradhras kernel: [19728.019612] sd 26:0:0:0: [sdb] Assuming drive cache: write through
2014-06-05T13:32:29.398039+08:00 caradhras kernel: [19728.022007]  sdb: sdb1
2014-06-05T13:32:29.939744+08:00 caradhras udisksd[1197]: Mounted /dev/sdb1 at /run/media/ori/9016-4EF8 on behalf of uid 1000
2014-06-05T13:32:37.129372+08:00 caradhras udisksd[1197]: Cleaning up mount point /run/media/ori/9016-4EF8 (device 8:17 is not mounted)
2014-06-05T13:32:37.134521+08:00 caradhras udisksd[1197]: Unmounted /dev/sdb1 on behalf of uid 1000
2014-06-05T13:32:37.168017+08:00 caradhras kernel: [19735.800015] sdb: detected capacity change from 7946108928 to 0

Not sure whether this is the cause or just a trigger for the xhci_hcd module since if I stop virtualbox and I unload the relative kernl modules, disconnecting and connecting the usb cable does not work as usual.

So, it seems that a workaround is to use Virtualbox to steal the device and then return it to the real system.