From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041217
Description of problem:
We get a kernel Oops shortly after attaching a USB Storage device. We have tried
several different devices, all of which worked with a slightly older kernel.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Boot system without storage attached
3.attach storage device
4.wait for device to settle
Actual Results: messages file shows attached Oops
Expected Results: device should have been attached to a device node.
this also happens with kernel kernel-2.6.12-1.1372_FC3
But it works with kernel-2.6.11-1.35_FC3
Created attachment 117024 [details]
messages file from boot to Oops from kernel-2.6.12-1.1398_FC4
Created attachment 117025 [details]
Oops message from kernel-2.6.12-1.1372_FC3
Mass update to all FC4 bugs:
An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (18.104.22.168). As there were ~3500 changes upstream between this and the
previous kernel, it's possible your bug has been fixed already.
Please retest with this update, and update this bug if necessary.
2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.
This is a mass-update to all currently open kernel bugs.
A new kernel update has been released (Version: 2.6.15-1.1830_FC4)
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_REPORTER 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.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
Closing per previous comment.