From: Alexander Sergeyev <sergeev917@gmail.com> To: Takashi Iwai <tiwai@suse.de> 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: Sat, 5 Feb 2022 18:00:16 +0300 [thread overview] Message-ID: <20220205150016.gvrst7ldvgjh7fra@localhost.localdomain> (raw) In-Reply-To: <s5htudk9cn3.wl-tiwai@suse.de> On Mon, Jan 31, 2022 at 03:57:04PM +0100, Takashi Iwai wrote: > > 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. > 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? I've built snd_hda_intel as a module, everything else is left built-in. The initial modprobe and rmmod were clean, but the subsequent modprobe gave IO_PAGE_FAULT. # modprobe snd-hda-intel snd_hda_intel 0000:05:00.1: bound 0000:05:00.0 (ops amdgpu_dm_audio_component_bind_ops) input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:08.1/0000:05:00.1/sound/card0/input24 input: HD-Audio Generic HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:08.1/0000:05:00.1/sound/card0/input25 input: HD-Audio Generic HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:08.1/0000:05:00.1/sound/card0/input26 input: HD-Audio Generic HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:08.1/0000:05:00.1/sound/card0/input27 snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC285: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker snd_hda_codec_realtek hdaudioC1D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) snd_hda_codec_realtek hdaudioC1D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0) snd_hda_codec_realtek hdaudioC1D0: mono: mono_out=0x0 snd_hda_codec_realtek hdaudioC1D0: inputs: snd_hda_codec_realtek hdaudioC1D0: Mic=0x19 snd_hda_codec_realtek hdaudioC1D0: Internal Mic=0x12 snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffff800 flags=0x0020]
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Sergeyev <sergeev917@gmail.com> To: Takashi Iwai <tiwai@suse.de> Cc: "moderated list:SOUND" <alsa-devel@alsa-project.org>, Kailang Yang <kailang@realtek.com>, Jeremy Szu <jeremy.szu@canonical.com>, Huacai Chen <chenhuacai@kernel.org>, open list <linux-kernel@vger.kernel.org>, tiwai@suse.com, Hui Wang <hui.wang@canonical.com>, PeiSen Hou <pshou@realtek.com>, Jian-Hong Pan <jhp@endlessos.org> Subject: Re: [PATCH 1/4] ALSA: hda/realtek: fix mute/micmute LEDs for HP 855 G8 Date: Sat, 5 Feb 2022 18:00:16 +0300 [thread overview] Message-ID: <20220205150016.gvrst7ldvgjh7fra@localhost.localdomain> (raw) In-Reply-To: <s5htudk9cn3.wl-tiwai@suse.de> On Mon, Jan 31, 2022 at 03:57:04PM +0100, Takashi Iwai wrote: > > 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. > 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? I've built snd_hda_intel as a module, everything else is left built-in. The initial modprobe and rmmod were clean, but the subsequent modprobe gave IO_PAGE_FAULT. # modprobe snd-hda-intel snd_hda_intel 0000:05:00.1: bound 0000:05:00.0 (ops amdgpu_dm_audio_component_bind_ops) input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:08.1/0000:05:00.1/sound/card0/input24 input: HD-Audio Generic HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:08.1/0000:05:00.1/sound/card0/input25 input: HD-Audio Generic HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:08.1/0000:05:00.1/sound/card0/input26 input: HD-Audio Generic HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:08.1/0000:05:00.1/sound/card0/input27 snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC285: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker snd_hda_codec_realtek hdaudioC1D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) snd_hda_codec_realtek hdaudioC1D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0) snd_hda_codec_realtek hdaudioC1D0: mono: mono_out=0x0 snd_hda_codec_realtek hdaudioC1D0: inputs: snd_hda_codec_realtek hdaudioC1D0: Mic=0x19 snd_hda_codec_realtek hdaudioC1D0: Internal Mic=0x12 snd_hda_intel 0000:05:00.6: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0x1fffff800 flags=0x0020]
next prev parent reply other threads:[~2022-02-05 14:54 UTC|newest] Thread overview: 66+ 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 ` 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 ` 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 ` 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-19 17:03 ` 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 2:00 ` Jeremy Szu 2021-05-27 6:14 ` Takashi Iwai 2021-05-27 6:14 ` Takashi Iwai 2022-01-11 19:52 ` Alexander Sergeyev 2022-01-11 19:52 ` Alexander Sergeyev 2022-01-12 9:45 ` Takashi Iwai 2022-01-12 9:45 ` Takashi Iwai 2022-01-12 10:12 ` Alexander Sergeyev 2022-01-12 10:12 ` Alexander Sergeyev 2022-01-12 10:13 ` Takashi Iwai 2022-01-12 10:13 ` Takashi Iwai 2022-01-12 10:48 ` Alexander Sergeyev 2022-01-12 10:48 ` Alexander Sergeyev 2022-01-12 20:18 ` Alexander Sergeyev 2022-01-12 20:18 ` Alexander Sergeyev 2022-01-13 7:14 ` Takashi Iwai 2022-01-13 7:14 ` Takashi Iwai 2022-01-13 18:31 ` Alexander Sergeyev 2022-01-13 18:31 ` Alexander Sergeyev 2022-01-13 21:19 ` Alexander Sergeyev 2022-01-13 21:19 ` Alexander Sergeyev 2022-01-14 16:37 ` Takashi Iwai 2022-01-14 16:37 ` Takashi Iwai 2022-01-14 18:37 ` Alexander Sergeyev 2022-01-14 18:37 ` Alexander Sergeyev 2022-01-15 7:55 ` Takashi Iwai 2022-01-15 7:55 ` Takashi Iwai 2022-01-15 15:22 ` Alexander Sergeyev 2022-01-15 15:22 ` Alexander Sergeyev 2022-01-19 9:12 ` Takashi Iwai 2022-01-19 9:12 ` Takashi Iwai 2022-01-19 9:32 ` Alexander Sergeyev 2022-01-19 9:32 ` Alexander Sergeyev 2022-01-22 19:05 ` Alexander Sergeyev 2022-01-22 19:05 ` Alexander Sergeyev 2022-01-22 20:56 ` Alexander Sergeyev 2022-01-22 20:56 ` Alexander Sergeyev 2022-01-26 15:24 ` Takashi Iwai 2022-01-26 15:24 ` Takashi Iwai 2022-01-29 14:47 ` Alexander Sergeyev 2022-01-29 14:47 ` Alexander Sergeyev 2022-01-30 11:10 ` Alexander Sergeyev 2022-01-30 11:10 ` Alexander Sergeyev 2022-01-31 14:57 ` Takashi Iwai 2022-01-31 14:57 ` Takashi Iwai 2022-02-05 15:00 ` Alexander Sergeyev [this message] 2022-02-05 15:00 ` Alexander Sergeyev 2022-02-05 17:51 ` Alexander Sergeyev 2022-02-05 17:51 ` Alexander Sergeyev 2022-02-07 14:21 ` Takashi Iwai 2022-02-07 14:21 ` Takashi Iwai 2022-02-08 19:49 ` Alexander Sergeyev 2022-02-08 19:49 ` Alexander Sergeyev 2022-02-08 14:36 ` Takashi Iwai 2022-02-08 14:36 ` Takashi Iwai 2022-02-08 19:52 ` Alexander Sergeyev 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=20220205150016.gvrst7ldvgjh7fra@localhost.localdomain \ --to=sergeev917@gmail.com \ --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=tiwai@suse.com \ --cc=tiwai@suse.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: linkBe 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.