* perf samples too long without perf running (?!?)
@ 2014-03-08 1:57 Andy Lutomirski
2014-03-08 7:51 ` Mike Galbraith
0 siblings, 1 reply; 5+ messages in thread
From: Andy Lutomirski @ 2014-03-08 1:57 UTC (permalink / raw)
To: linux-kernel@vger.kernel.org
On recent (3.13) kernels, I'm frequently getting messages like:
perf samples too long (2503 > 2500), lowering
kernel.perf_event_max_sample_rate to 50000
a few seconds to minutes after bootup. As far as I know, I'm not
using perf. What's going on here?
--Andy
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: perf samples too long without perf running (?!?)
2014-03-08 1:57 perf samples too long without perf running (?!?) Andy Lutomirski
@ 2014-03-08 7:51 ` Mike Galbraith
2014-03-08 9:13 ` Markus Trippelsdorf
0 siblings, 1 reply; 5+ messages in thread
From: Mike Galbraith @ 2014-03-08 7:51 UTC (permalink / raw)
To: Andy Lutomirski; +Cc: linux-kernel@vger.kernel.org
On Fri, 2014-03-07 at 17:57 -0800, Andy Lutomirski wrote:
> On recent (3.13) kernels, I'm frequently getting messages like:
>
> perf samples too long (2503 > 2500), lowering
> kernel.perf_event_max_sample_rate to 50000
>
> a few seconds to minutes after bootup. As far as I know, I'm not
> using perf. What's going on here?
14c63f17b1
I get those all the time too, just building kernels.
[ 598.583918] perf samples too long (2539 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
Darn nmi_watchdog is an expensive employee. Scarier are the ones from
2ab00456ea when using perf. Firing the dog makes it all batter.
-Mike
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: perf samples too long without perf running (?!?)
2014-03-08 7:51 ` Mike Galbraith
@ 2014-03-08 9:13 ` Markus Trippelsdorf
2014-03-08 16:22 ` Andy Lutomirski
0 siblings, 1 reply; 5+ messages in thread
From: Markus Trippelsdorf @ 2014-03-08 9:13 UTC (permalink / raw)
To: Mike Galbraith; +Cc: Andy Lutomirski, linux-kernel@vger.kernel.org
On 2014.03.08 at 08:51 +0100, Mike Galbraith wrote:
> On Fri, 2014-03-07 at 17:57 -0800, Andy Lutomirski wrote:
> > On recent (3.13) kernels, I'm frequently getting messages like:
> >
> > perf samples too long (2503 > 2500), lowering
> > kernel.perf_event_max_sample_rate to 50000
> >
> > a few seconds to minutes after bootup. As far as I know, I'm not
> > using perf. What's going on here?
>
> 14c63f17b1
>
> I get those all the time too, just building kernels.
I have:
echo 0 > /proc/sys/kernel/perf_cpu_time_max_percent
in my local startup script since that commit.
--
Markus
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: perf samples too long without perf running (?!?)
2014-03-08 9:13 ` Markus Trippelsdorf
@ 2014-03-08 16:22 ` Andy Lutomirski
2014-03-08 17:12 ` Paul Bolle
0 siblings, 1 reply; 5+ messages in thread
From: Andy Lutomirski @ 2014-03-08 16:22 UTC (permalink / raw)
To: Markus Trippelsdorf; +Cc: Mike Galbraith, linux-kernel@vger.kernel.org
On Sat, Mar 8, 2014 at 1:13 AM, Markus Trippelsdorf
<markus@trippelsdorf.de> wrote:
> On 2014.03.08 at 08:51 +0100, Mike Galbraith wrote:
>> On Fri, 2014-03-07 at 17:57 -0800, Andy Lutomirski wrote:
>> > On recent (3.13) kernels, I'm frequently getting messages like:
>> >
>> > perf samples too long (2503 > 2500), lowering
>> > kernel.perf_event_max_sample_rate to 50000
>> >
>> > a few seconds to minutes after bootup. As far as I know, I'm not
>> > using perf. What's going on here?
>>
>> 14c63f17b1
>>
>> I get those all the time too, just building kernels.
>
> I have:
> echo 0 > /proc/sys/kernel/perf_cpu_time_max_percent
> in my local startup script since that commit.
...so the NMI watchdog (which happens IIRC once every two minutes)
takes more than 0.4ms or so, so perf flips out, changes its parameters,
and writes a log message.
Is it just me or is this whole situation screwed up for multiple reasons?
--Andy
>
> --
> Markus
--
Andy Lutomirski
AMA Capital Management, LLC
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: perf samples too long without perf running (?!?)
2014-03-08 16:22 ` Andy Lutomirski
@ 2014-03-08 17:12 ` Paul Bolle
0 siblings, 0 replies; 5+ messages in thread
From: Paul Bolle @ 2014-03-08 17:12 UTC (permalink / raw)
To: Andy Lutomirski
Cc: Markus Trippelsdorf, Mike Galbraith, linux-kernel@vger.kernel.org
On Sat, 2014-03-08 at 08:22 -0800, Andy Lutomirski wrote:
> Is it just me or is this whole situation screwed up for multiple reasons?
One minor reason would be that this message should read (say)
perf samples taking too long (2503 ns > 2500 ns), [...]
At least, that's what I thought after diving into the code to see what
was causing warnings like these.
And, since apparently things are just fine without administrator
intervention, I'd say another minor reason is that printing this at
KERN_INFO or KERN_NOTICE level should be enough here.
Paul Bolle
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-03-08 17:12 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-03-08 1:57 perf samples too long without perf running (?!?) Andy Lutomirski
2014-03-08 7:51 ` Mike Galbraith
2014-03-08 9:13 ` Markus Trippelsdorf
2014-03-08 16:22 ` Andy Lutomirski
2014-03-08 17:12 ` Paul Bolle
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox