From: John Ogness <john.ogness@linutronix.de>
To: Ryo Takakura <ryotkkr98@gmail.com>, pmladek@suse.com
Cc: Jason@zx2c4.com, gregkh@linuxfoundation.org,
linux-serial@vger.kernel.org, lkp@intel.com,
oe-lkp@lists.linux.dev, oliver.sang@intel.com,
ryotkkr98@gmail.com
Subject: Re: [linux-next:master] [serial] b63e6f60ea: BUG:soft_lockup-CPU##stuck_for#s![modprobe:#]
Date: Thu, 24 Apr 2025 11:06:23 +0206 [thread overview]
Message-ID: <84r01i0w9k.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20250424081101.110914-1-ryotkkr98@gmail.com>
On 2025-04-24, Ryo Takakura <ryotkkr98@gmail.com> wrote:
>> By other words, the rslib test should get fixed by adding
>> cond_resched(). And the conversion of the 8250 serial console
>> driver to nbcon is correct.
>
> I see, and agree! I'll test what's discussed here so that we can say
> the above statement is true and the John's series can be brought back.
I'm looking forward to seeing your test results. Note there is also 2
more issues blocking the series:
https://lore.kernel.org/linux-serial/80b020fc-c18a-4da4-b222-16da1cab2f4c@nvidia.com/
and an offlist report from NXP relating to not being able to suspend on
ARMv8 due to printk irq work IPIs.
John
next prev parent reply other threads:[~2025-04-24 9:00 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
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 [this message]
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=84r01i0w9k.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=Jason@zx2c4.com \
--cc=gregkh@linuxfoundation.org \
--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 \
--cc=ryotkkr98@gmail.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).