modem-manager tries to probe, crashes PalmOS handhelds and makes other serial devices unusable

[Matt Behrens]

These problems do not occur on my hardy system, nor do I recall them occurring on jaunty.

The visor module is required to communicate with PalmOS handhelds. Normally it sets up ttyUSB ports and enables communication via those ports with pilot-link, jpilot, etc. However, since karmic, connected PalmOS devices are crashing instead of communicating.

The LifeDrive will crash immediately on connection if the visor module is active, or will crash upon visor insertion if visor is not active when it is connected.

The CLIÉ I have access to (PEG-S320) will not crash until I cancel a HotSync operation. I attribute the difference between the two to the fact that the LifeDrive seems to always have a serial connection open.

For the LifeDrive, I have the following dmesg sequence:

(visor not active, LifeDrive connected)
[ 1466.748169] usb 1-3: new high speed USB device using ehci_hcd and address 9
[ 1466.881499] usb 1-3: configuration #1 chosen from 1 choice
(visor inserted)
[ 1471.671375] USB Serial support registered for Handspring Visor / Palm OS
[ 1471.672985] USB Serial support registered for Sony Clie 3.5
[ 1471.674030] USB Serial support registered for Sony Clie 5.0
[ 1471.678580] visor 1-3:1.0: Handspring Visor / Palm OS converter detected
[ 1471.679203] usb 1-3: Handspring Visor / Palm OS converter now attached to ttyUSB0
[ 1471.683173] usb 1-3: Handspring Visor / Palm OS converter now attached to ttyUSB1
[ 1471.683251] usbcore: registered new interface driver visor
[ 1471.683258] visor: USB HandSpring Visor / Palm OS driver
(LifeDrive crashes)
[ 1474.596135] usb 1-3: USB disconnect, address 9
[ 1474.597209] visor ttyUSB0: Handspring Visor / Palm OS converter now disconnected from ttyUSB0
[ 1474.597569] visor ttyUSB1: Handspring Visor / Palm OS converter now disconnected from ttyUSB1
[ 1474.597652] visor 1-3:1.0: device disconnected
[ 1475.264101] usb 3-1: new full speed USB device using uhci_hcd and address 11
[ 1475.388125] usb 3-1: device descriptor read/64, error -71
[ 1475.616123] usb 3-1: device descriptor read/64, error -71
[ 1475.832125] usb 3-1: new full speed USB device using uhci_hcd and address 12
[ 1475.956127] usb 3-1: device descriptor read/64, error -71
[ 1476.184114] usb 3-1: device descriptor read/64, error -71
[ 1476.400127] usb 3-1: new full speed USB device using uhci_hcd and address 13
[ 1476.808109] usb 3-1: device not accepting address 13, error -71
[ 1476.920131] usb 3-1: new full speed USB device using uhci_hcd and address 14
[ 1477.336069] usb 3-1: device not accepting address 14, error -71
[ 1477.336121] hub 3-0:1.0: unable to enumerate USB device on port 1

ProblemType: Bug
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: matt 3553 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 16'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,1043834a,00100004'
   Controls : 12
   Simple ctrls : 7
Date: Sun Aug 30 18:33:20 2009
DistroRelease: Ubuntu 9.10
MachineType: ASUSTeK Computer INC. 1000HE
Package: linux-image-2.6.31-8-generic 2.6.31-8.28
PccardctlIdent:

PccardctlStatus:

ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-8-generic root=UUID=564b6024-8d7a-4d50-8410-563167a8756a ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-8-generic N/A
 linux-firmware 1.16
RfKill:
 0: eeepc-wlan: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Tags: ubuntu-unr
Uname: Linux 2.6.31-8-generic i686
dmi.bios.date: 07/23/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1002
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1000HE
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.:bvr1002:bd07/23/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 1000HE
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

[Matt Behrens (zigg)]

Still occurs on 2.6.31-9-generic.

[Matt Behrens (zigg)]

Trying to narrow this down a bit using the LifeDrive, I've discovered that it does *not* crash in recovery mode.

