[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <84ldvcyq41.fsf@jogness.linutronix.de>
Date: Wed, 15 Jan 2025 18:00:38 +0106
From: John Ogness <john.ogness@...utronix.de>
To: Jon Hunter <jonathanh@...dia.com>, Greg Kroah-Hartman
<gregkh@...uxfoundation.org>
Cc: Jiri Slaby <jirislaby@...nel.org>, Petr Mladek <pmladek@...e.com>,
Sergey Senozhatsky <senozhatsky@...omium.org>, Steven Rostedt
<rostedt@...dmis.org>, Thomas Gleixner <tglx@...utronix.de>, Esben
Haabendal <esben@...nix.com>, linux-serial@...r.kernel.org,
linux-kernel@...r.kernel.org, Andy Shevchenko
<andriy.shevchenko@...ux.intel.com>, Arnd Bergmann <arnd@...db.de>, Tony
Lindgren <tony@...mide.com>, Niklas Schnelle <schnelle@...ux.ibm.com>,
Serge Semin <fancer.lancer@...il.com>, "linux-tegra@...r.kernel.org"
<linux-tegra@...r.kernel.org>
Subject: Re: [PATCH tty-next v5 5/6] serial: 8250: Switch to nbcon console
On 2025-01-15, Jon Hunter <jonathanh@...dia.com> wrote:
> I have noticed a suspend regression on -next for some of our 32-bit
> Tegra (ARM) devices (Tegra20, Tegra30 and Tegra124). Bisect is pointing
> to this commit and reverting this on top of -next (along with reverting
> "serial: 8250: Revert "drop lockdep annotation from
> serial8250_clear_IER()") fixes the issue. So far I have not dug in any
> further. Unfortunately, I don't have any logs to see if there is some
> crash or something happening but I will see if there is any more info I
> can get.
Do you at least know if it is failing to suspend or failing to resume
(based on power consumption)?
John
Powered by blists - more mailing lists