Description of problem:
Thinkpad T40 with new WD Passport 80GB USB2 Hard Drive will work as a high speed
device the first time I connect, but fails on subsequent connection, at high
speed. I am able to modprobe -r ehci-hcd and connect as a low speed device with
Version-Release number of selected component (if applicable):
Created attachment 125972 [details]
messages, dmesg, lspci
Looks like some random corruption to me. Otherwise how an address could jump
from 2 to 6 and from 8 to 23? You aren't running an nVidia video driver by
any chance? It's known to do things like that.
The increments seem rather random each time I do this.... And, no, I am not
running nVidia.... The only "non-standard" driver is, dare I say, madwifi from
the livna repository....
Created attachment 125974 [details]
lsmod output to list modules
Here is the output of modules loaded subsequent to the failure....
Have upgraded to FC5. Problem persists on FC5 (kernel-2.6.16-1.2080_FC5).
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.
(this is a mass-close to kernel bugs in NEEDINFO state)
As indicated previously there has been no update on the progress of this bug
therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue
still occurs for you and I will try to assist in its resolution. Thank you for
taking the time to report the initial bug.
If you believe that this bug was closed in error, please feel free to reopen