From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: John Ogness <john.ogness@linutronix.de>
Cc: kernel test robot <oliver.sang@intel.com>,
oe-lkp@lists.linux.dev, lkp@intel.com,
Petr Mladek <pmladek@suse.com>,
linux-serial@vger.kernel.org
Subject: Re: [linux-next:master] [serial] b63e6f60ea: BUG:soft_lockup-CPU##stuck_for#s![modprobe:#]
Date: Wed, 22 Jan 2025 10:37:03 +0100 [thread overview]
Message-ID: <2025012240-creatable-defective-d713@gregkh> (raw)
In-Reply-To: <84wmenqm03.fsf@jogness.linutronix.de>
On Wed, Jan 22, 2025 at 09:47:00AM +0106, John Ogness wrote:
> Hi Greg,
>
> On 2025-01-22, kernel test robot <oliver.sang@intel.com> wrote:
> > kernel test robot noticed "BUG:soft_lockup-CPU##stuck_for#s![modprobe:#]" on:
> >
> > commit: b63e6f60eab45b16a1bf734fef9035a4c4187cd5 ("serial: 8250: Switch to nbcon console")
> > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>
> It looks like we need to revert this commit (and the one after it) until
> I can find out what is going on here.
>
> >From linux-next they are:
>
> b63e6f60eab4 serial: 8250: Switch to nbcon console
>
> 422c9727b07f serial: 8250: Revert "drop lockdep annotation from serial8250_clear_IER()"
Ok, now reverted, thanks for finding the offending commits.
> I hope to get this solved soon, but I am currently taking part in a Rust
> training, which does not leave me many extra brain cycles at the moment.
Totally understood :)
thanks,
greg k-h
next prev parent reply other threads:[~2025-01-22 9:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 2:28 [linux-next:master] [serial] b63e6f60ea: BUG:soft_lockup-CPU##stuck_for#s![modprobe:#] kernel test robot
2025-01-22 8:41 ` John Ogness
2025-01-22 9:37 ` Greg Kroah-Hartman [this message]
2025-01-24 16:10 ` Petr Mladek
2025-01-24 16:39 ` Petr Mladek
2025-03-15 3:38 ` Ryo Takakura
2025-03-17 8:45 ` John Ogness
2025-03-17 14:42 ` Ryo Takakura
2025-04-21 3:41 ` Ryo Takakura
2025-04-22 12:15 ` Petr Mladek
2025-04-22 14:03 ` John Ogness
2025-04-24 8:11 ` Ryo Takakura
2025-04-24 9:00 ` John Ogness
2025-04-24 14:13 ` Ryo Takakura
2025-04-24 9:02 ` Petr Mladek
2025-04-24 14:17 ` Ryo Takakura
2025-04-30 9:15 ` Ryo Takakura
2025-04-30 15:41 ` John Ogness
2025-05-01 4:10 ` Ryo Takakura
2025-06-16 15:15 ` Florian Bezdeka
2025-06-18 4:42 ` John Ogness
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=2025012240-creatable-defective-d713@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=john.ogness@linutronix.de \
--cc=linux-serial@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=pmladek@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;
as well as URLs for NNTP newsgroup(s).