On Mon, Oct 26, 2015 at 04:57:08PM +0600, Andrey Kitsul wrote:
Hello,
I see in the logs:
2015-10-26 16:52:11 <WARN> Event 0x0000000000442440 0x0000000000000000 took 1418 ms 2015-10-26 16:52:26 <WARN> Event 0x0000000000442440 0x0000000000000000 took 1523 ms 2015-10-26 16:52:41 <WARN> Event 0x0000000000442440 0x0000000000000000 took 1452 ms 2015-10-26 16:52:56 <WARN> Event 0x0000000000442440 0x0000000000000000 took 1429 ms 2015-10-26 16:53:11 <WARN> Event 0x0000000000442440 0x0000000000000000 took 1405 ms 2015-10-26 16:53:26 <WARN> Event 0x0000000000442440 0x0000000000000000 took 1428 ms 2015-10-26 16:53:41 <WARN> Event 0x0000000000442440 0x0000000000000000 took 1493 ms 2015-10-26 16:53:56 <WARN> Event 0x0000000000442440 0x0000000000000000 took 1455 ms How to interpret?
You would have to use gdb or perhpaps addr2line to translate addresses to event function names but with 15 s period it is pretty obvious that it is kernel periodic scan. You can confirm that by enabling debug { events } in the kernel proto and see kernel periodic events. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."