Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <s5hbl7li0fe.wl-tiwai@suse.de> <CAHk-=wiTwX5mzzEcw3jk3QdW600Hntt=Ehgoyz8K-VU8zbEmBg@mail.gmail.com>
In-Reply-To: <CAHk-=wiTwX5mzzEcw3jk3QdW600Hntt=Ehgoyz8K-VU8zbEmBg@mail.gmail.com>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri, 2 Jul 2021 21:37:46 -0700
Message-ID: <CAHk-=whhDWDsVz12mhKtnS6DG-GzVWxBk2XjoOp=gwNJ7T0bTw@mail.gmail.com>
Subject: Re: [GIT PULL] sound updates for 5.14-rc1
To:     Takashi Iwai <tiwai@suse.de>
Cc:     Mark Brown <broonie@kernel.org>,
        Liam Girdwood <lgirdwood@gmail.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Fri, Jul 2, 2021 at 6:36 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> After incorrectly suspecting Andrew's -mm tree (because the kernel
> hung with a watchdog on TLB flushing, and so I suspected mm problems),
> I've now bisected my hung machine into the sound tree.

Hmm. One more step to go, but I think the culprit is comit
9ce650a75a3b ("ALSA: usb-audio: Reduce latency at playback start").
Because I don't think it can be the other choice.

Will finish the bisect (this took much too long, partly due to an
annoying F34 bug that makes all the boots take forever). And then go
back and verify that a revert fixes it on the current tip too.

But I thought I'd report this as a likely candidate.

          Linus