From: Linus Torvalds <torvalds@linux-foundation.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] sound fixes for 6.1-rc5
Date: Fri, 11 Nov 2022 17:28:19 -0800 [thread overview]
Message-ID: <CAHk-=wgSH5ubdvt76gNwa004ooZAEJL_1Q-Fyw5M2FDdqL==dg@mail.gmail.com> (raw)
In-Reply-To: <87fsepx42m.wl-tiwai@suse.de>
On Fri, Nov 11, 2022 at 12:56 AM Takashi Iwai <tiwai@suse.de> wrote:
>
> please pull sound fixes for v6.1-rc5 from:
Hmm. I don't know that this came in through this particular pull
request, but I don't seem to have seen it before:
Nov 11 14:32:37 xps13 kernel:
snd_hda_intel 0000:00:1f.3: Too many BDL entries:
buffer=2097152, period=65536
there's six of those lines in my logs (two batches of three, five
seconds apart).
I don't see any negative side effects aside from the messages, and
sound seems to work fine, but since I don't think I've ever seen this
one before I thought I'd just mention it.
I also haven't been using this laptop on a while - an arm64 Fedora
uboot update broke my M2 boot, so I'm temporarily back to using my
trusty old xps13.
So while it's new to me, the issue that introduced it may not be
particularly new.
Google does show that the message itself has been happening for others
for a long time. But I checked with 'journalctl', and it hasn't
happened on this particular machine before.
It might be a non-kernel change that triggers it, of course.
Linus
next prev parent reply other threads:[~2022-11-12 1:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 8:56 [GIT PULL] sound fixes for 6.1-rc5 Takashi Iwai
2022-11-11 18:03 ` pr-tracker-bot
2022-11-12 1:28 ` Linus Torvalds [this message]
2022-11-12 8:46 ` Takashi Iwai
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='CAHk-=wgSH5ubdvt76gNwa004ooZAEJL_1Q-Fyw5M2FDdqL==dg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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: link
Be 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.