mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Nick Bowler" <nbowler@draconx.ca>,
	linux-kernel@vger.kernel.org, regressions@lists.linux.dev,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: PROBLEM: boot hang on Indy R4400SC (regression)
Date: Fri, 07 Nov 2025 19:29:25 +0000	[thread overview]
Message-ID: <e4ed75c7-b108-437f-b44b-69a9b340c085@app.fastmail.com> (raw)
In-Reply-To: <g3scb7mfjbsohdszieqkappslj6m7qu3ou766nckt2remg3ide@izgvehzcdbsu>



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@flygoat.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

  reply	other threads:[~2025-11-07 19:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-07  7:04 Nick Bowler
2025-11-07 19:29 ` Jiaxun Yang [this message]
2025-11-07 20:12   ` Nick Bowler
2025-11-08 20:02     ` Nick Bowler
2025-11-10 16:51       ` Thomas Bogendoerfer

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=e4ed75c7-b108-437f-b44b-69a9b340c085@app.fastmail.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=nbowler@draconx.ca \
    --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®