I tried some lsmod and diff action to determine if the problem was related to some sort of module insertion that didn't happen in recovery mode, but I eventually modprobed every additional normally used module while in recovery mode and could not reproduce the crash.

Could this perhaps be triggered by some program running outside the kernel?

[sabsem (sabsem)]

Also crash Palm Treo 680 on 2.6.31-9-generic

[Matt Behrens (zigg)]

Based on some Web research, it seems that the "proper" way these days to use modern Palms with jpilot, pilot-link et al. is to set them to use the usb: device then let udev (?) link the two up, skipping the visor module entirely. I think I missed out on this because the visor module has always worked.

However, using usb: is not working either:

>> device connected
[ 1849.776124] usb 1-3: new high speed USB device using ehci_hcd and address 15
[ 1849.909491] usb 1-3: configuration #1 chosen from 1 choice
>> executed pilot-dlpsh -p usb: -i
[ 1972.557307] usb 1-3: USB disconnect, address 15
[ 1972.558349] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd pilot-dlpsh rqt 194 rq 4 len 20 ret -108
[ 1975.124129] usb 1-3: new high speed USB device using ehci_hcd and address 16
[ 1975.257385] usb 1-3: configuration #1 chosen from 1 choice

It doesn't crash the LifeDrive, though, so that's good ;)

I could use some guidance from someone who understands this more thoroughly in order to get this bug targeted properly. There are definitely two issues though, AFAIK:

1. the visor module has begun crashing Palms, and
2. the usb: method (which I understand gnome-pilot also uses?) is not working

[Matt Behrens (zigg)]

I left pilot-dlpsh running in the above test and am now seeing the following:

[ 2160.708243] INFO: task pilot-dlpsh:4663 blocked for more than 120 seconds.
[ 2160.708259] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 2160.708272] pilot-dlpsh D c0805380 0 4663 4426 0x00000004
[ 2160.708293] f2a55c88 00000086 f72014c0 c0805380 f29c0f28 c0805380 9a2ceb4b 000001cc
[ 2160.708322] c0805380 c0805380 f29c0f28 c0805380 9a1ba74b 000001cc c0805380 f292a1c0
[ 2160.708349] f29c0c90 f2a55d34 7fffffff f2a55d38 f2a55ce4 c0566eb5 f2a55cc0 c041f672
[ 2160.708376] Call Trace:
[ 2160.708404] [<c0566eb5>] schedule_timeout+0x185/0x200
[ 2160.708423] [<c041f672>] ? submit_async+0x82/0xf0
[ 2160.708440] [<c041feef>] ? ehci_urb_enqueue+0x7f/0xf0
[ 2160.708467] [<c0566bd2>] wait_for_common+0xa2/0x120
[ 2160.708478] [<c0137c70>] ? default_wake_function+0x0/0x10
[ 2160.708486] [<c0566ccd>] wait_for_completion_timeout+0xd/0x10
[ 2160.708496] [<c040be1c>] usb_start_wait_urb+0x5c/0xb0
[ 2160.708504] [<c040c160>] usb_control_msg+0xc0/0x120
[ 2160.708513] [<c0124508>] ? default_spin_lock_flags+0x8/0x10
[ 2160.708521] [<c0412f7c>] proc_control+0x1ac/0x420
[ 2160.708529] [<c0414282>] ? proc_ioctl+0x122/0x1d0
[ 2160.708537] [<c0414dfc>] usbdev_ioctl+0x63c/0xa10
[ 2160.708546] [<c040e107>] ? usb_autopm_do_device+0x67/0xf0
[ 2160.708554] [<c0105500>] ? show_interrupts+0x160/0x2a0
[ 2160.708562] [<c05688a7>] ? unlock_kernel+0x27/0x30
[ 2160.708570] [<c0414610>] ? usbdev_open+0x80/0x230
[ 2160.708577] [<c04123e0>] ? match_devt+0x0/0x20
[ 2160.708584] [<c0568698>] ? _spin_lock+0x8/0x10
[ 2160.708593] [<c01d7a1a>] ? shmem_get_acl+0x3a/0x70
[ 2160.708602] [<c01e5b2d>] ? chrdev_open+0xcd/0x190
[ 2160.708611] [<c01e0da7>] ? __dentry_open+0x187/0x230
[ 2160.708619] [<c01e0f35>] ? nameidata_to_filp+0x55/0x70
[ 2160.708626] [<c01e5a60>] ? chrdev_open+0x0/0x190
[ 2160.708634] [<c01eea3a>] ? do_filp_open+0x53a/0x890
[ 2160.708642] [<c0124508>] ? default_spin_lock_flags+0x8/0x10
[ 2160.708650] [<c01f0233>] vfs_ioctl+0x73/0x90
[ 2160.708658] [<c0105500>] ? show_interrupts+0x160/0x2a0
[ 2160.708666] [<c01f0501>] do_vfs_ioctl+0x71/0x310
[ 2160.708673] [<c01f07ff>] sys_ioctl+0x5f/0x80
[ 2160.708680] [<c01e0bd9>] ? sys_open+0x29/0x40
[ 2160.708688] [<c010334c>] syscall_call+0x7/0xb
[ 2160.708695] [<c0105500>] ? show_interrupts+0x160/0x2a0

