From: Takashi Iwai <tiwai@suse.de>
To: Alexander Sergeyev <sergeev917@gmail.com>
Cc: Jeremy Szu <jeremy.szu@canonical.com>,
tiwai@suse.com,
"moderated list:SOUND" <alsa-devel@alsa-project.org>,
Kailang Yang <kailang@realtek.com>,
open list <linux-kernel@vger.kernel.org>,
Huacai Chen <chenhuacai@kernel.org>,
Jian-Hong Pan <jhp@endlessos.org>,
Hui Wang <hui.wang@canonical.com>, PeiSen Hou <pshou@realtek.com>
Subject: Re: [PATCH 1/4] ALSA: hda/realtek: fix mute/micmute LEDs for HP 855 G8
Date: Mon, 31 Jan 2022 15:57:04 +0100 [thread overview]
Message-ID: <s5htudk9cn3.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220130111020.44gzrm5ckrakjta2@localhost.localdomain>
On Sun, 30 Jan 2022 12:10:20 +0100,
Alexander Sergeyev wrote:
>
> On Sat, Jan 29, 2022 at 05:47:07PM +0300, Alexander Sergeyev wrote:
> > But unbind-bind problems with IO_PAGE_FAULT and "out of range cmd" are not
> > eliminated. IO_PAGE_FAULT are often logged without accompanying "out of range
> > cmd". And after adding debugging printk() I haven't managed to trigger "out
> > of range cmd" yet. But IO_PAGE_FAULT are more easily triggered.
>
> IO_PAGE_FAULTs go away with CONFIG_IOMMU_DEFAULT_PASSTHROUGH enabled. As I
> understand, this leads to reduced DMA device isolation which is generally not
> desirable. I was initially thinking about races between some delayed code and
> io-memory pages unmapping, but first IO_PAGE_FAULTs (running non-passthrough
> iommu) happen during bind operations as well.
That's logical, as IOMMU is bypassed for DMA with that option.
I still don't get what really triggers it. This won't happen when you
build modules and load/unload the driver instead of dynamic binding?
And the out-of-range access is puzzling, too. I guess this comes from
the update of a COEF, i.e. it reads a strange value and tries to
update the value based on it. The problem is that it's no -1 but some
random value. This might be tied with the IOMMU error, and it might
reading unexpected address, which would be really bad.
In anyway, we need to track down exactly which access triggers those
errors...
> What is also interesting, unbind & bind consistently fails on 31th bind:
>
> echo -n '0000:05:00.6' > /sys/bus/pci/drivers/snd_hda_intel/bind
> -bash: echo: write error: No such device
>
> And does not recover from there until a reboot.
This is intended behavior. The driver has a static device index that
is incremented at each probe, so that the driver may probe multiple
instances. It'll be tricky to reset this for dynamic binding,
though. This problem is not only for HD-audio but for most of other
drivers. But I leave this as is for now, since the dynamic binding is
rarely used for PCI and other buses, so far.
Takashi
next prev parent reply other threads:[~2022-01-31 14:57 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 17:03 [PATCH 1/4] ALSA: hda/realtek: fix mute/micmute LEDs for HP 855 G8 Jeremy Szu
2021-05-19 17:03 ` [PATCH 2/4] ALSA: hda/realtek: fix mute/micmute LEDs and speaker for HP Zbook G8 Jeremy Szu
2021-05-19 17:03 ` [PATCH 3/4] ALSA: hda/realtek: fix mute/micmute LEDs and speaker for HP Zbook Fury 15 G8 Jeremy Szu
2021-05-19 17:03 ` [PATCH 4/4] ALSA: hda/realtek: fix mute/micmute LEDs and speaker for HP Zbook Fury 17 G8 Jeremy Szu
2021-05-27 2:00 ` [PATCH 1/4] ALSA: hda/realtek: fix mute/micmute LEDs for HP 855 G8 Jeremy Szu
2021-05-27 6:14 ` Takashi Iwai
2022-01-11 19:52 ` Alexander Sergeyev
2022-01-12 9:45 ` Takashi Iwai
2022-01-12 10:12 ` Alexander Sergeyev
2022-01-12 10:13 ` Takashi Iwai
2022-01-12 10:48 ` Alexander Sergeyev
2022-01-12 20:18 ` Alexander Sergeyev
2022-01-13 7:14 ` Takashi Iwai
2022-01-13 18:31 ` Alexander Sergeyev
2022-01-13 21:19 ` Alexander Sergeyev
2022-01-14 16:37 ` Takashi Iwai
2022-01-14 18:37 ` Alexander Sergeyev
2022-01-15 7:55 ` Takashi Iwai
2022-01-15 15:22 ` Alexander Sergeyev
2022-01-19 9:12 ` Takashi Iwai
2022-01-19 9:32 ` Alexander Sergeyev
2022-01-22 19:05 ` Alexander Sergeyev
2022-01-22 20:56 ` Alexander Sergeyev
2022-01-26 15:24 ` Takashi Iwai
2022-01-29 14:47 ` Alexander Sergeyev
2022-01-30 11:10 ` Alexander Sergeyev
2022-01-31 14:57 ` Takashi Iwai [this message]
2022-02-05 15:00 ` Alexander Sergeyev
2022-02-05 17:51 ` Alexander Sergeyev
2022-02-07 14:21 ` Takashi Iwai
2022-02-08 19:49 ` Alexander Sergeyev
2022-02-08 14:36 ` Takashi Iwai
2022-02-08 19:52 ` Alexander Sergeyev
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=s5htudk9cn3.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=chenhuacai@kernel.org \
--cc=hui.wang@canonical.com \
--cc=jeremy.szu@canonical.com \
--cc=jhp@endlessos.org \
--cc=kailang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pshou@realtek.com \
--cc=sergeev917@gmail.com \
--cc=tiwai@suse.com \
/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