linux-kernel - Re: [REGRESSION] Headphones no longer working on MacPro6,1 with 4.4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 24 May 2016 09:41:06 -0700
From:	Laura Abbott <labbott@...hat.com>
To:	Takashi Iwai <tiwai@...e.de>
Cc:	Jaroslav Kysela <perex@...ex.cz>, alsa-devel@...a-project.org,
	"linux-kernel@...r.kernel.org >> Linux Kernel Mailing List" 
	<linux-kernel@...r.kernel.org>
Subject: Re: [REGRESSION] Headphones no longer working on MacPro6,1 with 4.4

On 05/21/2016 12:42 AM, Takashi Iwai wrote:
> On Sat, 21 May 2016 08:41:28 +0200,
> Takashi Iwai wrote:
>>
>> On Sat, 21 May 2016 00:27:22 +0200,
>> Laura Abbott wrote:
>>>
>>> On 03/15/2016 12:49 PM, Takashi Iwai wrote:
>>>> On Tue, 15 Mar 2016 20:38:41 +0100,
>>>> Takashi Iwai wrote:
>>>>>
>>>>> On Tue, 15 Mar 2016 20:23:09 +0100,
>>>>> Laura Abbott wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> We received a bug report https://bugzilla.redhat.com/show_bug.cgi?id=1316119
>>>>>> that the headphone jack on a MacPro6,1 stopped working on an upgrade from 4.3
>>>>>> to 4.4.
>>>>>>
>>>>>> The bugzilla has the alsainfo, diffing shows that the Amp-Out vals are
>>>>>> different. I tried a revert of 9f660a1c4 (" ALSA: hda/realtek - Fix silent
>>>>>> headphone output on MacPro 4,1 (v2)") but that didn't help.
>>>>>>
>>>>>> Any ideas before asking for a bisect? Does this hardware version need to have
>>>>>> the vref fixup as well?
>>>>>
>>>>> The obvious difference is the power state of each node.  The recent
>>>>> kernel has the finer power saving mode, and this might be the cause --
>>>>> Mac has some secret that requires some node to be powered up.
>>>>>
>>>>> Try to power on each node via hda-verb.  For example, to power up the
>>>>> node 0x05, run like:
>>>>>   hda-verb /dev/snd/hwC0D0 0x05 SET_POWER 0x01
>>>>
>>>> Oops, a typo: the last argument must be 0x00, corresponding to D0:
>>>>     hda-verb /dev/snd/hwC0D0 0x05 SET_POWER 0x00
>>>>
>>>>
>>>
>>> Bringing this back again, the command that makes it work is
>>>
>>> hda-verb /dev/snd/hwC0D0 0x10 SET_POWER 0x00
>>
>> OK, then please give alsa-info.sh output (run with --no-upload option)
>> at both working and non-working cases.
>>
>>> And this is still needed as of 4.5.4
>>
>> Of course, nothing has changed.  I didn't hear from you since my
>> previous question...
>
> Wait, some relevant changes have been merged in 4.6.
> Please check 4.6 at first to be sure.  Then give alsa-info.sh
> outputs.
>
>
> Takashi
>

I'm assuming you were referring to de3df8a986b6 ("ALSA: hda - Keep
powering up ADCs on Cirrus codecs") and 50fd4987c4f3 ("ALSA: hda - Don't
trust the reported actual power state"). These were available in the 4.4.5
stable tree but the problem still persists with that tree.

alsa-info is attached.




View attachment "alsa-info.txt.dHjx33I0I9.broken" of type "text/plain" (78429 bytes)