and it won't die.

[Matt Behrens (zigg)]

I managed to kill it by turning the LifeDrive back on (it had gone to sleep) and initiating a HotSync, which did not work. I had previously sent several -9 signals to it, so I assume those made it through once it was apparently freed up.

(Sorry for the comment spam; it seems I keep getting new possibly-useful bits of info. I am done for now.)

[Matt Behrens (zigg)]

I finally nailed this one down by comparing loaded processes between recovery mode and normal boot. It turns out that modem-manager tries to probe the Palm when it allocates its USB ports.

My workaround is to remove the modemmanager package and kill instances of modem-manager (I am not sure how to stop it from spawning.) You probably lose mobile broadband support in this case.

modem-manager needs to be taught how to not probe Palm devices, I think.

[Alexander Sack (asac)]

are you saying you are running modem-manager on that Palm device somehow or that connecting the palm to a system that has modemmanager running crashes the palm because we send AT commands there? Can you please clarify.

[Matt Behrens (zigg)]

That appears to be the case, yes. I don't have the output handy, and would have to reinstall the package to capture it, but while in recovery mode, I connected my LifeDrive, the visor module allocated ttyUSB0 and ttyUSB1 to it, verified the LifeDrive was operating properly. I then ran modem-manager by hand, and its output indicated it was probing said ttys, at which point the LifeDrive crashed and rebooted.

So yes, I imagine sending the AT commands is what is crashing the LifeDrive.

By the way, if it's helpful, you can find a listing of USB device IDs for Palms in /lib/udev/rules.d/40-libpisock9.rules.

[Alexander Sack (asac)]

can you try to connect with minicom against the tty (before that run : "sudo stop network-manager" and "sudo killall modem-manager). and send some AT commands ... like: ATZ, AT+CPIN?, AT+CFUN? etc. and see if that causes your palm device to go down too?

[Matt Behrens (zigg)]

Man, it's been ages since I've used minicom. :)

I cleared the init and reset strings from the config first, left all other settings at default. In turn, I tested both ttyUSB0 (which is the HotSync port) and ttyUSB1. I believe the latter is used for serial applications... it might possibly not be open unless an app on the Palm opens it? I am not really sure.

ttyUSB0: nothing happened. I typed each of the commands you listed above. Nothing echoed, the LifeDrive didn't blink.

ttyUSB1: opening minicom did nothing, but the first stroke of "A" crashed the Palm.

[cliffb (cbailey)]

I am having the same problem with a Treo 755. Plugging it in to the USB port causes the Treo to reset. "stopping" the network-manager and then killing the modem-manager process fixed the problem. Restarting the network-manager immediately crashed the Treo.

The ID for the Treo (as a phone - not a modem) is: 0830:0061

