Bug 81038

Summary: ehci-hcd fails to init on a Intel D845EBG2 motherboard
Product: [Retired] Red Hat Linux Reporter: Joe Ceklosky <jceklosk>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: bhuffman
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
URL: None
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:50:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Joe Ceklosky 2003-01-03 17:13:35 UTC
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:
Always

Steps to Reproduce:
1.Boot the machine
2.
3.
    

Actual Results:  Does not init the ehci_hdc modules

Expected Results:  ehci_hdc init

Additional info:

Comment 1 Brian Huffman 2003-01-03 23:17:06 UTC
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 21:30:19 UTC

*** This bug has been marked as a duplicate of 80488 ***

Comment 3 Red Hat Bugzilla 2006-02-21 18:50:54 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.