From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 07E78C433EF for ; Thu, 4 Nov 2021 16:37:19 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D622660E05 for ; Thu, 4 Nov 2021 16:37:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231670AbhKDQjz (ORCPT ); Thu, 4 Nov 2021 12:39:55 -0400 Received: from smtp-out2.suse.de ([195.135.220.29]:38368 "EHLO smtp-out2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230058AbhKDQjy (ORCPT ); Thu, 4 Nov 2021 12:39:54 -0400 Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out2.suse.de (Postfix) with ESMTP id 669711FD35; Thu, 4 Nov 2021 16:37:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1636043835; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=DWWjsw3+dx+jUbChweO+fNu5otO1S8egeCknN63hdrg=; b=o8DQUoPDYVoLB/Ac64vmOkE8HGU6f/GTk1gute5dBmK/D3lZ8skOMK3Uvob+5ozoLpf3vU dnJcHPnN0dcoc/8BLyPr2NK7kSKtvoPY317/zapIzO+jnSmr2Ai58F+Sv7uRCJ0L2oj4nP jaWoALCvb84OMn/rIMz+rlYe7Ts4cmY= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1636043835; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=DWWjsw3+dx+jUbChweO+fNu5otO1S8egeCknN63hdrg=; b=FlBS7/0Cxi37nj8Y1TsXiUV9qldsDIl9xOH5sxXuWspeU2x5qNk1Dfa+EBKvuLW8xL5Vqt CQHVRIQqFhAtcSAQ== Received: from alsa1.suse.de (alsa1.suse.de [10.160.4.42]) by relay2.suse.de (Postfix) with ESMTP id 5E2F62C160; Thu, 4 Nov 2021 16:37:15 +0000 (UTC) Date: Thu, 04 Nov 2021 17:37:15 +0100 Message-ID: From: Takashi Iwai To: "Alex Xu (Hello71)" Cc: Takashi Iwai , Linux Kernel Mailing List Subject: Re: No HDA sound output with AMD IOMMU on master In-Reply-To: <1636040759.fnw68jgcw1.none@localhost> References: <1636040759.fnw68jgcw1.none.ref@localhost> <1636040759.fnw68jgcw1.none@localhost> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 04 Nov 2021 17:01:51 +0100, Alex Xu (Hello71) wrote: > > Hi, > > At some point between 86f925fded03 and 5f4e450cd96b, the built-in sound > card on my ASRock B450 Pro4 has stopped working for me. All controls are > unchanged (no new or removed controls, all outputs are unmuted), but > when I try to play sound, I hear a click from the output powering up but > no sound otherwise. While attempting to play sound, the following lines > are output to the kernel log: > > [ 15.081961] snd_hda_intel 0000:0b:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0016 address=0x14ac00000 flags=0x0000] > [ 15.081982] snd_hda_intel 0000:0b:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0016 address=0x14ac00040 flags=0x0000] > [ 15.082253] snd_hda_intel 0000:0b:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0016 address=0x14ac00080 flags=0x0000] > [ 15.082581] snd_hda_intel 0000:0b:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0016 address=0x14ac000c0 flags=0x0000] > [ 15.082914] snd_hda_intel 0000:0b:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0016 address=0x14ac00100 flags=0x0000] > [ 15.083247] snd_hda_intel 0000:0b:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0016 address=0x14ac00140 flags=0x0000] > [ 15.083580] snd_hda_intel 0000:0b:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0016 address=0x14ac00180 flags=0x0000] > [ 15.083914] snd_hda_intel 0000:0b:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0016 address=0x14ac001c0 flags=0x0000] > [ 15.084246] snd_hda_intel 0000:0b:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0016 address=0x14ac00200 flags=0x0000] > [ 15.084579] snd_hda_intel 0000:0b:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0016 address=0x14ac00240 flags=0x0000] > [ 749.373925] amd_iommu_report_page_fault: 5917 callbacks suppressed > [ 749.373933] snd_hda_intel 0000:0b:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0016 address=0x1f2000000 flags=0x0000] > [ 749.373952] snd_hda_intel 0000:0b:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0016 address=0x1f2000040 flags=0x0000] > [ 749.374248] snd_hda_intel 0000:0b:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0016 address=0x1f2000080 flags=0x0000] > [ 749.374574] snd_hda_intel 0000:0b:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0016 address=0x1f20000c0 flags=0x0000] > [ 749.374907] snd_hda_intel 0000:0b:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0016 address=0x1f2000100 flags=0x0000] > [ 749.375240] snd_hda_intel 0000:0b:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0016 address=0x1f2000140 flags=0x0000] > [ 749.375572] snd_hda_intel 0000:0b:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0016 address=0x1f2000180 flags=0x0000] > [ 749.375904] snd_hda_intel 0000:0b:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0016 address=0x1f20001c0 flags=0x0000] > [ 749.376238] snd_hda_intel 0000:0b:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0016 address=0x1f2000200 flags=0x0000] > [ 749.376570] snd_hda_intel 0000:0b:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0016 address=0x1f2000240 flags=0x0000] > > Note that I first attempted to play audio around 15 seconds in, then > tried again about 730 seconds later. > > Adding mem_encrypt=off to the kernel command line does not fix the > issue, but adding mem_encrypt=off amd_iommu=off to the kernel command > line does fix it. I am not using any other IOMMU-related parameters such > as iommu=pt. > > I have not yet tested it, but it seems reasonable that this issue is > probably related to the recently pulled "ALSA: memalloc" series of > changes. > > Let me know what further information or testing is required. I can do a > full bisection but it is somewhat time-consuming due to the manual > nature of the tests. Could you try to revert the commit 2d9ea39917a4? thanks, Takashi