The ID for the Treo (as a modem) is: 0830:127d

Might it be possible to have the modem-manager see the phone-as-a-modem only when the ID is 0830:127d. Or maybe there is already a way to do that? Inquiring minds want to know.

Thanks, Cliff

[Onno (o-schuit)]

I appear to have the same problem for the Palm Treo 650. The phone crashes when I press the sync button (while connected to my Ubuntu 9.10 box through USB).

Removing the modemmanager package (through System > Administration > Synaptic Package Manager) solves the problem.

Thanks Matt!

Onno

[Jamie Jackson (jamiejackson)]

Same issue with a Visor Neo. "apt-get remove modemmanager" works around the problem for me, too.

Thanks for the report and the research/workaround, Matt.

[ronny (ronny-standtke)]

I just updated to Kubuntu-9.10 and can confirm this issue. My Palm Treo is now crashing instead of syncing with KPilot...

[ronny (ronny-standtke)]

I can also confirm that removing modemmanager works around the crashing problem. Unfortunately, KPilot still does not like to sync with the Treo. But this is another issue.

[James E. LaBarre (jamesl-bestweb)]

I am having the same issues with a Sony Clie PEG-SJ22. Removing "modemmanager" didn't fix the issue. Still crashes or locks up the Clie during hot-sync.

[cliffb (cbailey)]

My way around this is not elegant, but it works. Before plugging in the sync cable I "stop" the network-manager. I found that necessary as the network-manager respawns the modem-manager. Then I kill the modem-manager process, do the sync and then "start" the network-manager again. When I use the phone as a modem I do the above, start the modem program on the phone and then plug in the sync cable and restart the network-manager - connects every time. Like I said, not elegant, but it works.

[cecst (v-launchpad-net-cecst-com)]

I can also confirm that removing modemmanager works around the crashing problem on Palm TX. So did
stopping network-manager and then killing modem-manager on a second machine.

[Don Cristóbal (doncristobal)]

I confirm this on Xubuntu 9.10 and Palm TX (Palm OS Garnet v. 5.4.9). Uninstalling modem-manager and stopping network-manager helps only partially: The Palm does not crash immediately any more, but it does crash when trying to install files using gpilot-install-file - and in the meantime the gpilotd process eats 100% cpu, so I have to kill it

[Andrew Ross (cargoflyer)]

You guys rock! Confirmed...Uninstalled modemmanager via Package mgr and my Treo 755p quit rebooting, and all looks good in Evolution calendar, address, & memos. Per other instructions, I did put visor in modules, and a couple other things. However, nothing worked until I uninstalled modemmanager. I hope this does not affect any other functionality. Thanks!

[Brock Riedell (kbrcbc)]

Confirmed for me also - syncing a Treo 650 to J-Pilot using the visor module. No problem across several Ubuntu versions, but the Karmic upgrade suddenly broke syncing, resetting the device every time just as others have described. I uninstalled modemmanager, rebooted, and am now syncing without problems. Thanks Matt for the workaround.

[Elrohir (elrohir)]

Confirm, too, on Kubuntu. I use a Treo680. Since Karmic it crashed constantly while attached to usb port. Uninstalling modemmanager and rebooting fixed the problem. Thank god! That would have been a major problem to me! Thanks a lot!

[BrettJGladman (bjgladman)]

Using a Treo 650 on 9.10 64-bit. I also had crashing upon hitting hotsync on the Treo. Using
synaptic to uninstall modemmanger resolved the problem and I can now sync with jpilot (must
hit hotsync in jpilot first, then on Treo). [Had to reboot after modemmanager uninstall.]
The only problem is that something seems to have removed the categories on my address
book, but I am unsure if that is jpilot or one of the other attempt I made earlier.
Thanks a lot for this help.

[jkohler2 (jkohler2)]

Neither of my 2 usb 56k modems, Zoom or U.S. Robotics, would respond to
sudo gnome-ppp, under Ubuntu 9.10 in contrast to Ubuntu 9.04 which
worked perfectly.

      Bug #469881 in Ubuntu: “gnome-ppp fails under 9.10, works under 9.04”

