Re: bin/50350: rump/rumpkern/t_sp/stress_{long,short} fail on Core 2 Quad

[Andreas Gustafsson <gson%gson.org@localhost>]

The following reply was made to PR bin/50350; it has been noted by GNATS.

From: Andreas Gustafsson <gson%gson.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: hannken%NetBSD.org@localhost
Subject: Re: bin/50350: rump/rumpkern/t_sp/stress_{long,short} fail on Core 2 Quad
Date: Thu, 7 Mar 2019 10:12:46 +0200

 I did another bisection in an alternate reality where the build was
 not broken on 2019.03.01.08.15.23, by patching the affected version
 so that they built.  This narrowed down the point where the tests
 started failing to the following commit:
 
   2019.03.01.09.02.03 hannken src/sys/kern/kern_exit.c 1.274
   2019.03.01.09.02.03 hannken src/sys/kern/kern_lwp.c 1.196
   2019.03.01.09.02.03 hannken src/sys/kern/vfs_trans.c 1.57
   2019.03.01.09.02.03 hannken src/sys/sys/fstrans.h 1.13
   2019.03.01.09.02.03 hannken src/sys/sys/lwp.h 1.181
 
 Given the history of these test failures (that they have been failing
 on i386 since 2013, are not failing in qemu, and mysteriously stopped
 failing on amd64 for me at one point), I figure this is probably not a
 case of the above commit introducing a new bug or being incorrect as
 such, but rather somehow retriggering the existing bug.  Perhaps the
 nature of the changes in the commit might offer some clue as to what
 that bug is.
 -- 
 Andreas Gustafsson, gson%gson.org@localhost