From: Petr Mladek <pmladek@suse.com>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Sumit Gemini <sumit.gemini0@gmail.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org
Subject: Re: Fwd: Watchdog detected hard lockup.
Date: Thu, 25 May 2017 11:56:45 +0200 [thread overview]
Message-ID: <20170525095645.GE26699@pathway.suse.cz> (raw)
In-Reply-To: <20170525055014.GB386@jagdpanzerIV.localdomain>
On Thu 2017-05-25 14:50:14, Sergey Senozhatsky wrote:
> On (05/25/17 11:14), Sumit Gemini wrote:
> > Thanks Sergey and i forgot to add other guys in discussion.
> >
> >
> > [1]lkml.kernel.org/r/20170509082859.854-1-sergey.senozhatsky@gmail.com
> >
> > Now I'm going for backporting the kernel with RFC, as you suggested me
> > yesterday.
>
> or you can try to reduce the amount of data you printk from IRQ.
In fact, you should reduce the amount of data you printk from all
contexts. There might be more sources that produce too many messages.
The system evidently has troubles to keep the speed and get them
on the console.
You might also try to reduce the console_level and show only the more
important messages on the console.
> need to hex dump sbks all the time?
I wanted to suggest using ratelimit but it seems that the hex dump
is already ratelimited, see net_ratelimit() in
ip_handle_martian_source().
This might suggest that are more sources of printk messages on the
system. Or that you modified the ratelimit setting to print too many
messages.
> switching to a deferred printk won't
> do the trick, probably, because you gonna console_unlock() from IRQ in
> the worst case anyway.
Yup.
Best Regards,
Petr
prev parent reply other threads:[~2017-05-25 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAD6qDH4cw1BSHpHoqzFGYkcxBJcFy=AjjoYuY1-a+HAwgDDY1g@mail.gmail.com>
2017-05-18 7:31 ` Sergey Senozhatsky
[not found] ` <CAD6qDH6e7HChVg0N8myc5g82ovWAbsqXTD5+=bT6b8ADv8MVYA@mail.gmail.com>
[not found] ` <CAD6qDH6r76dv6pucTpOOmq_GCi=Yt9mW1yTOHSMLitHVf3CqpQ@mail.gmail.com>
2017-05-24 8:26 ` Sergey Senozhatsky
2017-05-24 8:39 ` Sergey Senozhatsky
[not found] ` <CAD6qDH6zyP535vm4VQ+R0JFRXupvXsxj2xUmDKcd3=iJAfY1Dg@mail.gmail.com>
[not found] ` <20170524125907.GA463@jagdpanzerIV.localdomain>
[not found] ` <CAD6qDH6+G6WYdP8-aOhLk0VJV1QX1yXLD-dwxLk=o3ZLmG_-JQ@mail.gmail.com>
[not found] ` <20170525052952.GA386@jagdpanzerIV.localdomain>
[not found] ` <CAD6qDH6C2umiP-UOB2nkwawQO+1JBw8Xc+a0NFRCOZHTjnqmtQ@mail.gmail.com>
2017-05-25 5:50 ` Fwd: " Sergey Senozhatsky
2017-05-25 9:56 ` Petr Mladek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170525095645.GE26699@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=sumit.gemini0@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®