Hello all, thanks even once more for the support, you people are truly great! I will have access to the machine in the second part of the day and will for sure give it a spin! And of course, if all works out, then of course I will provide you with a dmesg of the successful start. I will definitely keep you posted! Best wishes,
Stefan On Mon, June 13, 2022 11:08 pm, Patrick Wildt wrote: > Am Mon, Jun 13, 2022 at 07:44:24PM +0200 schrieb Mark Kettenis: > >>> From: kiltz <[email protected]> >>> Date: Mon, 13 Jun 2022 18:12:27 +0200 >>> >>> >>> Dear Mark, >>> first of all, thank you very much for your explainations, the diff and, >>> indeed, the ultra swift reply! That helps us a lot already. >>> A snapshot with a higher value of max CPUs out of the box, of course, >>> would be the proverbial icing on the cake. Probably a strange question >>> but I hazard it anyways - should we monitor the snapshot directory the >>> /pub/OpenBSD/snapshots folder or is >>> there a quicker way to find out what your fellow developers think? >>> Again, many thanks for your help and best wishes, >>> >> >> Hi Stefan, >> >> >> Theo put that diff in snaphots. I suspect that tomorrow's snapshot >> will have it. You can easily tell, since all 80 CPUs should attach with >> that diff. >> >> Cheers, >> >> >> Mark >> > > And it's nice to hear that SP install already worked. I remember > booting it up on an Oracle machine with an Ampere Altra which led to > messages like > > agintcmsi0 at agintc0: unsupported type 0x0000001700026f31 > > See http://ix.io/3GEX > > > While I had a diff somewhere to 'fix that', I never got the timer > interrupt to fire. > > That you already had an SP install means all that should be fine. > If this change/new snap works, I'd be interested to read a full > dmesg! > > Cheers, > Patrick > >
