FC5: gnome-pilot AND pilot-link broken (worse than FC4!)

[George Avrunin]

I have a 3-year-old Treo 90 (only a PDA, not a phone) that, at least
after I got the udev rules straightened out, worked fine with FC 4.
(At least with jpilot/pilot-link; I've never used gnome-pilot.)
It doesn't work with FC 5, and exposes a kernel bug.

On a fully-updated fresh install of FC 5, when I plug in the Treo USB
cable and press the sync button, I get the following in
/var/log/messages:
--------------------------------------------------
Mar 26 20:28:06 g2 kernel: usb 3-2: new full speed USB device using uhci_hcd and address 3
Mar 26 20:28:07 g2 kernel: usb 3-2: configuration #1 chosen from 1 choice
Mar 26 20:28:07 g2 kernel: usbcore: registered new driver usbserial
Mar 26 20:28:07 g2 kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
Mar 26 20:28:07 g2 kernel: usbcore: registered new driver usbserial_generic
Mar 26 20:28:07 g2 kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core
Mar 26 20:28:07 g2 kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Handspring Visor / Palm OS
Mar 26 20:28:07 g2 kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 3.5
Mar 26 20:28:07 g2 kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 5.0
Mar 26 20:28:07 g2 kernel: visor 3-2:1.0: Handspring Visor / Palm OS converter detected
Mar 26 20:28:07 g2 kernel: usb 3-2: Handspring Visor / Palm OS converter now attached to ttyUSB0
Mar 26 20:28:07 g2 kernel: usb 3-2: Handspring Visor / Palm OS converter now attached to ttyUSB1
Mar 26 20:28:07 g2 kernel: usbcore: registered new driver visor
Mar 26 20:28:07 g2 kernel: drivers/usb/serial/visor.c: USB HandSpring Visor / Palm OS driver
Mar 26 20:28:07 g2 kernel: visor ttyUSB0: Device lied about number of ports, please use a lower one.
--------------------------------------------------

I am, of course, unable to sync.  The Treo just sits there, waiting
for the sync.  When I try to sync with pilot-xfer or jpilot, I get a
complaint that buffer overflow was detected in the application and
pilot-xfer or jpilot is killed.  When I unplug the cable or reset the
Treo, I get a kernel bug:

--------------------------------------------------
Mar 26 20:41:35 g2 kernel: usb 3-2: USB disconnect, address 3
Mar 26 20:41:35 g2 kernel: ------------[ cut here ]------------
Mar 26 20:41:35 g2 kernel: kernel BUG at kernel/workqueue.c:109!
Mar 26 20:41:35 g2 kernel: invalid opcode: 0000 [#1]
Mar 26 20:41:35 g2 kernel: last sysfs file: /class/tty/ttyUSB1/dev
Mar 26 20:41:35 g2 kernel: Modules linked in: visor usbserial vfat fat sd_mod sg usb_storage scsi_mod radeon drm ppdev autofs4 sunrpc ip_conntrack_netbios_ns ipt_REJECT xt_state ip_conntrack nfnetlink xt_tcpudp iptable_filter ip_tables x_tables dm_mirror dm_mod video button battery ac ipv6 lp parport_pc parport usblp floppy nvram ehci_hcd uhci_hcd natsemi e1000 snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm i2c_i801 i2c_core hw_random snd_timer snd soundcore snd_page_alloc ext3 jbd
Mar 26 20:41:35 g2 kernel: CPU:    0
Mar 26 20:41:35 g2 kernel: EIP:    0060:[<c012755f>]    Not tainted VLI
Mar 26 20:41:35 g2 kernel: EFLAGS: 00010217   (2.6.15-1.2054_FC5 #1)
Mar 26 20:41:35 g2 kernel: EIP is at queue_work+0x17/0x2f
Mar 26 20:41:35 g2 kernel: eax: e599698c   ebx: c18e88a0   ecx: 00000000   edx:
e5996988
Mar 26 20:41:35 g2 kernel: esi: e5d36440   edi: e981ce14   ebp: e981ce14   esp:
f7f69ec0
Mar 26 20:41:35 g2 kernel: ds: 007b   es: 007b   ss: 0068
Mar 26 20:41:35 g2 kernel: Process khubd (pid: 78, threadinfo=f7f69000 task=f7f6c000)
Mar 26 20:41:35 g2 kernel: Stack: <0>00000000 f8d1e77e e981ce00 f8d0dc00 f8d0dc34 c025df49 e981cebc e981ce14
Mar 26 20:41:35 g2 kernel:        c02254a0 e981ce14 00000000 c0360e40 c02256cd e981ce14 c0224e88 e981ce14
Mar 26 20:41:35 g2 kernel:        e8da8458 00000000 c0224342 e981ce00 e8da8400 c025c7ad e8da8400 e8da86d4
Mar 26 20:41:35 g2 kernel: Call Trace:
Mar 26 20:41:35 g2 kernel:  [<f8d1e77e>] usb_serial_disconnect+0x54/0x94 [usbserial]     [<c025df49>] usb_unbind_interface+0x34/0x6a
Mar 26 20:41:35 g2 kernel:  [<c02254a0>] __device_release_driver+0x5c/0x74     [<c02256cd>] device_release_driver+0x2a/0x38
Mar 26 20:41:35 g2 kernel:  [<c0224e88>] bus_remove_device+0x6d/0x7f     [<c0224342>] device_del+0x38/0x68
Mar 26 20:41:35 g2 kernel:  [<c025c7ad>] usb_disable_device+0x68/0xc9     [<c0259376>] usb_disconnect+0x8d/0xe6
Mar 26 20:41:35 g2 kernel:  [<c0259aa3>] hub_thread+0x336/0x9e5     [<c012a17b>] autoremove_wake_function+0x0/0x2d
Mar 26 20:41:35 g2 kernel:  [<c025976d>] hub_thread+0x0/0x9e5     [<c012a09b>] kthread+0x91/0xbd
Mar 26 20:41:35 g2 kernel:  [<c012a00a>] kthread+0x0/0xbd     [<c0101005>] kernel_thread_helper+0x5/0xb
Mar 26 20:41:35 g2 kernel: Code: fa 89 d8 5b 5e 5f e9 08 51 1b 00 8b 48 14 89 c2 8b 01 eb ae 53 89 c3 0f ba 2a 00 19 c0 31 c9 85 c0 75 1c 8d 42 04 39 42 04 74 08 <0f> 0b 6d 00 93 96 2f c0 8b 03 e8 88 ff ff ff b9 01 00 00 00 89
Mar 26 20:41:35 g2 kernel: Continuing in 120 seconds. ^MContinuing in
119 seconds. ^MContinuing in 118 seconds. ^MContinuing in 117
seconds. ^MContinuing in 116 seconds. ^MContinuing in 115
seconds. ^MContinuing in 114 seconds. ^MContinuing in 113
seconds. ^MContinuing in 112 seconds. ^MContinuing in 111
seconds. ^MContinuing in 110 seconds. ^MContinuing in 109
seconds. ^MContinuing in 108 seconds. ^MContinuing in 107
seconds. ^MContinuing in 106 seconds. ^M, 
[snipped]
--------------------------------------------------
etc.

The system freezes until after the 2 minutes of "Continuing in ...",
and after the freeze at least some USB stuff doesn't work (e.g., I
can't mount a USB memory key).

I've filed a bug report on this
(https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=186712), but
I'd certainly appreciate any suggestions for workarounds anyone might
have in the meantime.

Thanks,

  George