Bug Description

It does not happen the first time I hotSync my Treo 650, but somewhere in subsequent pilot hotsync attempts, I am getting a kernel oops with the below kernel trace. This operation is not normally prone to error like this, so I suspect either the appletouch driver or some oddity regarding running on a PPC machine. Also, I believe that something might be going wrong in the suspend/resume cycle that is putting the kernel into a funky state, since I am able to hotSync reliably after a clean boot.

I'm having this problem as well, but without appletouch loaded. There is also a debian bug #357193 filed against this. I suspect this is a problem in the stock kernel and has been fixed in later versions.

Ben: is there a plan for getting Palm USB syncing working in Dapper? (I assume it has to be made to work at some point, otherwise people with such devices are going to be out of luck for the next five years...) Is there a plan to rev. the kernel? Or to figure out the problem and backport a patch?

I also observe this problem on the 386 architecture (2.6.15.7 on Athlon XP). I think it may explain a lot of problems people are having with Palm syncing on USB. I investigated, and the root cause appears to be a race condition during open/close of the USB device. A brief description of the problem, along with the official patch, is here:

I have a patch against Dapper 2.6.15.7 attached (it is a little different - seems gregkh's patch is against a later version?). Applying it causes my Treo 600 sync process to go from "almost never" working to "always" working.

I'd like to echo the previous reporters comment about this being an important issue for a Dapper update... It was really frustrating for me, personally, and I think there are a lot of Palm users out there who would benefit.

Brian writes:
"I tried to recreate the crash a fair bit today and was unable to recreate the original bug report. I tried performing hot syncs throught
the day and even hibernated once and then hot synced. "