On Tue, May 13, 2025 at 02:28:08PM +0200, Martin Pieuchot wrote:
> On 13/05/25(Tue) 13:57, Jeremie Courreges-Anglas wrote:
[...]
> > The sparc64 LDOM went into two panics - I somehow managed to break it
> > out of ddb after the first panic due to bogus conserver.  The data
> > below is minimal, sorry, I didn't recover the full trace from dmesg
> > after the 1st panic, and 'mach ddbcpu 0' locked up during the 2nd
> > panic.
> 
> I wonder if sparc64's pmap is in need for some love...
> 
> > 
> > I had not run a sparc64 bulk build on this machine in the recent
> > months, and I don't know whether both panics are related to your diff,
> > but I'll do my best to try and reproduce them.  Currently I've
> > restarted the bulk build without the uvm change. Maybe someone with
> > more sparc64 knowledge will bring some clue here.
> 
> Please let me know.

I can already tell that this LDOM ran the rest of the bulk with the
parallel uvm fault diff reverted...  Now restarting another build from
scratch, with your diff on top of -current.

> You can also start by "ps /o" or "show proc".

Hopefully that will be enough!  mach ddbcpu x didn't seem very usable.

-- 
jca