Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932124AbbEULX7 (ORCPT ); Thu, 21 May 2015 07:23:59 -0400 Received: from mondschein.lichtvoll.de ([194.150.191.11]:53698 "EHLO mail.lichtvoll.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751856AbbEULXz convert rfc822-to-8bit (ORCPT ); Thu, 21 May 2015 07:23:55 -0400 From: Martin Steigerwald To: Takashi Iwai Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org Subject: Re: [REGRESSION] 4.1-rc4: Sound muted after boot Date: Thu, 21 May 2015 13:23:54 +0200 Message-ID: <5064269.CSrZTixCiO@merkaba> User-Agent: KMail/4.14.7 (Linux/4.1.0-rc4-tp520-btrfstrim-pstatetrace+; KDE/4.14.2; x86_64; git-38b5d90; 2015-04-16) In-Reply-To: References: <1902192.Ae1uPbIBnJ@merkaba> <2833904.edl5C89hXc@merkaba> MIME-Version: 1.0 Content-Transfer-Encoding: 8BIT Content-Type: text/plain; charset="iso-8859-1" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4515 Lines: 112 Am Donnerstag, 21. Mai 2015, 12:07:30 schrieb Takashi Iwai: > At Thu, 21 May 2015 11:52:08 +0200, > > Martin Steigerwald wrote: > > Am Donnerstag, 21. Mai 2015, 11:16:24 schrieb Takashi Iwai: > > > At Thu, 21 May 2015 10:53:46 +0200, > > > > > > Martin Steigerwald wrote: > > > > Am Donnerstag, 21. Mai 2015, 06:28:24 schrieb Takashi Iwai: > > > > > At Wed, 20 May 2015 16:31:55 +0200, > > > > > > > > > > Martin Steigerwald wrote: > > > > > > Hello! > > > > > > > > > > > > On ThinkPad T520 (Intel Sandybridge) with 4.14-rc4 + two BTRFS > > > > > > patches > > > > > > and one Intel P-State debug patch I have no sound output on > > > > > > internal > > > > > > Intel HD audio codec. > > > > > > > > > > > > According to ThinkPad T520 LED with striked-through speaker the > > > > > > loud > > > > > > speaker is in disabled state. Also KDE?s Phonon says a soundcard > > > > > > is > > > > > > missing. In alsa-mixer I see nothing as MM for muted. If I press > > > > > > the > > > > > > key next to the LED I get a notification on the desktop that > > > > > > loud > > > > > > speaker has been enabled / disabled, but the LED still is on for > > > > > > it > > > > > > being disabled. > > > > > > > > > > > > I do not hear anything in Amarok or with aplay. alsa-mixer sound > > > > > > volumes > > > > > > are 100 for master and PCM. I also tried with disabling > > > > > > "Auto-Mute > > > > > > Mod", but still no sound. > > > > > > > > > > > > When I reboot and in BIOS or GRUB press the key then the LED > > > > > > toggles > > > > > > state. > > > > > > > > > > > > When I reboot into Linux 4.0.1 sound is working fine and loud > > > > > > speaker > > > > > > disabled LED is toggled off, so I bet this is a regression > > > > > > 4.1-rc4 > > > > > > compared to 4.0.1. > > > > > > > > > > Please run alsa-info.sh at both working and non-working cases > > > > > (with > > > > > old and new kernels), and attach the outputs. Run the script with > > > > > --no-upload option. > > > > > > > > All attached. > > > > > > > > I also have full dmesg outputs available in case it is needed. > > > > > > > > > Also, such a problem is rather the device permissions problem. > > > > > Check the device permissions of /dev/snd/* files (also check > > > > > getfacl > > > > > /dev/snd/*, too). > > > > > > > > If its a permissions problem, why does it happen with 4.1-rc4, but > > > > not > > > > with 4.0.1 oder any earlier kernels? > > > > > > I wanted to mean it's rather "often" a permission problem. Not > > > necessarily your case, but still worth to check. > > > > > > The mute LED behavior change is because of the new control added > > > recently. You seem to have changed the value to "On" while the > > > default should be "Follow Master". This explains the difference of > > > behavior from 4.0. It's no regression but manual misconfiguration by > > > user. In this mode, LED has no connection with the sound output at > > > all. > > > > I didn?t change ALSA configuration on upgrade from 4.0 to 4.1. Can it be > > it picked "On" as default? > > It shouldn't. The default is "follow master". > Might it be changed by kmix or such...? I don?t know, but in my KMix setup the Mute-LED Mode is not within the displayed channels, but on available channels, so I didn?t see this. > > > Other than that, no different is seen in the hardware level. The > > > codec registers show all same values. That is, from the driver POV, > > > the sound should work. (Though, you set "Disabled" to "Auto-Mute > > > Mode" control which looks rather weird.) > > > > > > So, revert "Mute-LED Mode" control to "Follow Master". It can be done > > > via alsamixer, amixer or whatever. Then check whether the sound > > > works again. Check also from the headphone, too. > > > > That works. Thank you. Headphone I will check later. > > Interesting. Could you confirm that changing "Mute-LED Mode" really > mutes the output, not only changing the LED? This control was > supposed to behave independently from the sound output. When I set it back to "On" again output is muted. On setting "Off" or "Follow master" I can hear sound. Thanks, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/