Red Hat Bugzilla – Bug 127750
uhci_hcd controller halted with 4GB RAM in Dell Precision 450
Last modified: 2015-01-04 17:07:52 EST
Description of problem:
- Installed 4, 1GB DIMMS in Dell Precision 450
- Boot with kernel 2.6.6-1.435.2.3smp (or non-SMP)
- USB not functional (USB mouse doesn't work)
- dmesg shows: uhci_hcd 0000:00:1d.0: host controller process error,
something bad happened!
uhci_hcd 0000:00:1d.0: host controller halted, very bad!
- less than 4GB, USB is functional
Version-Release number of selected component (if applicable):
UHCI Driver v2.2
Boot either SMP or UP kernel with 4GB (4-1GB DIMMS tested)
Created attachment 101858 [details]
dmesg snip for 4gb USB problem
This sounds like something I'm seeing on a Dell Precision 450 with 4GB
of RAM, but I don't remember those exact kernel messages and I need to
reinstall FC2 and retest before I can say for certain that it's
experiencing this exact bug.
BTW, in case something keeps me from testing this in the near future,
does using the "mem=" option for the kernel (e.g. "mem=2048m") make
the mouse work, or do you have to physically remove memory?
Yep mem=2048m makes the mouse work and no errors from uhci_hcd.
MD5 (kernel-2.6.6-1.435.2.3.no4g4g.i686.rpm) =
MD5 (kernel-2.6.6-1.435.2.3.no4g4g.src.rpm) =
MD5 (kernel-debuginfo-2.6.6-1.435.2.3.no4g4g.i686.rpm) =
MD5 (kernel-smp-2.6.6-1.435.2.3.no4g4g.i686.rpm) =
These kernels have 4g4g disabled in the kernel .config. With these,
the USB ports on this Precision 450 work, without having to use mem=
to limit memory.
I'm guessing now that this issue may be 4g4g-related somehow...
With plain 2.6.6-1.435.2.3smp (i.e. without disabling 4g4g), mem=2596m
works, mem=2597m breaks...
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat. The Fedora legacy project will be producing further kernel
updates for security problems only.
If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.
FWIW, this got "fixed" (?) by one of the FC2 update kernels, which disabled 4g4g...