I've had similar issues [1] in the past with apu1d4. It seemed it was collectd that was the culprit, but I've been running with bsd.sp since as a workaround. I want to try the next release when it comes out because I saw quite a lot of diffs regarding mp/locks/multi-thread. Who knows, maybe it was fixed :)
Dani [1] - https://marc.info/?l=openbsd-bugs&m=157080005817280&w=2 ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, April 11, 2020 2:20 PM, <[email protected]> wrote: > The pre-dawn daily digest > Volume 1 : Issue 5555 : "text" Format > > Messages in this Issue: > Re: [pc engines apu1d4] kernel crash periodically > > Date: Fri, 10 Apr 2020 14:03:50 +0200 > From: Martin Pieuchot [email protected] > To: Pascal Cabaud [email protected] > Cc: [email protected] > Subject: Re: [pc engines apu1d4] kernel crash periodically > Message-ID: [email protected] > > On 10/04/20(Fri) 12:18, Pascal Cabaud wrote: > > > Hello Martin, > > Thanks for searching bits in this bug report. Are the APU really popular > > to run OpenBSD or is there a problem with them: AFAICS, i've found many > > reports in archives... > > The problem is unlikely to be related to the hardware. > > > Le 2020-04-10 09:58, Martin Pieuchot disait : > > > > > Thanks for the report. This looks to me like a memory corruption in > > > the kernel. This is hard to understand because the panic(9) only show > > > the symptom, not the actual bug. > > > > Ok, I'm recording console with GNU Screen. Let's wait... > > To play with daemons, it'll be more difficult, i've to find backup > > hardware first. > > I understand, however wouldn't be surprised if the issue is exposed by > one of the daemon doing a lot of stuff and dealing with network, relayd > or collectd maybe.
