linux-kernel - Re: snd_hda_intel 0000:00:1f.3: No response from codec, resetting bus: last cmd=

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]

Message-ID: <s5heeynwzhi.wl-tiwai@suse.de>
Date:   Mon, 04 Nov 2019 14:19:21 +0100
From:   Takashi Iwai <tiwai@...e.de>
To:     Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc:     Paul Menzel <pmenzel@...gen.mpg.de>,
        Andreas Noever <andreas.noever@...il.com>,
        Michael Jamet <michael.jamet@...el.com>,
        Yehezkel Bernat <YehezkelShB@...il.com>,
        Christian Kellner <ck@...om.net>,
        intel-gfx@...ts.freedesktop.org, Takashi Iwai <tiwai@...e.de>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Mario Limonciello <mario.limonciello@...l.com>
Subject: Re: snd_hda_intel 0000:00:1f.3: No response from codec, resetting bus: last cmd=

On Mon, 04 Nov 2019 14:10:24 +0100,
Mika Westerberg wrote:
> 
> Hi,
> 
> On Mon, Nov 04, 2019 at 01:57:54PM +0100, Paul Menzel wrote:
> > Dear Linux folks,
> > 
> > 
> > On the Dell XPS 13 9380 with Debian Sid/unstable with Linux 5.3.7
> > resuming0with Dell’s Thunderbolt TB16 dock connected, Linux spews
> > the errors below.
> 
> I have this machine here so can try to reproduce it as well.
> 
> > ```
> > [    0.000000] Linux version 5.3.0-1-amd64 (debian-kernel@...ts.debian.org) (gcc version 9.2.1 20191008 (Debian 9.2.1-9)) #1 SMP Debian 5.3.7-1 (2019-10-19)
> > […]
> > [    1.596619] pci 0000:00:1f.3: Adding to iommu group 12
> > [   14.536274] snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
> > [   14.544100] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
> > [   14.760751] input: HDA Intel PCH Headphone Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input16
> > [   14.760790] input: HDA Intel PCH HDMI as /devices/pci0000:00/0000:00:1f.3/sound/card0/input17
> > [  156.614284] snd_hda_intel 0000:00:1f.3: No response from codec, disabling MSI: last cmd=0x20270503
> > [  157.622232] snd_hda_intel 0000:00:1f.3: No response from codec, resetting bus: last cmd=0x20270503
> > [  158.626371] snd_hda_intel 0000:00:1f.3: No response from codec, resetting bus: last cmd=0x20370503
> > [  159.634102] snd_hda_intel 0000:00:1f.3: No response from codec, resetting bus: last cmd=0x201f0500
> > [  161.678121] snd_hda_intel 0000:00:1f.3: No response from codec, resetting bus: last cmd=0x20270503
> > [  162.682272] snd_hda_intel 0000:00:1f.3: No response from codec, resetting bus: last cmd=0x20370503
> > [  163.694234] snd_hda_intel 0000:00:1f.3: No response from codec, resetting bus: last cmd=0x201f0500
> > [  165.730142] snd_hda_intel 0000:00:1f.3: No response from codec, resetting bus: last cmd=0x20270503
> > […]
> > ```
> > 
> > In the bug report *[Intel Ice Lake, snd-hda-intel, HDMI] "No
> > response from codec" (after display hotplug?)* [1], note it’s a
> > different model, Takashi comments that this is a Thunderbolt or
> > i915 issue.
> 
> 0000:00:1f.3 is on PCH so not sure how it could be related to
> Thunderbolt, well or i915 for that matter.

It's the HD-audio controller PCI device and both HDMI and onboard
codecs are on that bus.  HDMI codec a shadow device of GPU, so it has
a strong dependency on i915 GPU driver.  The power of HD-audio bus and
codec is controlled over DRM audio component ops, so the power-on must
have been notified to GPU side, but still something seems missing.
ANd, with the dock, the other parties come to play into the game, so
it becomes more complex...


thanks,

Takashi