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]
Message-ID: <202304251457.d108dbb3-yujie.liu@intel.com>
Date:   Tue, 25 Apr 2023 15:16:29 +0800
From:   kernel test robot <yujie.liu@...el.com>
To:     <kan.liang@...ux.intel.com>
CC:     <oe-lkp@...ts.linux.dev>, <lkp@...el.com>,
        <linux-perf-users@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <peterz@...radead.org>, <mingo@...hat.com>, <eranian@...gle.com>,
        <ak@...ux.intel.com>, Kan Liang <kan.liang@...ux.intel.com>
Subject: Re: [PATCH V4 2/2] perf/x86/intel/ds: Delay the threshold update

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

in testcase: kvm-unit-tests-qemu

compiler: gcc-11
test machine: 224 threads 2 sockets Intel(R) Xeon(R) Platinum 8480+ (Sapphire Rapids) with 256G memory

(please refer to attached dmesg/kmsg for entire log/backtrace)


If you fix the issue, kindly add following tag
| Reported-by: kernel test robot <yujie.liu@...el.com>
| Link: https://lore.kernel.org/oe-lkp/202304251457.d108dbb3-yujie.liu@intel.com


[  179.997768][ T2324] 2023-04-23 15:30:10 ./run_tests.sh
...
[  180.442663][T20263] x86/split lock detection: #AC: qemu-system-x86/20263 took a split_lock trap at address: 0x1e3
[  182.372875][ T2324] 
[  182.845057][T20473] x86/split lock detection: #AC: qemu-system-x86/20473 took a split_lock trap at address: 0x1e3
[  184.109963][ T2324] 
[  184.594015][T20686] x86/split lock detection: #AC: qemu-system-x86/20686 took a split_lock trap at address: 0x1e3
[  186.113512][ T2324] 
[  186.595753][T20897] x86/split lock detection: #AC: qemu-system-x86/20897 took a split_lock trap at address: 0x1e3
[  188.771195][ T2324] 
[  189.257277][T21112] x86/split lock detection: #AC: qemu-system-x86/21112 took a split_lock trap at address: 0x1e3
[  190.649532][ T2324] 
[  191.142833][T21320] x86/split lock detection: #AC: qemu-system-x86/21320 took a split_lock trap at address: 0x1e3
[  204.181302][ T2324] 
[  204.192731][ T2324] 
[  204.677795][T21577] x86/split lock detection: #AC: qemu-system-x86/21577 took a split_lock trap at address: 0x1e3
[  208.521357][ T2324] 
[  209.002903][T21799] x86/split lock detection: #AC: qemu-system-x86/21799 took a split_lock trap at address: 0x1e3
[  209.092837][ T2324] 
[  209.565251][T22006] x86/split lock detection: #AC: qemu-system-x86/22006 took a split_lock trap at address: 0x1e3
[  209.654034][ T2324] 
[  210.133408][T22210] x86/split lock detection: #AC: qemu-system-x86/22210 took a split_lock trap at address: 0x1e3
[  210.200824][ T2324] 
[  210.668239][T22414] x86/split lock detection: #AC: qemu-system-x86/22414 took a split_lock trap at address: 0x1e3
[  211.617069][ T2324] 
[  212.098716][T22618] x86/split lock detection: #AC: qemu-system-x86/22618 took a split_lock trap at address: 0x1e3
[  212.139734][T22618] kvm: emulating exchange as write
[  212.236036][ T2324] 
[  212.721375][T22825] x86/split lock detection: #AC: qemu-system-x86/22825 took a split_lock trap at address: 0x1e3
[  212.815919][ T2324] 
[  213.308442][T23032] x86/split lock detection: #AC: qemu-system-x86/23032 took a split_lock trap at address: 0x1e3
[  213.390697][ T2324] 
[  213.864128][T23236] x86/split lock detection: #AC: qemu-system-x86/23236 took a split_lock trap at address: 0x1e3
[  213.937439][ T2324] 
[  214.410905][T23443] x86/split lock detection: #AC: qemu-system-x86/23443 took a split_lock trap at address: 0x1e3
[  214.491760][ T2324] 
[  214.958649][T23647] x86/split lock detection: #AC: qemu-system-x86/23647 took a split_lock trap at address: 0x1e3
[  216.032131][ T2324] 
[  216.520146][T23858] x86/split lock detection: #AC: qemu-system-x86/23858 took a split_lock trap at address: 0x1e3
[  218.172563][ T2324] 
[  218.664754][T24072] x86/split lock detection: #AC: qemu-system-x86/24072 took a split_lock trap at address: 0x1e3
[  218.739564][ T2324] 
[  219.241807][T24274] x86/split lock detection: #AC: qemu-system-x86/24274 took a split_lock trap at address: 0x1e3
[  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
[  234.178388][   C84] pstore: backend (erst) writing error (-28)
input_data: 0x000000407e8bd3a8
input_len: 0x0000000001535d82
output: 0x000000407ac00000
output_len: 0x00000000050619f8
kernel_total_size: 0x0000000005228000
needed_size: 0x0000000005400000
trampoline_32bit: 0x000000000009d000


-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests

View attachment "config-6.3.0-rc3-00006-ga17c97370d1f" of type "text/plain" (156853 bytes)

View attachment "job-script" of type "text/plain" (5737 bytes)

Download attachment "dmesg.xz" of type "application/x-xz" (91640 bytes)

View attachment "kvm-unit-tests-qemu" of type "text/plain" (511770 bytes)

View attachment "job.yaml" of type "text/plain" (4889 bytes)