I ran a bisect back further while patching in f2bd1c5ae2cb0cf9525c9bffc0038c12dd7e1338.
When doing this, 3fd63658caed9494cca1d4789a66d3d2def2a0ab appears to be the commit in 6.1+ that it's interacting badly with. I couldn't revert this cleanly without reverting a handful of other commits, but doing so also results in working audio with 6.1.8 while leaving in f2bd1c5ae2cb. (e9441675edc1, 1cda83e42bf6, 37882100cd06, 0e213813df02, fb5987844808 were the others removed)
Hopefully that helps narrow it down for someone more familiar, otherwise I'll keep digging.
On Sat, Jan 28, 2023 at 7:23 PM Jason Montleon jmontleo@redhat.com wrote:
I have confirmed 6.2-rc5 is also broken and removing the same commit causes it to work again.
Thank you, Jason Montleon
On Sat, Jan 28, 2023 at 12:52 PM Greg KH gregkh@linuxfoundation.org wrote:
On Sat, Jan 28, 2023 at 12:09:54PM -0500, Jason Montleon wrote:
I did a bisect which implicated f2bd1c5ae2cb0cf9525c9bffc0038c12dd7e1338 as the first bad commit.
Reverting this commit on 6.1.8 gives me working sound again.
I'm not clear why this is breaking 6.1.x since it appears to be in 6.0.18 (7494e2e6c55e), which was the last working package in Fedora for the 6.0 line. Maybe something else didn't make it into 6.1?
So this is also broken in Linus's tree (6.2-rc5?)
thanks,
greg k-h
-- Jason Montleon | email: jmontleo@redhat.com Red Hat, Inc. | gpg key: 0x069E3022 Cell: 508-496-0663 | irc: jmontleo / jmontleon
-- Jason Montleon | email: jmontleo@redhat.com Red Hat, Inc. | gpg key: 0x069E3022 Cell: 508-496-0663 | irc: jmontleo / jmontleon