Re: SGI O2 unable to boot 9.0+ (status update)

[Mike Shields <mike%shieldsworld.com@localhost>]

On Jun 24, 2024, at 1:20 PM, Andrius V <vezhlys%gmail.com@localhost> wrote:
> 
> On Mon, Jun 24, 2024 at 7:10 PM Mike Shields <mike%shieldsworld.com@localhost> wrote:
>> 
>> I’ll follow Warner’s suggestion and start with 8.3 + some interval and see if I can find the breaking point.
>> 
> 
> Yes, that's one of the ways to try to identify at least the commit
> causing the issue, but might be a bit tedious exercise. I would
> suggest to put old kernel to the new image and see if it still boots
> to rule out some bootloader issues (not sure how sgimips works here,
> but had experience with x86 then the problem was a bootloader, not a
> kernel). You can follow sys/sys/param.h 8.99.x version commits for
> example (between one version can be lots of commits but, it may help
> to narrow the search).

Just thought I’d give a status update on the attempts to get R5k/R10k IP32 sgimips back to life:

I was able to find the point via bisection, only took about 9 or 10 iterations. On the freebsd-8 branch, the failure starts between 2018-03-07 and 2018-03-08 (a build of 03-97 boots fine, a build of 03-08 freezes after a few lines). 

I have been sifting through the changes, and am finding some updates in src/sys/arch/mips/mips/locore.S to be the most suspicious.

I am not familiar with R5k/R10k core setup steps, so I’m just fooling around in the dark for now, testing various reversions in that file, but with no success so far.

I’ll keep plugging away, but if any other interested eyes have more familiarity, feel free to bail me out of these depths! ;-)