On Wed, Jul 09, 2025 at 02:54:03AM +0530, Naresh Kamboju wrote:
On Tue, 8 Jul 2025 at 00:04, Naresh Kamboju naresh.kamboju@linaro.org wrote:
On Sun, 6 Jul 2025 at 15:50, Naresh Kamboju naresh.kamboju@linaro.org wrote:
On Fri, 4 Jul 2025 at 20:14, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 6.15.5 release. There are 263 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Sun, 06 Jul 2025 12:55:09 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at: https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.15.5-rc2.... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.15.y and the diffstat can be found below.
thanks,
greg k-h
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.
Reported issue is also noticed on Linux tree 6.16-rc5 build.
We are investigating this problem.
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 ]
Reference bug report lore link,
As these are upstream, and causing the problem there too, can you email the tty list about them? And those are 2 different serial drivers, and one serial core change, all independant, which feels odd that they all were needed to fix this issue.
thanks,
greg k-h