Messages in this thread | | | Date | Thu, 7 Mar 2019 00:09:53 +0100 | From | Pavel Machek <> | Subject | Re: System crash with perf_fuzzer (kernel: 5.0.0-rc3) |
| |
On Fri 2019-01-25 08:00:56, Andi Kleen wrote: > > [Fri Jan 25 10:28:53 2019] perf: interrupt took too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 79750 > > [Fri Jan 25 10:29:08 2019] perf: interrupt took too long (3136 > 3126), lowering kernel.perf_event_max_sample_rate to 63750 > > [Fri Jan 25 10:29:11 2019] perf: interrupt took too long (4140 > 3920), lowering kernel.perf_event_max_sample_rate to 48250 > > [Fri Jan 25 10:29:11 2019] perf: interrupt took too long (5231 > 5175), lowering kernel.perf_event_max_sample_rate to 38000 > > [Fri Jan 25 10:29:11 2019] perf: interrupt took too long (6736 > 6538), lowering kernel.perf_event_max_sample_rate to 29500 > > These are fairly normal.
Unfortunately, they are. Could we set up our defaults so that they don't normally happen?
pavel@amd:~/g/unicsy_demo$ dmesg | grep "took too" [ 761.507893] perf: interrupt took too long (2516 > 2500), lowering kernel.perf_event_max_sample_rate to 79250 [ 4736.674595] perf: interrupt took too long (3209 > 3145), lowering kernel.perf_event_max_sample_rate to 62250 pavel@amd:~/g/unicsy_demo$
-- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html [unhandled content-type:application/pgp-signature] | |