mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: kernel test robot <yujie.liu@intel.com>
Cc: kan.liang@linux.intel.com, oe-lkp@lists.linux.dev, lkp@intel.com,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	mingo@redhat.com, eranian@google.com, ak@linux.intel.com
Subject: Re: [PATCH V4 2/2] perf/x86/intel/ds: Delay the threshold update
Date: Tue, 25 Apr 2023 13:19:55 +0200	[thread overview]
Message-ID: <20230425111955.GB1335080@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <202304251457.d108dbb3-yujie.liu@intel.com>

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?

  reply	other threads:[~2023-04-25 11:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-21 18:45 [PATCH V4 1/2] perf/x86/intel/ds: Flush the PEBS buffer in PEBS enable kan.liang
2023-04-21 18:45 ` [PATCH V4 2/2] perf/x86/intel/ds: Delay the threshold update kan.liang
2023-04-25  7:16   ` kernel test robot
2023-04-25 11:19     ` Peter Zijlstra [this message]
2023-04-27  6:26       ` Yujie Liu
2023-05-04  9:11     ` Peter Zijlstra
2023-05-04 10:16       ` Peter Zijlstra
2023-04-26 13:18 ` [PATCH V4 1/2] perf/x86/intel/ds: Flush the PEBS buffer in PEBS enable Peter Zijlstra
2023-04-26 14:23   ` Liang, Kan
2023-05-10 13:25 ` [tip: perf/urgent] perf/x86/intel/ds: Flush PEBS DS when changing PEBS_DATA_CFG tip-bot2 for Kan Liang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230425111955.GB1335080@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=ak@linux.intel.com \
    --cc=eranian@google.com \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mingo@redhat.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=yujie.liu@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®