Description of problem: Error when connecting a visor device: Bad EIP value. The /dev/ttyUSB? stay after deconnecting the device. Version-Release number of selected component (if applicable): kernel 2.6.9-1.678_FC3 All ok with 2.6.9-1.667 How reproducible: every time. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 107041 [details] syslog extract
*** Bug 140166 has been marked as a duplicate of this bug. ***
The only issue I have with marking the other as a duplicate is that this bug, 140005, is specifically noted to be FC3, while 140166 was marked for FC2. I just want to make sure that it'll be looked at for both releases. Thanks.
the two trees are in sync with each other (and are 99.9% the same tree), so if its fixed in one, the other will be fixed at the same time.
*** Bug 139823 has been marked as a duplicate of this bug. ***
*** Bug 140193 has been marked as a duplicate of this bug. ***
*** Bug 140269 has been marked as a duplicate of this bug. ***
*** Bug 140303 has been marked as a duplicate of this bug. ***
Created attachment 107253 [details] log messages from failed hotsync attempt Okay, with kernel-2.6.9-1.6_FC2 I no longer get the "Unable to handle kernel NULL pointer dereference at virtual address 00000000" error that I was getting with kernel-2.6.9-1.3_FC2. But I still can't successfully sync my Palm m505. The sync starts, but disconnects after a few seconds. (See the log messages.) There's nothing in 2.6.9 that I particularly need, so I'm dropping back to kernel-2.6.8-1.521 for now.
Marginal improvement on FC3 with the 2.6.9-1.681_FC3 kernel. The sync appears to start fine, but JPilot hangs at "Syncing AddressDB" while the PDA tries to go further to saving the ToDo. At least now the kernel does not oops, but the sync fails nevertheless.
Oddly 2.6.9-1.681_FC3 seems to remove other kernels... After 2.6.9-1.681_FC3 installation same behaviour as in comments #9 and #10. Back to 667: rpm -ivh --force kernel-2.6.9-1.667.i686.rpm reboot Sync hangs and a new message appears: kernel: usb 4-2: control timeout on ep0in Oops: rpm -ivh --force kernel-utils-2.4-13.1.39.i386.rpm All working fine. Watching for some difference between kernel configs..., but no results at the moment...
I see exactly the same as Florin Andrei above using 2.6.9-1.861_FC3 but using kpilot, not jpilot, suggesting a kernel bug rather than a bug in either program. The Oops I was seeing has gone away, but I still can't sync.
Confirm 2.6.9-1.681_FC3 removes Oops. Something seems to have changed in that the permissions on the ttyUSB* devices are such that they are no longer accessible to me - I see a udev update in the right sort of timescale to affect this. Trying a pilot-xfer -L as root gets the first part of the installed databases list, but hangs part way through. No error message regarding this is seen in the kernel log or elsewhere except the palm device timing out after a minute. Not seeing USB timeout messages.
Confirmed that I am seeing this problem as well, FC3, kernel 2.6.9-1.681_FC3, USB connected Visor. Hardware is detected via USB, visor module loads, /dev/ttyUSB* and /dev/pilot are created correctly (and owned corrrectly), the gpilot-applet executes, but the Visor never leaves the "Identifying user" stage. The gpilot-applet never reaches the stage where it exchanges data visibly, although the progress indicator does continue to run, even after the Visor has issued its own error and a USB disconnect happens.
This bug and my bug (140125) seem to be duplicates as well. They were both opened within hours of each other and both are assigned to Dave Jones. Should we close on of them as a dup?
This bug is also reproducible on FC2 using the kernel 2.6.9-6 (FC2). I'm using a Zire 31 and I am syncing it with MultiSync. Bug is also reproducible in pilot-link command line tools. Trying 'dlpsh' and doing an 'ls' command, the listing of palm dbs would halt after listing a few of them.
This bug is fixed with latest kernel in updates-testing for me, using a palm M125, modules visor + usbserial. Working kernel: kernel-smp-2.6.9-1.698_FC3.i686.rpm Thanks!
Confirmed also working for me with that kernel (698), see comment in chrisw's bug #140125
Confirmed also working for me with kernel 2.6.9-1.698_FC3.
Would someone please make a testing kernel available in the http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/2/i386/ directory, so those of us still at FC2 can test, as well?
I'm adding my 2 cents to this. I'm experienceing the same problem as you all. I started having problems with my windows computer at work (win 2k) and then tried to sync at home on my Linux pc and it failed to sync in both places. I thought it was a clie problem, so I've just went through sony support, and was ready to return the device, when after lots of googling I came across this bug. :-O I guess between my last sync on my linux box I had upgraded to 2.6.9 from 2.6.8, and did not test the pda, but tested the pwc phillips driver ;-). I just downgraded to 2.6.8 tonight after reading this ( actually I have both kernels custom built on the box ) and 2.6.8 works awesome, but 2.6.9-1.6_FC2custom does not work at all. It does exactly the same behavior, dlpsh ls fails to list the files, pilot-xfer exhibits the same behavior. I just found the link to the updates, so I'll download that and test it out too, because I want to use 2.6.9 with the pwc driver and the visor driver fixes ( not tonight though). When will this new kernel be in the main FC 2 tree also? Thanks lots! Joe
I just installed and compiled kernel-sourcecode-2.6.9-1.9_FC2 from the testing ftp link above. The pilot-link ( sony clie ) ( and pwc driver ) work great! Just synced up the pda. Thanks!
Palm Pilot m500 now works perfectly. Tested with kernel-2.6.9- 1.698_FC3.i686.rpm installed from the FC3 testing directory.
Running 2.6.9-1.9_FC2, pilot synchronization working for me, too.