Received: by 2002:a05:6358:45e:b0:b5:b6eb:e1f9 with SMTP id 30csp285372rwe; Wed, 24 Aug 2022 00:29:06 -0700 (PDT) X-Google-Smtp-Source: AA6agR4e4BC3XOZH/dcyJ1zUdWi8TbzVseerX9dswYUAqPt/kLASXXsRRYXJMSo2L/UBzR2VFzxZ X-Received: by 2002:a17:902:f382:b0:173:5eb:f67b with SMTP id f2-20020a170902f38200b0017305ebf67bmr5311658ple.53.1661326146364; Wed, 24 Aug 2022 00:29:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1661326146; cv=none; d=google.com; s=arc-20160816; b=braWOuH07buxJPF2+c6cEwVXNg/dFtB97INB3lE9o43sCwlxJ+pfIJj0IeAHoETLJ9 hocbzRKtIMnvQrBP/YbpmBTz6Of0myzcONVgzGgHYrUzgk8r7+jbDtHIG6bCdWxkSye/ doHJDyIQ5VvL4rOLM92NamARzTtZEzoD4hX9lxKRooMtLiWN4czsXlRSfNLmo1vdxSjT eAfyPs3YJhqHzg3mU4dTRxQ0p4dH+UDOp6DA0+7OHvRNB6PX8YIPQ2iDBu6nJ+cXqpVm iOiseRCuSEGwKo7qbctdSZKLKhLqSe2MjzuIHehC0SoOKjksXkXvw2am/0p6rf0bOkWC WN9w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from:to :references:cc:content-language:subject:user-agent:mime-version:date :message-id; bh=yKOtFmBM0KGOuNMVe07e8kMnjmo6nQa+G2pOfu2vTdI=; b=Ev6nhvmrnHdihFymvIxX9mVAQVsr4UwW1vdOzJMLgJ1HCoNWg9+5Z/GPM70BpYqNPH h2nubzE5DAg5GaAw+9bBI64cNQk9jWsVSVwx2TzDXTX1d4E2MWY19B8GWlFIGNrotQrE 2yGTGUy/BAKy7gKdrKNj4/IvBqSK7qOcS5rICxoF3f1rb4jOpIAG5fUHMhtEixUWfrVx kuhOFkKANy72GAIIaWoUz+uiCrpfm01DCFpyuzSlfhT0uO41bOHd7NO8kn9sDoA0PzDS 9MotcoyNN78vG/f9szutmMfrikQjalnIChcmndn+GqS4lrJwg0wEm6u0kN3+9WD/PVM1 d6nA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id k190-20020a6384c7000000b0041cfefd9844si10980210pgd.694.2022.08.24.00.28.55; Wed, 24 Aug 2022 00:29:06 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235127AbiHXHNj (ORCPT + 99 others); Wed, 24 Aug 2022 03:13:39 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43834 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233467AbiHXHNh (ORCPT ); Wed, 24 Aug 2022 03:13:37 -0400 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8234::]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5478F94109 for ; Wed, 24 Aug 2022 00:13:36 -0700 (PDT) Received: from [2a02:8108:963f:de38:eca4:7d19:f9a2:22c5]; authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1oQkZy-0006rf-HJ; Wed, 24 Aug 2022 09:13:34 +0200 Message-ID: Date: Wed, 24 Aug 2022 09:13:34 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.0 Subject: Re: [REGRESSION 5.19.x] AMD HD-audio devices missing on 5.19 Content-Language: en-US Cc: linux-kernel@vger.kernel.org References: <874jy4cqok.wl-tiwai@suse.de> To: regressions@lists.linux.dev From: Thorsten Leemhuis In-Reply-To: <874jy4cqok.wl-tiwai@suse.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1661325216;22c85f27; X-HE-SMSGID: 1oQkZy-0006rf-HJ X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,NICE_REPLY_A, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [TLDR: I'm adding this regression report to the list of tracked regressions; all text from me you find below is based on a few templates paragraphs you might have encountered already already in similar form.] TWIMC: this mail is primarily send for documentation purposes and for regzbot, my Linux kernel regression tracking bot. These mails usually contain '#forregzbot' in the subject, to make them easy to spot and filter. Hi, this is your Linux kernel regression tracker. On 22.08.22 16:12, Takashi Iwai wrote: > > we've received regression reports about the missing HD-audio devices > on AMD platforms, and this turned out to be caused by the commit > 512881eacfa72c2136b27b9934b7b27504a9efc2 > bus: platform,amba,fsl-mc,PCI: Add device DMA ownership management > > The details are found in openSUSE bugzilla: > https://bugzilla.suse.com/show_bug.cgi?id=1202492 > > The problem seems to be that HD-audio (both onboard analog and HDMI) > PCI devices are assigned to the same IOMMU group as AMD graphics PCI > device, and once after the AMDGPU is initialized beforehand, those > audio devices can't be probed since iommu_device_use_default_domain() > returns -EBUSY. > > I'm not sure whether it's specific to PCI bus due to the assignment > logic of those IOMMU groups, or it's about the handling of the active > domain assignment. In anyway, disabling IOMMU works around the > problem, and passing driver_managed_dma flag to the HD-audio driver > was also confirmed to work around it, too. > > The problem persists with 6.0-rc1 kernel. > > If you have / can give any fix patch or debug patch, let me know; I'll > build test kernels and ask the reporters. Thanks for the report. To be sure below issue doesn't fall through the cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression tracking bot: #regzbot introduced 512881eacfa72c2136b27b99 ^ https://bugzilla.suse.com/show_bug.cgi?id=1202492 #regzbot title AMD HD-audio devices missing on 5.19 #regzbot ignore-activity This isn't a regression? This issue or a fix for it are already discussed somewhere else? It was fixed already? You want to clarify when the regression started to happen? Or point out I got the title or something else totally wrong? Then just reply -- ideally with also telling regzbot about it, as explained here: https://linux-regtracking.leemhuis.info/tracked-regression/ Reminder for developers: When fixing the issue, add 'Link:' tags pointing to the report (the mail this one replies to), as explained for in the Linux kernel's documentation; above webpage explains why this is important for tracked regressions. Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) P.S.: As the Linux kernel's regression tracker I deal with a lot of reports and sometimes miss something important when writing mails like this. If that's the case here, don't hesitate to tell me in a public reply, it's in everyone's interest to set the public record straight.