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

[George Avrunin]

>>>>> On Mon, 27 Mar 2006 16:24:18 -0400, "BM" == Brian Mury <brianmury at alumni.uvic.ca> wrote:

  BM> I haven't seen any replies to my original post that dealt with
  BM> the new bug of the machine hanging when trying to sync my Palm
  BM> (message below for reference), but I've played with it a bit
  BM> more and characterized the behaviour a little better.
  BM> 
  BM> When pressing the hotsync button on the cradle, /dev/ttyUSB0 and
  BM> /dev/ttyUSB1 are created, and /dev/pilot is created as a soft
  BM> link to /dev/ttyUSB1 (BTW, shouldn't that be /dev/ttyUSB0?). The
  BM> hang happens when the palm exits sync mode - either when
  BM> completing communications with the computer, or by timing out,
  BM> or by cancelling the sync (via the cancel button on the Palm's
  BM> display).
  BM> 
  BM> I don't know if this is a problem with udev, or a problem with
  BM> the kernel, or a problem with something else, so I'm not sure
  BM> what to file a bug against. Any suggestions?
  BM> 

Do you see anything in /var/log/messages?  I have a problem with the
kernel claiming my Treo 90 lies about the number of ports, although it
creates ttyUSB0 and ttyUSB1 as it should.  When I tell jpilot to sync
(or start a pilot-xfer backup), there's a buffer overflow and the
jpilot (or pilot-xfer) is killed.  When I disconnect or reset the
Treo, there's a kernel bug reported in /var/log/messages saying "kernel BUG at
kernel/workqueue.c:109!".  The machine freezes for a couple of
minutes and when it comes back to life, I can't mount USB keys, etc.
So in my case, at least, it seems to be a kernel bug.  Your
description sounds similar.  Can you sync the Palm at all?

I filed a report
(https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=186712).  If
you're seeing something related, add yourself to that.  

  George