From: Peter Zijlstra <peterz@infradead.org>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Andi Kleen <ak@linux.intel.com>,
"Liang, Kan" <kan.liang@intel.com>,
jolsa@redhat.com, bigeasy@linutronix.de,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>, x86 <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Long standing kernel warning: perfevents: irq loop stuck!
Date: Fri, 23 Feb 2018 13:14:56 +0100 [thread overview]
Message-ID: <20180223121456.GZ25201@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAM_iQpXvuYKn94WjJ9nSjzhk8DzYAvDmdgxsi6cc9CdBfkdTnw@mail.gmail.com>
On Thu, Feb 22, 2018 at 08:59:47PM -0800, Cong Wang wrote:
> Hello,
>
> We keep seeing the following kernel warning from 3.10 kernel to 4.9
> kernel, it exists for a rather long time.
>
> Google search shows there was a patch from Ingo:
> https://patchwork.kernel.org/patch/6308681/
>
> but it doesn't look like ever merged into mainline...
>
> I don't know how it is triggered. Please let me know if any other
> information I can provide.
What exact workload are you using to reproduce?
And I'm taking that the patch 'works' for you?
Given the HSD143 errata and its possible relevance, have you tried
changing the magic number to 32, does it then still fix things?
No real objection to the patch as such, it just needs a coherent comment
and a tested-by tag I think.
next prev parent reply other threads:[~2018-02-23 12:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 4:59 Cong Wang
2018-02-23 12:14 ` Peter Zijlstra [this message]
2018-02-26 20:32 ` Cong Wang
2018-02-26 20:39 ` Andi Kleen
2019-08-12 17:24 ` Josh Hunt
2019-08-12 17:54 ` Thomas Gleixner
2019-08-12 18:57 ` Josh Hunt
2019-08-12 19:34 ` Thomas Gleixner
2019-08-12 19:42 ` Josh Hunt
2019-08-19 21:17 ` Josh Hunt
2019-08-19 23:16 ` Josh Hunt
2019-08-22 14:31 ` Josh Hunt
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=20180223121456.GZ25201@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ak@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xiyou.wangcong@gmail.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
Powered by JetHome