Bug 111339

Summary: kernel oops when syncing palm pda via usb
Product: [Fedora] Fedora Reporter: Ivo <ivo>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 1   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:00:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
dmesg output none

Description Ivo 2003-12-02 12:06:05 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20030701

Description of problem:
kernel oopses in usb_disconnect when syncing with my palm tungsten via
usb (using the visor module). 
A way to reproduce the oops reliably is to initiate a sync and then
cancel the connection from the palm. In normal operation the sync
often succeeds but produces an oops occasionally, say 1 in 4 times.

I've observed this both on my laptop using the 2.4.22-1.2115.nptl
kernel, as well as my dual processor desktop machine under
2.4.22-1.2129.nptlsmp. I'll add an attachment with relevant dmesg output.

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

How reproducible:

Steps to Reproduce:
1. sync palm using pilot-xfer, jpilot, or gnome-pilot-applet
2. cancel the connection on the pda

Actual Results:  program doing the sync, e.g. jpilot, hangs in disk
wait. dmesg report kernel oops. usb moules cannot be unloaded.

Expected Results:  no kernel oops. sync should be canceled.

Additional info:

Comment 1 Ivo 2003-12-02 12:07:15 UTC
Created attachment 96279 [details]
dmesg output

Comment 2 Ivo 2003-12-04 11:39:41 UTC

*** This bug has been marked as a duplicate of 107929 ***

Comment 3 Red Hat Bugzilla 2006-02-21 19:00:15 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.