All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: regressions@lists.linux.dev
Cc: linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION 5.19.x] AMD HD-audio devices missing on 5.19 #forregzbot
Date: Mon, 19 Sep 2022 17:23:11 +0200	[thread overview]
Message-ID: <b5271342-c804-70c1-9a81-d94efa59b203@leemhuis.info> (raw)
In-Reply-To: <c6ea56f5-05be-c9bb-4eda-a3c4a081326f@leemhuis.info>

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.

On 24.08.22 09:13, Thorsten Leemhuis wrote:

> 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

#regzbot fixed-by: 2380f1e8195ef612deea

      reply	other threads:[~2022-09-19 15:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22 14:12 [REGRESSION 5.19.x] AMD HD-audio devices missing on 5.19 Takashi Iwai
2022-08-23  1:00 ` Jason Gunthorpe
2022-08-23  6:06   ` Takashi Iwai
2022-08-23 11:46     ` Takashi Iwai
2022-08-23 20:28       ` Jason Gunthorpe
2022-08-23 21:01         ` Robin Murphy
2022-08-24  0:02           ` Jason Gunthorpe
2022-08-24  0:02             ` Jason Gunthorpe
2022-09-06 15:41         ` Jason Gunthorpe
2022-09-06 15:52           ` Takashi Iwai
2022-09-06 15:53             ` Jason Gunthorpe
2022-09-06 16:04               ` Takashi Iwai
2022-09-06 16:08                 ` Jason Gunthorpe
2022-09-06 16:16                   ` Takashi Iwai
2022-09-07 10:08                     ` Takashi Iwai
2022-09-07 13:28         ` Takashi Iwai
2022-09-07 13:48           ` Jason Gunthorpe
2022-09-08  6:23             ` Takashi Iwai
2022-08-24  7:13 ` Thorsten Leemhuis
2022-09-19 15:23   ` Thorsten Leemhuis [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b5271342-c804-70c1-9a81-d94efa59b203@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.