From: Matthieu Baerts <matttbe@kernel.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com
Subject: Re: [matttbe-net-next:gh-issue-617-stalls-starting-vsock] [sched/mmcid] 5e4b47fd15: BUG:soft_lockup-CPU##stuck_for#s![make:#]
Date: Fri, 13 Mar 2026 09:51:02 +0100 [thread overview]
Message-ID: <bf7f1085-ddd1-4f42-aad3-cec1922bde77@kernel.org> (raw)
In-Reply-To: <202603131533.347f08fb-lkp@intel.com>
Hello,
On 13/03/2026 09:11, kernel test robot wrote:
> kernel test robot noticed "BUG:soft_lockup-CPU##stuck_for#s![make:#]" on:
>
> commit: 5e4b47fd150c2ab74396945eae895ed419505daa ("Revert "sched/mmcid: Switch over to the new mechanism"")
> https://git.kernel.org/cgit/linux/kernel/git/matttbe/net-next.git gh-issue-617-stalls-starting-vsock
Thank you for the bug report. A newer version exists without this issue:
https://lore.kernel.org/all/20260310201009.257617049@kernel.org
Applied in tip: sched/urgent
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2026-03-13 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 8:11 [matttbe-net-next:gh-issue-617-stalls-starting-vsock] [sched/mmcid] 5e4b47fd15: BUG:soft_lockup-CPU##stuck_for#s![make:#] kernel test robot
2026-03-13 8:51 ` Matthieu Baerts [this message]
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=bf7f1085-ddd1-4f42-aad3-cec1922bde77@kernel.org \
--to=matttbe@kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.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 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.