Bug 76495
Summary: | kernel-2.4.18-17.8.x update caused maestro3 to stop working | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Mike Basinger <dbasinge> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED DUPLICATE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-10-23 16:39:01 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mike Basinger
2002-10-22 14:55:44 UTC
I can confirm this problem affects RedHat 8.0 kernel 2.4.18-17.8.0. The original (2.4.18-14) kernel does not have the problem Always reproducable. Using redhat-config-soundcard, the sox process triggered is the CPU resource eater. Enableing ESD on login causes ESD to take the cpu resources. |