linux-kernel - Re: [PATCH V4 2/2] perf/x86/intel/ds: Delay the threshold update

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]

Date:   Tue, 25 Apr 2023 13:19:55 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     kernel test robot <yujie.liu@...el.com>
Cc:     kan.liang@...ux.intel.com, oe-lkp@...ts.linux.dev, lkp@...el.com,
        linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org,
        mingo@...hat.com, eranian@...gle.com, ak@...ux.intel.com
Subject: Re: [PATCH V4 2/2] perf/x86/intel/ds: Delay the threshold update

On Tue, Apr 25, 2023 at 03:16:29PM +0800, kernel test robot wrote:
> Hello,
> 
> kernel test robot noticed "Kernel_panic-not_syncing:Timeout:Not_all_CPUs_entered_broadcast_exception_handler" on:
> 
> commit: a17c97370d1fb9b2eac75c85136a1f70ec44eded ("[PATCH V4 2/2] perf/x86/intel/ds: Delay the threshold update")
> url: https://github.com/intel-lab-lkp/linux/commits/kan-liang-linux-intel-com/perf-x86-intel-ds-Delay-the-threshold-update/20230422-024743
> base: https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git 15def34e2635ab7e0e96f1bc32e1b69609f14942
> patch link: https://lore.kernel.org/all/20230421184529.3320912-2-kan.liang@linux.intel.com/
> patch subject: [PATCH V4 2/2] perf/x86/intel/ds: Delay the threshold update
> 

> [  224.064675][   C84] mce: CPUs not responding to MCE broadcast (may include false positives): 0-83,85-223
> [  224.064681][   C84] Kernel panic - not syncing: Timeout: Not all CPUs entered broadcast exception handler
> [  225.089881][   C84] Shutting down cpus with NMI
> [  225.129381][   C84] Kernel Offset: disabled

That seems very unrelated to the patch at hand; was this bisect double
checked?