Bug 106496 - Machine Freezes when syncing Handspring Visor
Machine Freezes when syncing Handspring Visor
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Dave Jones
Brian Brock
Depends On:
Blocks: CambridgeTarget
  Show dependency treegraph
Reported: 2003-10-07 16:05 EDT by Paul Eden
Modified: 2015-01-04 17:03 EST (History)
1 user (show)

See Also:
Fixed In Version: kernel-2.4.22-1.2088.nptl
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-11-03 08:24:59 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Paul Eden 2003-10-07 16:05:38 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.1; Linux)

Description of problem:
When syncing they system freezes.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Setup syncing with gpilotd-control-applet to /dev/ttyUSB1
2. Place the visor in the cradle and plug in the usb cord.
3. Press the sync button on the cradle.
4. System freezes

Actual Results:  The whole system freezes.  The keyboard and mouse do not work anymore.  The caps lock and scroll lock leds blink.  The only remedy is to press the reset or power button.

Expected Results:  The palm should sync with the PIM software (in my case evolution 1.4)

Additional info:

I am running these programs:
Comment 1 Dave Jones 2003-10-08 22:01:08 EDT
The caps lock and scroll lock leds blinking means you got a kernel panic.
If you switch to tty1 (ctrl-alt-f1) before you press the sync button on the
cradle, you should see a backtrace hopefully.
Comment 2 Dave Jones 2003-10-21 21:24:10 EDT
A possible fix for this is going to be in tomorrows rawhide push. Please test.
Comment 3 Paul Eden 2003-11-03 08:24:59 EST
After an update to the code from Fedora Core Test release 3 this
behavior has ended.  I am able to sync correctly.
Comment 4 Paul Eden 2003-11-03 08:28:22 EST
These are the versions of the other programs involved in which the bug
is not appearing:

Note You need to log in before you can comment on or make changes to this bug.