A temporary workaround was suggested:

sudo apt-get remove modemmanager

After rebooting my laptop, sudo gnome-ppp works fine.

There must be an error in modem manager

[Marc Deslauriers (mdeslaur)]

For 56k modems, see Bug #496206.

[Matt Behrens (zigg)]

Still a problem in 0.2.git.20091014t233208.16f3e00-0ubuntu1 on lucid.

Still work-aroundable by apt-get purge modemmanager; sudo killall modem-manager.

[Torsten Spindler (tspindler)]

I have a similar problem with a SmartCard reader, which also becomes unavailable after being probed by modemmanager.

[Dominik (domfi)]

Just as a very dirty hack: try to remove (rename) /usr/lib/ModemManager/libmm-plugin-generic.so. This disables probing on generic serial devices and still let internal UMTS Modems (like from sierra, etc) work like expected. At least it works for me until modemmanager is fixed.

[Dominik (domfi)]

This issue exists since August 2009: Has anybody opened a bug-report in the upstream project yet?

At least I don't find one on Gnome-Bugzilla.
Strange...

To hopefully get this problem solved I will open one and link this Bug to it.

As far as I see:

The culprit is the ModemManager. It probes all serial devices for attached
modems. These probes irritate some serial devices. For us these are:

  * Palm OS Handheld
  * PCMCIA Smartcard-Reader

but there might be other devices which don't like ModemManager fiddle about with there interface.

[Dominik (domfi)]

Opened: https://bugzilla.gnome.org/show_bug.cgi?id=608022

[jaf0 (jaf0)]

Treo 700p here. any additional information you need for this specific device?

USB ID is Bus 001 Device 004: ID 0830:1279 Palm, Inc.

[jaf0 (jaf0)]

I guess the rest of the information is as follows.

Currently on a Hard Reset (Clean device), it modprobes properly and sets up the ttyUSB0 and ttyUSB1
Feb 3 01:50:31 t30 kernel: [ 4065.572956] usbcore: registered new interface driver usbserial
Feb 3 01:50:31 t30 kernel: [ 4065.572999] USB Serial support registered for generic
Feb 3 01:50:31 t30 kernel: [ 4065.573071] usbcore: registered new interface driver usbserial_generic
Feb 3 01:50:31 t30 kernel: [ 4065.573078] usbserial: USB Serial Driver core
Feb 3 01:50:31 t30 kernel: [ 4065.613866] USB Serial support registered for Handspring Visor / Palm OS
Feb 3 01:50:31 t30 kernel: [ 4065.613907] USB Serial support registered for Sony Clie 3.5
Feb 3 01:50:31 t30 kernel: [ 4065.613944] USB Serial support registered for Sony Clie 5.0
Feb 3 01:50:31 t30 kernel: [ 4065.614012] usbcore: registered new interface driver visor
Feb 3 01:50:31 t30 kernel: [ 4065.614018] visor: USB HandSpring Visor / Palm OS driver
Feb 3 01:50:53 t30 kernel: [ 4087.802648] usb 1-1.4: USB disconnect, address 18

as soon as i disconnect the cable, the 700p crashes/reboots.

f/u to post #33 the USB device ID is for modem.

[Dominik (domfi)]

Hello jaf0,

there's a tool "lsudev" in the ModemManager-Sources. Is it possible to run this tool while your treo is visible? You have to stop Modemmanager/Networkmanager before this! As far as I understood, this command delivers all information needed by the
NetworkManager Developers. If you attach the output here I will update the Upstream Bugzilla.

Regards
Dominik

[Dominik (domfi)]

By the way: Is it possible to set a "Bug watcher" to the corresponding ticket in Gnome-Bugzilla?

[Dominik (domfi)]

Sorry: correct Question is: Why are the Updates of the Upstream Tickets not shown here in Launchpad? The Bugwatcher is already active as I see?

[jaf0 (jaf0)]

dominik: lsdev or lsudev?

