Red Hat Bugzilla – Bug 812052
problem detecting sound hardware
Last modified: 2012-04-16 10:11:39 EDT
Created attachment 577122 [details]
"messages" for 3.3.1 kernel and 3.3.0 kernel boot
Description of problem:
This started with kernel-PAE 3.3.1-3. With all previous kernels for at least the past 1.5 years there have been no problems with sound hardware detection. I boot up on 3.3.1 and log in to KDE and I get a KDE error pop up "Remove Sound Devices" that states that certain devices are no longer available and would I like to have them removed. I also get a KDE notification balloon that states that HDA NVidia ALC883 does not work and it is falling back to "default".
Version-Release number of selected component (if applicable):
Only one boot out of seven with 3.3.1-3 did not have the problem. Every boot with < 3.3.1-3 works as expected.
Steps to Reproduce:
1.boot into kernel-PAE 3.3.1-3
receive messages that hardware needs to be removed. If I boot enough times I did get the correct hardware, "Internal Audio Analog Stereo" one time.
boot into kernel-PAE 3.3.0-8
everything works as it should. System Settings shows what it always shows: "Internal Audio Analog Stereo"
Fedora 16 upgraded from Fedora 14 (upgrade was back in December of 2011, no problems until latest kernel)
motherboard: ECS GeForce6100SM-M
CPU: AMD Athlog 64 X2 5600+
nouveau driver on integrated Geforce6100 GPU
relevant sections of "messages" file for kernel-PAE 3.3.1-3 (Apr 11) and kernel-PAE 3.3.0-8 (Apr 12)
The kernel seems to find the devices identically between kernel versions. Both show the card0 probes working.
Pulseaudio seems to be having some kind of issue with having too many files open:
Apr 11 09:17:32 HAL5000 pulseaudio: module-udev-detect.c: inotify_init1() failed: Too many open files
Apr 11 09:17:32 HAL5000 pulseaudio: module.c: Failed to load module "module-udev-detect" (argument: ""): initialization failed.
Apr 11 09:17:32 HAL5000 pulseaudio: main.c: Module load failed.
Apr 11 09:17:32 HAL5000 pulseaudio: main.c: Failed to initialize daemon.
Apr 11 09:17:32 HAL5000 pulseaudio: main.c: Daemon startup failed.
Lennart, what is pulseaudio trying to do there?
When you updated the kernel, was anything else updated at the same time? Or have you done other updates since installing 3.3.0-8? When kernel 3.3.1-3 was installed, it built a new initramfs to use with it. If there were updates to things in userspace that are contained in the initramfs between the two kernel updates, then only the initramfs for 3.3.1-3 would contain those.
Also, can you please try 3.3.1-3 without loading the vbox modules at all? While it may seem unrelated, they've been known to cause weird issues.
Thank you for looking at this. Of course, now that I have filed a bug, it figures that this time when I booted 3.3.0-8 that I just got the same message about the sound hardware. So, it is NOT just 3.3.1-3. It just appears to happen more often with 3.3.1-3 kernel.
As for what I updated the same time as the kernel:
I installed the 3.3.0-8 kernel back on April 2 and ran for the entire week, cold booting each morning with no problems. So whatever it is seems to have crept in very recently.
I updated on April 4:
I updated on April 3:
Now that 3.3.0-8 is acting up, I'm at a loss. I am going to reinstall 3.3.1-3 and then see if I get the same problems with using Gnome instead of KDE. I haven't tried Gnome since this started happening.
I just installed 3.3.1-3 and rebooted (not a cold boot). Then logged into my user account with Gnome DE. No errors or messages. Opened the system settings and then sound, everything looked as expected, and then I ran the sound test and it worked fine. I then logged out of Gnome, and into KDE, no problem, and the sound settings in the KDE control panel were fine. At this point, I think I need to run more tests with using Gnome vs KDE, to see if that really is an issue.
I believe this can be closed. I no longer believe it is a kernel problem. It looks more like something with KDE on this system. Consistently after a boot, if I log into Gnome first, then into KDE, there is no problem. If I log straight into KDE, I have problems with the sound hardware detection, and some applications will not play sounds.
Thank you for letting us know.