All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Hunt <joshhunt00@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andi Kleen <ak@linux.intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Cong Wang <xiyou.wangcong@gmail.com>,
	"Liang, Kan" <kan.liang@intel.com>,
	jolsa@redhat.com, bigeasy@linutronix.de,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
	x86 <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Long standing kernel warning: perfevents: irq loop stuck!
Date: Mon, 12 Aug 2019 11:57:46 -0700	[thread overview]
Message-ID: <CAKA=qzY=F-wj8YXhb-B7RahNceeab0rSA=06qBc8+7V-SyY-+Q@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1908121933310.7324@nanos.tec.linutronix.de>

On Mon, Aug 12, 2019 at 10:55 AM Thomas Gleixner <tglx@linutronix.de> wrote:
>
> On Mon, 12 Aug 2019, Josh Hunt wrote:
> > Was there any progress made on debugging this issue? We are still
> > seeing it on 4.19.44:
>
> I haven't seen anyone looking at this.
>
> Can you please try the patch Ingo posted:
>
>   https://lore.kernel.org/lkml/20150501070226.GB18957@gmail.com/
>
> and if it fixes the issue decrease the value from 128 to the point where it
> comes back, i.e. 128 -> 64 -> 32 ...
>
> Thanks,
>
>         tglx

I just checked the machines where this problem occurs and they're both
Nehalem boxes. I think Ingo's patch would only help Haswell machines.
Please let me know if I misread the patch or if what I'm seeing is a
different issue than the one Cong originally reported.

Thanks
-- 
Josh

  reply	other threads:[~2019-08-12 18:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-23  4:59 Long standing kernel warning: perfevents: irq loop stuck! Cong Wang
2018-02-23 12:14 ` Peter Zijlstra
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 [this message]
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='CAKA=qzY=F-wj8YXhb-B7RahNceeab0rSA=06qBc8+7V-SyY-+Q@mail.gmail.com' \
    --to=joshhunt00@gmail.com \
    --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=peterz@infradead.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.