linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
	Andreas Noever <andreas.noever@gmail.com>,
	Michael Jamet <michael.jamet@intel.com>,
	Yehezkel Bernat <YehezkelShB@gmail.com>,
	Christian Kellner <ck@xatom.net>,
	intel-gfx@lists.freedesktop.org, Takashi Iwai <tiwai@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Mario Limonciello <mario.limonciello@dell.com>
Subject: Re: snd_hda_intel 0000:00:1f.3: No response from codec, resetting bus: last cmd=
Date: Mon, 04 Nov 2019 14:19:21 +0100	[thread overview]
Message-ID: <s5heeynwzhi.wl-tiwai@suse.de> (raw)
In-Reply-To: <20191104131024.GB2552@lahna.fi.intel.com>

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@lists.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

  reply	other threads:[~2019-11-04 13:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 12:57 snd_hda_intel 0000:00:1f.3: No response from codec, resetting bus: last cmd= Paul Menzel
2019-11-04 13:10 ` Mika Westerberg
2019-11-04 13:19   ` Takashi Iwai [this message]
2019-11-04 14:58     ` Mika Westerberg
2019-11-04 15:08       ` Takashi Iwai
2019-11-04 17:31 ` Tomas Janousek
2019-11-19 13:27   ` Paul Menzel

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=s5heeynwzhi.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=ck@xatom.net \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@dell.com \
    --cc=michael.jamet@intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=pmenzel@molgen.mpg.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).