> Can you use 'git bisect' to track down the kernel commit that caused > this problem? Yes, I will try that and report the back the findings. On Tue, Mar 22, 2022 at 8:15 AM Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > On Tue, Mar 22, 2022 at 12:37:37AM +0100, Jirka Hladky wrote: > > Cc: regressions@xxxxxxxxxxxxxxx stable@xxxxxxxxxxxxxxx > > > > On Tue, Mar 22, 2022 at 12:29 AM Jirka Hladky <jhladky@xxxxxxxxxx> wrote: > > > > > > Starting from kernel 5.17 (tested with rc2, rc4, rc7, rc8) we > > > experience kernel oops on Intel Xeon Gold dual-socket servers (2x Xeon > > > Gold 6126 CPU) > > > > > > Bellow is a backtrace and the dmesg log. > > > > > > I have trouble creating a simple reproducer - it happens at random > > > places when preparing the NAS benchmark to be run. The script creates > > > a bunch of directories, compiles the benchmark a start trial runs. > > > > > > Could you please help to narrow down the problem? > > Can you use 'git bisect' to track down the kernel commit that caused > this problem? > > thanks, > > greg k-h > -- -Jirka