[jaf0 (jaf0)]

nvm, i found a coupla versions...gonna run 'em here in a few.

[Dominik (domfi)]

jaf0: Sorry: The program is in the source code from ModemManager (in directory test/ ) not NetworkManager.
It's called lsudev. You have to build it on your own. It is not included in the deb.

[Dominik (domfi)]

I run "lsudev tty" for my smartcard-reader. The command does not exit, you have to abort it with Ctrl-c.

[jaf0 (jaf0)]

here's the lsudev.c that I used...

[jaf0 (jaf0)]

and here's a tar file of the various outputs ...

both for 700p as visor
and 700p as USBModem

root@t30:/usr/src/lsudev# tar -tvf output.tar
-rw-r--r-- root/src 10240 2010-02-04 16:39 lsudev.MobilestreamUSBModem.treo700p.out.gz
-rw-r--r-- root/src 4114 2010-02-04 15:36 lsudev.treo700p.out.gz
-rw-r--r-- root/src 210 2010-02-04 16:36 lsusb.MobilestreamUSBModem.treo700p.out.gz
-rw-r--r-- root/src 235 2010-02-04 15:47 lsusb.treo700p.out.gz

[Dominik (domfi)]

Thank you. I've attached it to the Gnome-Bugzilla.

[Don Cristóbal (doncristobal)]

I'd be glad to post my lsudev output, but I'll need some help...
* I've not found any lsudev file in /usr/src/modemmanager-0.2.git.20091014t233208.16f3e00/ (which I got by $ sudo apt-get source modemmanager).
* I can't run jaf0's lsudev.c.gz file (I made it executable 755 and said "./lsudev", but bash complains: "./lsudev.c: cannot execute binary file") - do I have to compile that first? How? Is there a compiled version I can download for (X)Ubuntu Karmic?

[jaf0 (jaf0)]

ok. i'm attaching a compiled version. md5sum of ungzipped file is ...

3c8dc47c248827124e8e11ae314a6559

compiled on Karmic (gcc (Ubuntu 4.4.1-4ubuntu9) 4.4.1)

[Don Cristóbal (doncristobal)]

Thank you, jaf0. Let's see if my output is the one you need. I said
$ ./lsudev tty (because someone mentioned that earlier)
and
$ ./lsudev usb (because my Palm TX uses a usb cable)

But honestly, I don't understand anything :-)

[Dominik (domfi)]

Christoph: Did you press the Sync-Button on you Palm TX before you ran lsudev? As far as I can see there's no ttyUSB*
in your output. The device is only visible if it is in "Sync-mode".

[jaf0 (jaf0)]

Dom:

As soon as I connected my 700p, modprobe loaded up the visor module....

perhaps he did not connect the device?

or didn't remove modem-manager.?

jaf0

[Dominik (domfi)]

For my old Tungsten T3 I had to start the hotsync to make the devices (ttyUSB0 / ttyUSB1) visible on my pc. I'll have a look at this again (if I find it somewhere... ).

[Ed Comer (celem)]

I use jpilot ver 1.6.2.4 on ubu9.10 amd64. I worked perfectly with ubu9.04, reliably syncing via usb: each and every time. When I upgraded to 9.10 it didn't work, crashing my Sony Clie PEG-SJ22/U, as described by others, above. When I removed the modemmanager package it still would not sync to usb:. I added the visor module back in to try /dev/pilot. This works but unreliably, meaning that it won't sync each and every time. I haven't figured why it syncs sometimes but not others. Personally, I would really like for it to work as it did with 9.04, namely without the visor module and syncing reliably to usb:

[nUboon2Age (nuboon2age)]

PROBLEM: with Lucid and a Palm 700p with a USB cradle using the visor module if I pressed the hotsync button the palm would be continously reseting indefinitely (had to unplug). The key to fixing this problem seemed to be purging modemmanager. I also removed the visor module.

