From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Nick Bowler <nbowler@draconx.ca>
Cc: Jiaxun Yang <jiaxun.yang@flygoat.com>,
linux-kernel@vger.kernel.org, regressions@lists.linux.dev,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: PROBLEM: boot hang on Indy R4400SC (regression)
Date: Mon, 10 Nov 2025 17:51:37 +0100 [thread overview]
Message-ID: <aRIYGUzHa-8U85Ei@alpha.franken.de> (raw)
In-Reply-To: <j5uutbx2oi2ccudo54o4hgxfmwfchwmd2ktig6xjgkqa7ho2pj@xb4luighppnc>
On Sat, Nov 08, 2025 at 03:02:17PM -0500, Nick Bowler wrote:
> On Fri, Nov 07, 2025 at 03:12:31PM -0500, Nick Bowler wrote:
> > On Fri, Nov 07, 2025 at 07:29:25PM +0000, Jiaxun Yang wrote:
> > > 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.
> >
> > I'll try adding some extra prints to at least figure out where it is
> > actually hanging.
>
> I did not have much success with adding prints, but looking more closely
> at the console output it seems that what is ultimately failing is the
> SCSI bus enumeration which does not complete unless I revert commit
> 35ad7e181541.
the problem is the tlb_probe() r4k_tlb_uniquify(), if the TLB contains
Index: 0 pgmask=4kb va=80000000 asid=00
[pa=00000000 c=0 d=0 v=0 g=0] [pa=00000000 c=0 d=0 v=0 g=0]
Index: 1 pgmask=4kb va=80000000 asid=00
[pa=00000000 c=0 d=0 v=0 g=0] [pa=00000000 c=0 d=0 v=0 g=0]
Index: 2 pgmask=4kb va=80000000 asid=00
[pa=00000000 c=0 d=0 v=0 g=0] [pa=00000000 c=0 d=0 v=0 g=0]
Index: 3 pgmask=4kb va=80000000 asid=00
[pa=00000000 c=0 d=0 v=0 g=0] [pa=00000000 c=0 d=0 v=0 g=0]
Index: 4 pgmask=4kb va=80000000 asid=00
[pa=00000000 c=0 d=0 v=0 g=0] [pa=00000000 c=0 d=0 v=0 g=0]
[...]
which is coming from the Indy PROM. I only tested this patch on an R5k
Indy and the R5000 CPU doesn't have a problem with this.
I'm working on a fix for this.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2025-11-10 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 7:04 PROBLEM: boot hang on Indy R4400SC (regression) Nick Bowler
2025-11-07 19:29 ` Jiaxun Yang
2025-11-07 20:12 ` Nick Bowler
2025-11-08 20:02 ` Nick Bowler
2025-11-10 16:51 ` Thomas Bogendoerfer [this message]
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=aRIYGUzHa-8U85Ei@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=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;
as well as URLs for NNTP newsgroup(s).