On Sat, Jun 19, 2021 at 12:31 PM Colin Ian King <colin.king@xxxxxxxxxxxxx> wrote: > > Hi, > > I suspect this issue was fixed with the following commit: > > commit e5e8b80d352ec999d2bba3ea584f541c83f4ca3f > Author: Rob Gardner <rob.gardner@xxxxxxxxxx> > Date: Sun Feb 28 22:48:16 2021 -0700 > > sparc64: Fix opcode filtering in handling of no fault loads Colin, yes, but I believe that it was quite a different kernel bug. Besides, my current kernel test is based on git kernel 5.13.0-rc6 (released last monday), which already includes the mentioned 'opcode' fix. > > stress-ng.git$ ./stress-ng --verbose --timeout 10m --opcode -1 > > stress-ng: debug: [480950] stress-ng 0.12.10 g27f90a2276bd > > stress-ng: debug: [480950] system: Linux ttip 5.13.0-rc6 #229 SMP Tue > > Jun 15 12:30:23 MSK 2021 sparc64 > > stress-ng: debug: [480950] RAM total: 7.8G, RAM free: 7.0G, swap free: 768.7M > > stress-ng: debug: [480950] 8 processors online, 256 processors configured > > stress-ng: info: [480950] dispatching hogs: 8 opcode
