From: Takashi Iwai <tiwai@suse.de>
To: Harin Lee <me@harin.net>
Cc: Takashi Iwai <tiwai@suse.de>,
Thorsten Leemhuis <regressions@leemhuis.info>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Linux kernel regressions list <regressions@lists.linux.dev>,
Linux Sound System <linux-sound@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
stoa@gmx.us
Subject: Re: [regression] ctxfi: no speaker output when headphones connected on >=7.0.x
Date: Thu, 07 May 2026 08:30:55 +0200 [thread overview]
Message-ID: <87v7czrasg.wl-tiwai@suse.de> (raw)
In-Reply-To: <7929c116-ff2e-413b-ae73-e7d19e846e0f@harin.net>
On Thu, 07 May 2026 00:06:11 +0200,
Harin Lee wrote:
>
> On 5/6/26 4:05 PM, Takashi Iwai wrote:
> > On Wed, 06 May 2026 08:24:36 +0200,
> > Thorsten Leemhuis wrote:
> >>
> >> Hi! Just FYI, I noticed a regression report in bugzilla:
> >>
> >> https://bugzilla.kernel.org/show_bug.cgi?id=221461
> >>
> >> To quote:
> >>
> >>> Dutch Ingraham 2026-05-03 18:12:49 UTC
> >>>
> >>> Kernels >=7.0.1 contain a regression as to Creative Sound Blaster Z SE
> >>> discrete pci sound card, but not integrated. Kernels 7.0.1, 7.0.2, and
> >>> 7.0.3 tested; 7.0.0 not tested. Reverting to any 6.18.x or 6.12.x does
> >>> not present the issue.
> >>>
> >>> Specifically, using pipewire managed by pavucontrol, on both Gentoo and
> >>> Arch Linux, when both external speakers and headphones are connected,
> >>> all sound is routed through the headphones regardless of whether settings
> >>> are set to Line Out/Speaker or Line Out/Headphones; there is no speaker
> >>> output. If headphones are disconnected, without reboot, speakers work;
> >>> reconnect headphones, without reboot, sound reverts to headphones.
> >>>
> >>> Kernel: 7.0.3, Gentoo compiled from source using olddefconfig on 6.18.24
> >>> .config; Arch standard release
> >>> 'lspci -nnk | grep -i audio' attached
> >>> 'dmesg | grep -i audio' for 7.0.3 and 6.18.24 attached
> >>> pipewire-1.6.4 on both Gentoo and Arch Linux
> >>> alsa-firmware-1.2.4 on both Gentoo and Arch Linux
> >>> 'cat /proc/sys/kernel/tainted' returns 0 for both Gentoo and Arch Linux
> >>>
> >>> Processor : AMD Ryzen7 5700G
> >>> Motherboard : Asus Prime X570-Pro
> >>> RAM : Patriot Viper Steel DDR-4 @3200mHz
> >>> Graphics : ASRock AMD Radeon RX 7600 Challenger 8GB OC
> >>> Sound Card : Creative Sound Blaster Z SE
> >>>
> >>>
> >>> Expected outcome: ability to choose output to either speakers or head-
> >>> phones while both are plugged-in to sound card.
> >>>
> >>> Workaround: none known.
> >>
> >> See the ticket for more details. One of them: 7.1-rc2 is affected as
> >> well. Reporter is CCed. Forwarded this to ensure this report makes it to
> >> the interested parties, as bugzilla might not have forwarded this.
> >>
> >> Dutch Ingraham: if nobody within a few days has an idea why this
> >> happens, you will likely have to use a git bisection to get this resolved.
> >
> > As there have been many significant changes in ctxfi since 6.18, it's
> > hard to tell what broke. Please go git bisect.
> >
> >
> > thanks,
> >
> > Takashi
> >
>
> Creative Sound Blaster Z-series uses the snd_hda_codec_ca0132 driver,
> not snd_ctxfi. The dmesg logs in the bugzilla shows only ca0132
> entries.
Ah, sorry, then it's easier. The only major change is the
commit 778031e1658d206a52bf9491c91ae5d4f4a2509d
ALSA: hda/ca0132: Set HP/Speaker auto-detect default from headphone pin verb
Try to revert this one.
thanks,
Takashi
next prev parent reply other threads:[~2026-05-07 6:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 6:24 [regression] ctxfi: no speaker output when headphones connected on >=7.0.x Thorsten Leemhuis
2026-05-06 7:05 ` Takashi Iwai
2026-05-06 22:06 ` Harin Lee
2026-05-07 6:30 ` Takashi Iwai [this message]
2026-05-07 12:47 ` Dutch Ingraham
2026-05-07 13:24 ` Takashi Iwai
[not found] ` <CAFTm+6Bj_dWdSifUoS7hZ3kfVambXK_=7jyGuHp33RZoSEGVUA@mail.gmail.com>
2026-05-07 15:05 ` Matt DeVillier
2026-05-07 15:07 ` Takashi Iwai
2026-05-07 15:12 ` Matt DeVillier
2026-05-07 18:23 ` Dutch Ingraham
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=87v7czrasg.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=me@harin.net \
--cc=perex@perex.cz \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=stoa@gmx.us \
--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