linux-kernel - Re: PROBLEM: boot hang on Indy R4400SC (regression)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <e4ed75c7-b108-437f-b44b-69a9b340c085@app.fastmail.com>
Date: Fri, 07 Nov 2025 19:29:25 +0000
From: "Jiaxun Yang" <jiaxun.yang@...goat.com>
To: "Nick Bowler" <nbowler@...conx.ca>, linux-kernel@...r.kernel.org,
 regressions@...ts.linux.dev,
 "linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>
Cc: "stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: PROBLEM: boot hang on Indy R4400SC (regression)



On Fri, 7 Nov 2025, at 7:04 AM, Nick Bowler wrote:
> Hi,

Hi Nick,

Many thanks for the issue report! It's pretty rare to get reports from
hardware that old.

Unfortunately my Indy won't go over ARCS prom so I'm not in a position
to debug this on my side. I have inspected the code again and I can't
see anything preventing it to work on R4000 family.

Maybe we can revert this for non-MIPS64R1 system only so we can get something
working for both old and new systems.

#regzbot introduced: 35ad7e181541aa5757f9f316768d3e64403ec843

Thanks

>
> After a recent 6.1.y stable kernel update, my Indy (mips64 R4400SC) now
> just stops booting early, just before when I would normally see the
> kernel messages about mounting the root filesystem.
>
> There are no further messages of any kind, and the boot process does not
> appear to ever complete.  However, the kernel is not fully crashed, as
> it does respond to sysrq commands from the keyboard (and I do get output
> on the console from these).
>
> I bisected to the following:
>  
>     794b679a28bb59a4533ae39a7cf945b9d5bbe336 is the first bad commit
>     commit 794b679a28bb59a4533ae39a7cf945b9d5bbe336
>     Author: Jiaxun Yang <jiaxun.yang@...goat.com>
>     Date:   Sat Jun 7 13:43:56 2025 +0100
>    
>         MIPS: mm: tlb-r4k: Uniquify TLB entries on init
>    
>         commit 35ad7e181541aa5757f9f316768d3e64403ec843 upstream.
>
> This reverts cleanly on top of 6.1.158 and the resulting kernel boots
> normally.  I then reproduced this failure on 6.18-rc4.  Reverting
> 35ad7e181541 on top of 6.18-rc4 also results in a normal boot.
>
> Let me know if you need any more info!
>
> Thanks,
>   Nick

-- 
- Jiaxun