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.
So I presume that is why I also don't see the messages about mounting the root filesystem (I suppose it is just waiting for a disk).
I see the drivers printing the usual info about each device, but not everything. Specifically, the lines that are missing are all of these ones that would normally be printed:
sda: sda1 sda2 sda9 sda11 sd 0:0:1:0: [sda] Attached SCSI disk
sdb: sdb1 sdb9 sdb11 sd 0:0:2:0: [sdb] Attached SCSI disk
sr 0:0:5:0: Attached scsi CD-ROM sr0
Other than that everything else seems alive. Several other drivers go through their initialization during the time the SCSI stuff is not completing. The 'random: crng init done' message is printed after a while too.
I tried enabling CONFIG_SOFTLOCKUP_DETECTOR and CONFIG_WQ_WATCHDOG to get some more information out but these options do not seem to do anything in this scenario, nothing is printed even after ~10 minutes.
Thanks, Nick