[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKA=qzY=F-wj8YXhb-B7RahNceeab0rSA=06qBc8+7V-SyY-+Q@mail.gmail.com>
Date: Mon, 12 Aug 2019 11:57:46 -0700
From: Josh Hunt <joshhunt00@...il.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Andi Kleen <ak@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>,
Cong Wang <xiyou.wangcong@...il.com>,
"Liang, Kan" <kan.liang@...el.com>, jolsa@...hat.com,
bigeasy@...utronix.de, "H. Peter Anvin" <hpa@...or.com>,
Ingo Molnar <mingo@...hat.com>, x86 <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: Long standing kernel warning: perfevents: irq loop stuck!
On Mon, Aug 12, 2019 at 10:55 AM Thomas Gleixner <tglx@...utronix.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
Powered by blists - more mailing lists