Bug 139823

Summary: kernel-2.6.9-1.678_FC3 Oops from visor module
Product: [Fedora] Fedora Reporter: Nigel Metheringham <nigel>
Component: kernelAssignee: Dave Jones <davej>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3CC: pfrields, rda, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-11-22 04:34:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Log output from kernel Oops
none
/var/log/message OOPS and problem recreation none

Description Nigel Metheringham 2004-11-18 10:01:44 UTC 
Description of problem:
Attempted to sync Palm device first time after kernel upgrade,
sync fails, kernel Oops produced

Version-Release number of selected component (if applicable):
kernel-2.6.9-1.678_FC3

How reproducible:
Will do further tests to determine this later

Steps to Reproduce:
1. Press sync button on USB attached Palm device
  

Additional info:
Attached information from /var/log/messages
Comment 1 Nigel Metheringham 2004-11-18 10:03:45 UTC 
Created attachment 106941 [details]
Log output from kernel Oops
Comment 2 Warren Togami 2004-11-18 10:05:29 UTC 
Was the previous 667 kernel any better?
Comment 3 Nigel Metheringham 2004-11-18 10:08:54 UTC 
Just to make it clear, everything related to the Palm was working OK
prior to this kernel upgrade (from kernel-2.6.9-1.667).

Current kernel is i686 UP build:-
Linux angua.localnet 2.6.9-1.678_FC3 #1 Mon Nov 15 18:28:07 EST 2004
i686 i686 i386 GNU/Linux

There is a udev tweak (left over from FC3 test releases) to make the
devices be visible to the system - an extra file
/etc/udev/rules.d/10_palm.rules containing
  KERNEL="ttyUSB1", NAME="%k", SYMLINK="pilot"

This may no longer be necessary, although a look at the default udev
rules file does not convince me that this is handled correctly yet.
Comment 4 Nigel Metheringham 2004-11-19 09:29:59 UTC 
Had a chance to reboot the box (the visor module is jammed in and 
can't be unloaded after this Oops) and retry.  The problem is
definitely reproducable on my hardware.
Comment 5 Peter Hunter 2004-11-20 13:03:35 UTC 
For what it's worth, I get this Oops too. Everything was fine under
667 and now I get the oops repeatably when trying to sync my Palm
Tungsten T3.
Comment 6 Kars de Jong 2004-11-21 14:52:23 UTC 
Same here, using a Palm Zire. Works OK with 667, the same Oops using 678.
Comment 7 Bob Arendt 2004-11-21 23:44:50 UTC 
Created attachment 107148 [details]
/var/log/message OOPS and problem recreation
Comment 8 Dave Jones 2004-11-22 04:34:53 UTC 

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