> From: Vitaliy Makkoveev <[email protected]> > Date: Tue, 7 Jul 2020 01:34:33 +0300 > > > On 5 Jul 2020, at 20:31, Paul Irofti <[email protected]> wrote: > > > > On Fri, Jul 03, 2020 at 06:36:39PM +0300, Paul Irofti wrote: > >> > >> > >> În 3 iulie 2020 17:55:25 EEST, Mark Kettenis <[email protected]> a > >> scris: > >>>> Date: Fri, 3 Jul 2020 15:13:22 +0200 > >>>> From: Robert Nagy <[email protected]> > >>>> > >>>> On 02/07/20 00:31 +0100, Stuart Henderson wrote: > >>>>> running on 38 of these, btw. > >>>> > >>>> been running with this on all my workstations and laptops and on 3 > >>> build > >>>> servers as well > >>> > >>> Are the issue that naddy@ saw solved? > >>> > >>> Did anybody do a *proper* test on anything besides amd64? Especially > >>> on architectures where the optimized clock_gettime is *not* available? > >> > >> Yes and yes. > > > > So, can we go ahead with this? > > > > Sorry for late reaction. At least VirtualBox based virtual machines > started to panic with the recent kernel. I reverted your diff and > panics stopped.
Should already be fixed.
