lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <3D1B8F1F-2C41-4CCD-A5D7-41CF412F99DE@gmail.com>
Date: Sun, 25 Aug 2024 18:24:28 +0200
From: Piotr Oniszczuk <piotr.oniszczuk@...il.com>
To: Pedro Falcato <pedro.falcato@...il.com>
Cc: Nhat Pham <nphamcs@...il.com>,
 Matthew Wilcox <willy@...radead.org>,
 Linux regressions mailing list <regressions@...ts.linux.dev>,
 LKML <linux-kernel@...r.kernel.org>,
 Johannes Weiner <hannes@...xchg.org>,
 Yosry Ahmed <yosryahmed@...gle.com>,
 Linux-MM <linux-mm@...ck.org>
Subject: Re: [regression] oops on heavy compilations ("kernel BUG at
 mm/zswap.c:1005!" and "Oops: invalid opcode: 0000")



> Wiadomość napisana przez Pedro Falcato <pedro.falcato@...il.com> w dniu 25.08.2024, o godz. 17:05:
> 
> Also, could you try a memtest86 on your machine, to shake out potential hardware problems?


I found less time consuming way to trigger issue: 12c24t cross compile of llvm with „only 16G” of ram - as this triggers many heavy swappings (top swap usage gets 8-9G out of 16G swap part)

With such setup - on 6.9.12 - i’m getting not available system (due cpu soft lockup) just in 1..3h
(usually first or second compile iteration; i wrote simple scrip compiling in loop + counting interations)

Then i switched back to 6.8.2 and…. decided interrupt successful test after 14 iterations (it was 19h of non-stop compiling with heavy swapping)
(sure - i can still keep test going - but builder is also needed for my normal development)

So summarising:
-on 6.9+ just 1..3h seems enough to provoke issue
-on 6.8.2 so far never in past + currently can’t provoke issue (last day in 19h test window nor 5 full distro builds nor last 2 weeks of development)

By above i personally don’t believe issue is in hw (ram)


   

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