For bluhm and bugs@ readers, Eivind narrowed it down to between these:
OpenBSD 6.3-current (GENERIC) #567: Sun Apr 22 08:12:07 MDT 2018
[email protected]:/usr/src/sys/arch/i386/compile/GENERIC
OpenBSD 6.3-current (GENERIC) #568: Tue Apr 24 23:16:33 MDT 2018
[email protected]:/usr/src/sys/arch/i386/compile/GENERIC
> Got it. The kernel bsd.20180423.gz does not have the crash. The kernel
> bsd.20180426.gz have the crash.
On 2018/07/18 23:25, Eivind Eide wrote:
> 2018-07-18 23:04 GMT+02:00 Alexander Bluhm <[email protected]>:
> > On Wed, Jul 18, 2018 at 08:39:17PM +0200, Eivind Eide wrote:
> >> Over several snapshots after 6.3 I get reliable system crash after a
> >> few minutes uptime on this old i386 machine of mine.
> >
> > It would be helpful to know when this started. Does it happen with
> > 6.3? Since 6.3 we have commited i386 Meltdown protection in several
> > steps and the trapframe was reordered. We compile with retpoline
> > now. I am not aware of any tests on Pentium 4 processor. The stack
> > trace ends in gdt at 0, might be NULL pointer call. Active process
> > is systq.
> >
> > So either we need the snapshot date or cvs date when this started
> > or some access to ddb. The stack trace has to checked manually.
>
> It did not happen at the time of 6.3-release. It came later. However
> I'm not using that old machine much, so I tried a couple of snaps in
> the months to follow in hope that it would just go away.... Now I
> finally realised it's not going away and found time to report this.
> It might have been like a month after you went to -current again when
> I installed the first snap with this problem...?
> Sorry! I don't know any better.
> If there's any more info I can provide you must hold my hands. I'm not
> that technical...
>
>
> >
> > Does anybody else see something like this with a Pentium 4?
> >
> > bluhm
>
>
>
> --
>
>
>
> Eivind Eide
>
> "ONLY THOSE WHO ATTEMPT THE IMPOSSIBLE WILL ACHIEVE THE ABSURD"
> - Oceania Association of Autonomous Astronauts
>
