Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 79210 - ehci-hcd.o fails to load
Summary: ehci-hcd.o fails to load
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: kernel
Version: 1.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
Depends On:
Blocks: 79578
TreeView+ depends on / blocked
Reported: 2002-12-07 16:02 UTC by Need Real Name
Modified: 2007-04-18 16:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2003-01-25 04:33:16 UTC

Attachments (Terms of Use)
The aforementioned patch (deleted)
2002-12-15 05:37 UTC, Need Real Name
no flags Details | Diff

Description Need Real Name 2002-12-07 16:02:44 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
ehci-hcd.o fails to load...

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Boot kernel 2.4.19-0.pp.20
2.Fails to load ehci-hcd.o (even after unarchiving the .gz)

Actual Results:  Nothing

Expected Results:  Successful loading of this module

Additional info:

Found it strange that all the drivers in :
/lib/modules/2.4.19-0.pp.20/kernel/drivers/usb were all archived

Comment 1 Arjan van de Ven 2002-12-07 17:07:57 UTC
can you find the PCI ID of your USB controller ?
(and the modules are compressed to save space; modutils knows how to uncompress
them on the fly when needed)

Comment 2 Need Real Name 2002-12-07 17:14:10 UTC
Has nothing to do with uncompressing on the fly..., since that works just fine.
Weird thing is that I see the insmod failure on kernel boot... but no where in
the system logs... peculiar

Doing an lspci bears this out:

00:1d.7 USB Controller: Intel Corp. 82801DB USB EHCI Controller (rev 02)

No idea why the kernel is balking at boot and not logging this to kernel messages!

Comment 3 Need Real Name 2002-12-14 16:57:43 UTC
Sent Arjanv an attachment with a patch from the maintainer

Comment 4 Pete Zaitcev 2002-12-15 01:20:19 UTC
Greg K-H pointed to this:

David-B said the timeout ought to be increased:

From: David Brownell

> static int ehci_reset (struct ehci_hcd *ehci)
> {
> ....
> ....
>    return handshake (&ehci->regs->command, CMD_RESET, 0, 250);
> }
> handshake() is always returning non-zero due to ETIMEOUT, I've also tried
> increasing 250 to 2000; if I ignore the return code from ehci_reset()
> the driver loads.

But does it work afterwards?  It didn't actually reset yet,
which is what the ETIMEDOUT indicates.

The EHCI 1.0 spec says (2.3.1) that bit clears itself when
the reset is done, and the only constraint on it is that
the STS_HALT bit must be set.  Which is guaranteed by the
call to ehci_halt() shortly before.

That 250 is in microseconds, not milliseconds, so maybe
this hardware is just slower to reset than the other EHCI
hardware I've used.  Try using "250 * 1000" instead ... your
"2000" was just two milliseconds, which still isn't much.

Requestor never indicated if he actually tested increased timeouts,
but just "sent Arjan a patch". Never attached the patch to the bug
either. But since Greg says it's known for the Intel's EHCI to have
this quirk, I'm assuming it's the timeout thing.

Comment 5 Need Real Name 2002-12-15 05:37:57 UTC
Created attachment 88739 [details]
The aforementioned patch

I have not tested the patch.

Comment 6 Need Real Name 2002-12-23 11:24:22 UTC
kernel 2.4.20-2.2 continues to show the same ehci-hcd.o load failure as

Comment 7 Need Real Name 2003-01-05 01:07:55 UTC
No change in the way ehci-hcd.o loads... same failure as 2.4.20-2.2

Comment 8 Need Real Name 2003-01-06 14:50:56 UTC
Close this bug... patch created back on Dec 15 from Brownell works on my
2.4.20-2.5 custom kernel. Perfectly

Note You need to log in before you can comment on or make changes to this bug.