FIX: Hotsync successfully with:
PDA: Palm 700p
Connection: USB cable connector
Remove: modemmanager completely purged.
Remove module: visor
Software: gnome-pilot
gnome-pilot Settings:
PDA id: 2001 (changed from default value which was 1000)
Name: Cradle (default)
Type: USB
Timeout: 2 (default)
Device: usb:
Speed: 115200 (default was 57600)

[nUboon2Age (nuboon2age)]

Also I was getting the same kind of dmesg entries as the original bug report when undergoing these continous resets:
such as:
  visor 1-3:1.0: Handspring Visor / Palm OS converter detected
  usb 1-3: Handspring Visor / Palm OS converter now attached to ttyUSB0

Followed shortly thereafter by:
  visor ttyUSB0: Handspring Visor / Palm OS converter now disconnected

[Matt Behrens (zigg)]

Looking at GNOME Bugzilla, it seems modem-manager has a blacklist that includes Palm devices (the lsusb log someone posted matches my LifeDrive.) Has anyone tested maverick with this yet? Wondering if it made it in.

[Bohdan Kmit' (mit)]

My Treo 680 stop crashing after upgrade to Kubuntu 10.10

[P (p92)]

it still crashed on kubuntu 10.10

I have removed modem-manager and killed it.

I connect the treo650 and press hotsync
the devices appear on the syslog :
Nov 18 17:01:48 minipc kernel: [19690.570042] usb 6-1: new full speed USB device using uhci_hcd and address 11
Nov 18 17:01:48 minipc kernel: [19690.751559] visor 6-1:1.0: Handspring Visor / Palm OS converter detected
Nov 18 17:01:48 minipc kernel: [19690.751684] usb 6-1: Handspring Visor / Palm OS converter now attached to ttyUSB0
Nov 18 17:01:48 minipc kernel: [19690.751766] usb 6-1: Handspring Visor / Palm OS converter now attached to ttyUSB1

I then start
pilot-debugsh /dev/ttyUSB0

as soon as I enter the command menu for example ===> treo650 reboots !

Nov 18 17:02:23 minipc kernel: [19725.790065] usb 6-1: USB disconnect, address 11
Nov 18 17:02:23 minipc kernel: [19725.790233] visor ttyUSB0: Handspring Visor / Palm OS converter now disconnected from ttyUSB0
Nov 18 17:02:23 minipc kernel: [19725.790285] visor ttyUSB1: Handspring Visor / Palm OS converter now disconnected from ttyUSB1
Nov 18 17:02:23 minipc kernel: [19725.790294] visor 6-1:1.0: device disconnected

So this problem is still not solved.

[P (p92)]

Please look at https://help.ubuntu.com/community/PalmDeviceSetup for a solution. You must not use visor module anymore as it conflicts with new libusb method.

[Matt Behrens (zigg)]

@PascalCavy: unfortunately, libusb (a.k.a. PILOTPORT=usb:) is not an option for all devices. I did just try it again, and was not able to start a sync. LifeDrive in particular was unsupported in libusb mode by pilot-link a few years ago, and I believe other Palms had similar issues:

http://lists.pilot-link.org/pipermail/pilot-link-general/2008-May/003364.html

Given your experience, and the fact that modemmanager is no longer crashing my LifeDrive on maverick, maybe libusb devices may still present an issue if the visor module is inserted?

[P (p92)]

My device is a Palm Treo650 and as suggested in the ubuntu forum I had to remove visor module in order to be able to sync the device using jpilot.

[Matt Behrens (zigg)]

Yeah, I don't know which devices do and don't work offhand, but I do know for a fact (again, I double-checked this, in case things had changed since I last tried it back when I opened this bug originally) that the LifeDrive *requires* the visor module. It's just a matter of which Palm devices the libusb code supports.

[Mathieu Trudel-Lapierre (cyphermox)]

These changes have been included since Maverick; marking as Fix Released.

This is not to say that there can't be issues: this bug was about blacklisting devices. There are tons of new devices released every day. If you find that your device isn't properly being ignored by ModemManager, please file a separate bug and include the USB ID so we can add it to the blacklisted devices.

Thanks!