[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250402124114.GW5880@noisy.programming.kicks-ass.net>
Date: Wed, 2 Apr 2025 14:41:14 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: kernel test robot <oliver.sang@...el.com>
Cc: oe-lkp@...ts.linux.dev, lkp@...el.com, linux-kernel@...r.kernel.org
Subject: Re: [peterz-queue:sched/hrtick] [entry,hrtimer,x86] c07c4e0c01:
BUG:soft_lockup-CPU##stuck_for#s![schbench:#]
On Fri, Mar 28, 2025 at 09:24:05AM +0800, kernel test robot wrote:
>
>
> Hello,
>
> kernel test robot noticed "BUG:soft_lockup-CPU##stuck_for#s![schbench:#]" on:
>
> commit: c07c4e0c013dc11dd466fa63a4af12ef8282b27b ("entry,hrtimer,x86: Push reprogramming timers into the interrupt return path")
> https://git.kernel.org/cgit/linux/kernel/git/peterz/queue.git sched/hrtick
>
> in testcase: schbench
> version: schbench-x86_64-48aed1d-1_20241103
> with following parameters:
>
> iterations: 3x
> message_threads: 10%
> worker_threads: 128
> runtime: 300s
> cpufreq_governor: performance
>
>
>
> config: x86_64-rhel-9.4
> compiler: gcc-12
> test machine: 128 threads 2 sockets Intel(R) Xeon(R) Platinum 8358 CPU @ 2.60GHz (Ice Lake) with 128G memory
>
Thanks, I can reproduce. I'll poke at it some.
Powered by blists - more mailing lists