[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100825111944.GA21682@elte.hu>
Date: Wed, 25 Aug 2010 13:19:44 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Robert Richter <robert.richter@....com>
Cc: Don Zickus <dzickus@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Cyrill Gorcunov <gorcunov@...il.com>,
Lin Ming <ming.m.lin@...el.com>,
"fweisbec@...il.com" <fweisbec@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Huang, Ying" <ying.huang@...el.com>,
Yinghai Lu <yinghai@...nel.org>,
Andi Kleen <andi@...stfloor.org>
Subject: Re: [PATCH -v3] perf, x86: try to handle unknown nmis with running
perfctrs
* Robert Richter <robert.richter@....com> wrote:
> On 25.08.10 06:41:30, Ingo Molnar wrote:
>
> > > > > > Uhhuh. NMI received for unknown reason 00 on CPU 9.
> > > > > > Do you have a strange power saving mode enabled?
> > > > > > Dazed and confused, but trying to continue
> >
> > Before the two patches i did not get these messages at all, on any
> > of the systems.
>
> Yes, because all were eaten by NOTIFY_STOP, and that's why we also
> lose NMIs from other sources, like the nmi button. The patches try to
> fix this.
I understand that, but obviously the patches need to fix the lack of
messages without introducing new regressions: such as messages not seen
before and CPUs with stuck NMIs.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists