Description of problem: kernel panic on startup Version-Release number of selected component (if applicable): RHEL 5.1 Beta Snapshot 7 How reproducible: always Steps to Reproduce: 1. install RHEL 5.1 beta 2. restart after install 3. kernel panic in snd_hda_codec Additional info: The machine is a new laptop Dell Latitude D630 (Intel 965GM chipset)
Created attachment 199951 [details] kernel dump
actually i was mistaken. snd_hda_codec loads fine - i get the panic after loading snd_hda_intel.
would be good to know how many other systems this affects... i.e. just this system or anything with this sound chipset.
Created attachment 200801 [details] "lspci -nv" from the laptop
Can you provide a stack trace possibly?
Re Comment #6: Boot and try loading the module manually, capture the panic. Thats the stack trace Im interested in.
I have a desktop system on my desk with what looks like the same if not a very similar audio chipset. I'll try out sound on it tomorrow morning.
Re comment #6: i've provided a stack trace in comment #1 ? or is it a wrong one ? it's a stack trace from kernel panic i got after running 'modprobe snd_hda_intel', captured with kdump.
Stack trace in comment #1 seems to be from alsaunmute being executed. I was looking for stack trace from when snd_hda_intel is loaded instead. Do both panics occur in the same place? I.e. would the stack trace from Comment #1 and the panic from loading snd_hda_intel be identical?
yes, that's right.
ok, the desktop system I have does not panic with the -48.el5 kernel. It boots up and the sound works just fine from what I can tell. I'll attach lspci output
Created attachment 202661 [details] lspci output - system does not panic
Rez, can you tell us what other Dell systems have this CODEC?
On Mon, 2007-09-24 at 15:42 -0500, Rezwanul_Kabir wrote: > What do the M65 and M90 have? > > Oh yes, M65 at least has STAC9200. Need to check M90.. > Red Hat should have an M65 in Westford. I have an M90 in my office in Raleigh. The M90 is currently running the x86 arch of the 8/17 beta code plus the 2.6.18-48.el5 kernel. I'm not aware of how to test for the specific CODEC in software.
Both M65 and M90 have STAC9200 audio codec..
Is this a regression? Did this used to work in 5.0? Or did this never ever work? Trying to determine if this was a regression introduced with the 1.0.14 ALSA update in 5.1 or not.
So, I have tested Snapshot 8 (48.el5), behaves exactly the same way. So i tried RHEL 5 GA, it boots, loads snd_hda_intel. However, running alsamixer results in kernel panic. I checked microphone settings, it was disabled. After enabling, alsamixer starts up without kernel panic. So - CLOSED/duplicate ?
Well, that's good that it is similar (not sure why the microphone is allowed to be disabled). My bugzilla deals with STAC9205 codecs, not STAC9200 so they are close but not exactly the same (maybe I'm splitting hairs). Maybe keep it opened but assign it to me? How's that sound, Brian?
There is new support for STAC9205 upstream in alsa-driver-1.0.15rc3. The STAC9200 support has been there for a little while, so not sure if this got broken by the recent ALSA update or not. There are also a bunch of updates in patch_sigmatel for newer dell models.
Yeah, you are probably referring to what Sigmatel added for the STAC9205-specific Dell laptops. I have a patch all worked up and am waiting for Dell to test it.
Just FYI on my latitude d630 the kernel also crashes when snd_hda_intel loads if I disable the microphone in the BIOS, otherwise it works fine. This is on Fedora 7 with kernel 2.6.22.9-91.fc7.
Just to bring some closure to this, perhaps someone could test the kernel with the patch for STAC9205. See people.redhat.com/jfeeney/.bz254067. Note: The only rpm there is for the x86_64 platform. Thanks.
Can someone with the affected hardware test Johns kernel mentioned in Comment #31?
I tried to foist testing of this off on Dell, thinking they must have a Lattitude D630 readily available, but they don't. Michal, since you reported it, could you test this please (unless you don't have the laptop anymore)? Thanks in advance if you can.
FWIW, this doesn't happen to me anymore with kernel kernel-2.6.23.15-137.fc8.x86_64
Unfortunately i don't have the laptop anymore.
Patch bug#451007 might solve this issue in RHEL5.3
This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?".
Unfortunately the previous automated notification about the non-inclusion of this request in Red Hat Enterprise Linux 5.3 used the wrong text template. It should have read: this request has been reviewed by Product Management and is not planned for inclusion in the current minor release of Red Hat Enterprise Linux. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?" or raise an exception.
Updating PM score.