mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: linux-serial@vger.kernel.or,
	open list <linux-kernel@vger.kernel.org>,
	lkft-triage@lists.linaro.org,
	Linux Regressions <regressions@lists.linux.dev>,
	linux-stable <stable@vger.kernel.org>,
	Jiri Slaby <jslaby@suse.com>,
	Aidan Stewart <astewart@tektelic.com>,
	Jakub Lewalski <jakub.lewalski@nokia.com>,
	Fabio Estevam <festevam@gmail.com>,
	Anders Roxell <anders.roxell@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Ben Copeland <benjamin.copeland@linaro.org>
Subject: Re: v6.16-rc5: ttys: auto login failed Login incorrect
Date: Wed, 9 Jul 2025 13:01:56 +0200	[thread overview]
Message-ID: <2025070924-slurp-monetary-a53f@gregkh> (raw)
In-Reply-To: <CA+G9fYtK2TLbpo-NE-KUXEp0y8+5zXNVRFkqdMjaGgcNFFG77g@mail.gmail.com>

On Wed, Jul 09, 2025 at 04:26:53PM +0530, Naresh Kamboju wrote:
> Approximately 20% of devices are experiencing intermittent boot failures
> with this kernel version. The issue appears to be related to auto login
> failures, where an incorrect password is being detected on the serial
> console during the login process.
> 
> This intermittent regression is noticed on stable-rc 6.15.5-rc2 and
> Linux mainline master v6.16-rc5. This regressions is only specific
> to the devices not on the qemu's.
> 
> Test environments:
>  - dragonboard-410c
>  - dragonboard-845c
>  - e850-96
>  - juno-r2
>  - rk3399-rock-pi-4b
>  - x86
> 
> Regression Analysis:
> - New regression? Yes
> - Reproducibility? 20% only
> 
> Test regression: 6.15.5-rc2 v6.16-rc5 auto login failed Login incorrect
> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> 
> ## log in problem
> 
> runner-ns46nmmj-project-40964107-concurrent-0 login: #
> Password:
> Login incorrect
> runner-ns46nmmj-project-40964107-concurrent-0 login:
> 
> ## Investigation
> The following three patches were reverted and the system was re-tested.
> The previously reported issues are no longer observed after applying the
> reverts.
> 
> serial: imx: Restore original RXTL for console to fix data loss
>     commit f23c52aafb1675ab1d1f46914556d8e29cbbf7b3 upstream.
> 
> serial: core: restore of_node information in sysfs
>     commit d36f0e9a0002f04f4d6dd9be908d58fe5bd3a279 upstream.
> 
> tty: serial: uartlite: register uart driver in init
>     [ Upstream commit 6bd697b5fc39fd24e2aa418c7b7d14469f550a93 ]


As stated before, those are 3 totally independent changes.  Any chance
you can nail this down to just one of the above?

thanks,

greg k-h

  reply	other threads:[~2025-07-09 11:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09 10:56 Naresh Kamboju
2025-07-09 11:01 ` Greg Kroah-Hartman [this message]
2025-07-09 12:25   ` Naresh Kamboju

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=2025070924-slurp-monetary-a53f@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=astewart@tektelic.com \
    --cc=benjamin.copeland@linaro.org \
    --cc=dan.carpenter@linaro.org \
    --cc=festevam@gmail.com \
    --cc=jakub.lewalski@nokia.com \
    --cc=jslaby@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.or \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®