Bug 200488

I saw keys like that. It's some moronic misfeature which some vendors
add to their keys: they present a normal drive and a pseudo-CD-ROM
to the host software. If you plug it in Windows, you can see both.
The messages appear because HAL pounds it every 2s.

A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed.  See bug 207474 for further details.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.

Thank you.

Still a problem

Oct 21 23:53:17 jks-desktop kernel: FS-Cache: Loaded
Oct 21 23:53:18 jks-desktop kernel: FS-Cache: netfs 'nfs' registered for caching
Oct 21 23:53:18 jks-desktop kernel: SELinux: initialized (dev 0:12, type nfs),
uses genfs_contexts

Oct 22 01:55:18 jks-desktop kernel: usb 5-2.4: new high speed USB device using
ehci_hcd and address 6
Oct 22 01:55:19 jks-desktop kernel: usb 5-2.4: configuration #1 chosen from 1 choice
Oct 22 01:55:19 jks-desktop kernel: Initializing USB Mass Storage driver...
Oct 22 01:55:19 jks-desktop kernel: scsi2 : SCSI emulation for USB Mass Storage
devices
Oct 22 01:55:19 jks-desktop kernel: usbcore: registered new driver usb-storage
Oct 22 01:55:19 jks-desktop kernel: USB Mass Storage support registered.
Oct 22 01:55:24 jks-desktop kernel:   Vendor: SanDisk   Model: U3 Cruzer Micro 
 Rev: 2.15
Oct 22 01:55:24 jks-desktop kernel:   Type:   Direct-Access                    
 ANSI SCSI revision: 02
Oct 22 01:55:24 jks-desktop kernel: SCSI device sda: 1994385 512-byte hdwr
sectors (1021 MB)
Oct 22 01:55:24 jks-desktop kernel: sda: Write Protect is off
Oct 22 01:55:24 jks-desktop kernel: sda: assuming drive cache: write through
Oct 22 01:55:24 jks-desktop kernel: SCSI device sda: 1994385 512-byte hdwr
sectors (1021 MB)
Oct 22 01:55:24 jks-desktop kernel: sda: Write Protect is off
Oct 22 01:55:24 jks-desktop kernel: sda: assuming drive cache: write through
Oct 22 01:55:24 jks-desktop kernel:  sda: sda1
Oct 22 01:55:24 jks-desktop kernel: sd 2:0:0:0: Attached scsi removable disk sda
Oct 22 01:55:24 jks-desktop kernel:   Vendor: SanDisk   Model: U3 Cruzer Micro 
 Rev: 2.15
Oct 22 01:55:24 jks-desktop kernel:   Type:   CD-ROM                           
 ANSI SCSI revision: 02
Oct 22 01:55:24 jks-desktop kernel: sd 2:0:0:0: Attached scsi generic sg0 type 0
Oct 22 01:55:24 jks-desktop kernel: scsi 2:0:0:1: Attached scsi generic sg1 type 5
Oct 22 01:55:24 jks-desktop kernel: sr0: scsi3-mmc drive: 8x/40x writer xa/form2
cdda tray
Oct 22 01:55:25 jks-desktop kernel: cdrom: This disc doesn't have any tracks I
recognize!
Oct 22 01:55:56 jks-desktop last message repeated 28 times

[jks@jks-desktop ~]$ uname -a
Linux jks-desktop 2.6.18-1.2200.fc5 #1 SMP Sat Oct 14 16:59:56 EDT 2006 x86_64
x86_64 x86_64 GNU/Linux

OK I didn't see the "I am providing the requested information for this bug."
last time.

This seems to have been fixed in the current fc5 kernel.

Scratch that, it is still a problem in  2.6.20-1.2312.fc5

Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
http://fedoraproject.org/wiki/LifeCycle/EOL

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.