Bug 103527
| Summary: | audigy driver cause hard lock of kernel | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 3 | Reporter: | Denis Hennessy <dhennessy> | ||||||||||||||
| Component: | kernel | Assignee: | Arjan van de Ven <arjanv> | ||||||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> | ||||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||||
| Priority: | high | ||||||||||||||||
| Version: | 3.0 | ||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | athlon | ||||||||||||||||
| OS: | Linux | ||||||||||||||||
| Whiteboard: | |||||||||||||||||
| Fixed In Version: | 421 | Doc Type: | Bug Fix | ||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2003-09-05 23:05:39 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: | |||||||||||||||||
| Attachments: |
|
||||||||||||||||
Created attachment 94122 [details]
output of sysreport
Created attachment 94123 [details]
log from serial console
Created attachment 94124 [details]
output of lspci -vv
Created attachment 94125 [details]
output of lsmod
Created attachment 94126 [details]
copy of /proc/meminfo
Created attachment 94127 [details]
copy of /proc/cpuinfo
This is reported against the .411 kernel. It also happened with the .399 kernel. This appears to be fixed in the .421 release of the kernel. |
Description of problem: I have a dual-athlon computer with an audigy sound card. The soundcard detection app detects the audigy but fails to produce any sound. When I type some characters into the address field in mozilla, the computer will lock hard and produce the stack trace (attached) on a serial console. Since the stack trace is primarily made up of the audigy driver, I presume that's where the problem lies. This computer and sound card worked fine with RH9. Version-Release number of selected component (if applicable): kernel-2.4.21-1.1931.2.411.ent How reproducible: Every time. Steps to Reproduce: 1.Boot computer 2.Start Mozilla 3.Type 3/4 characters into web address box in mozilla Actual results: Computer will freeze. Stack dump on attached serial console. Expected results: No freeze. Additional info: Attached next will be console log, sysreport output and output of lspci, lsmod, /proc/meminfo, /proc/cpuinfo