Bug 81038 - ehci-hcd fails to init on a Intel D845EBG2 motherboard
ehci-hcd fails to init on a Intel D845EBG2 motherboard
Status: CLOSED DUPLICATE of bug 80488
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2003-01-03 12:13 EST by Joe Ceklosky
Modified: 2008-01-17 12:49 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:50:54 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Joe Ceklosky 2003-01-03 12:13:35 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.79 [en] (X11; U; SunOS 5.8 sun4u)

Description of problem:
echi fails to init on an IntelD 845EBG2 
with the following messages:

hcd.c: ehci-hcd @ 00:1d.7, Intel Corp. 82801DB USB EHCI Controller
hcd.c: irq 9, pci mem e08a4c00
usb.c: new USB bus registered, assigned bus number 4
hcd.c: remove: 00:1d.7, state 0
usb.c: USB bus 4 deregistered

This is a known timing issue with the Intel boards for some
reason after apeaking with the USB kernel developement people.  
This value has been tweeked in newer versions of
2.4.21-PRE's kernels, please pick them up.

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

How reproducible:

Steps to Reproduce:
1.Boot the machine

Actual Results:  Does not init the ehci_hdc modules

Expected Results:  ehci_hdc init

Additional info:
Comment 1 Brian Huffman 2003-01-03 18:17:06 EST
This is a duplicate of 80488.  I have the same problem w/ my Intel 845GBV.  BTW,
when can we expect some response - even a simple one like "yes we know - will be
in release?"
Comment 2 Bill Nottingham 2003-01-06 16:30:19 EST

*** This bug has been marked as a duplicate of 80488 ***
Comment 3 Red Hat Bugzilla 2006-02-21 13:50:54 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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