Bug 180151

Huh? "Disappeared"?
At least attach two dmesgs, from 1.1830 and 1.1656, please.

Created attachment 124429 [details]
dmesg.2.6.14-1.1656_FC4 (works)

Created attachment 124430 [details]
dmesg.2.6.15-1.1831_FC4 (does not work)

2.6.15-1.1831_FC4 has the same symptom.

This looks like some sort of a handoff problem.

 ehci_hcd 0000:00:02.2: EHCI Host Controller
 ehci_hcd 0000:00:02.2: debug port 1
-ehci_hcd 0000:00:02.2: BIOS handoff failed (160, 01010001)
-ehci_hcd 0000:00:02.2: continuing after BIOS bug...
+PCI: cache line size of 64 is not supported by device 0000:00:02.2
 ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 1
 ehci_hcd 0000:00:02.2: irq 193, io mem 0xff6ffc00
-PCI: cache line size of 64 is not supported by device 0000:00:02.2
-ehci_hcd 0000:00:02.2: park 0
-ehci_hcd 0000:00:02.2: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004
+ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
 hub 1-0:1.0: USB hub found
...
 hub 2-0:1.0: 3 ports detected
+usb 1-1: new high speed USB device using ehci_hcd and address 2
 ACPI: PCI Interrupt Link [LUS1] enabled at IRQ 20
...
 hub 3-0:1.0: 3 ports detected
-usb 2-1: new full speed USB device using ohci_hcd and address 2
-usb 2-1: not running at top speed; connect to a high speed hub
-hub 2-1:1.0: USB hub found
-hub 2-1:1.0: 4 ports detected
-usb 2-1.3: new low speed USB device using ohci_hcd and address 3
-input: USB HID v1.10 Mouse [Cypress Semi. Cypress Ultra Mouse] on
usb-0000:00:02.0-1.3
 ieee1394: Initialized config rom entry `ip1394'
...
 ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[201]  MMIO=[ff4ff000-ff4ff7ff] 
Max Packet=[2048]
+usb 1-1: device descriptor read/64, error -110
 ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00e01800005546db]
...
 eth1: Setting full-duplex based on negotiated link capability.
-Bluetooth: Core ver 2.7
+usb 1-1: device descriptor read/64, error -110
+usb 1-1: new high speed USB device using ehci_hcd and address 3
+Bluetooth: Core ver 2.8
 NET: Registered protocol family 31

Tim, does 1832 (available from
http://people.redhat.com/davej/kernels/Fedora/FC-4/ ) fix this by any chance?

No, it doesn't.

This continues to be broken in Fedora Core 5. :-(

Still not working with kernel-2.6.16-1.2133_FC5.  This is on x86_64 by the way.

[This comment added as part of a mass-update to all open FC4 kernel bugs]

FC4 has now transitioned to the Fedora legacy project, which will continue to
release security related updates for the kernel.  As this bug is not security
related, it is unlikely to be fixed in an update for FC4, and has been migrated
to FC5.

Please retest with Fedora Core 5.

Thank you.

Already did so in comment #5.

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.

I no longer seem to get this problem so I suppose it's fixed.