From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Sumit Gemini <sumit.gemini0@gmail.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Watchdog detected hard lockup.
Date: Wed, 24 May 2017 17:26:53 +0900 [thread overview]
Message-ID: <20170524082653.GB3311@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <CAD6qDH6r76dv6pucTpOOmq_GCi=Yt9mW1yTOHSMLitHVf3CqpQ@mail.gmail.com>
On (05/24/17 12:57), Sumit Gemini wrote:
> Hi Sergey,
>
> Can I get solution for this issue? As i tried to stop martian source
> packets but team did not agree on it. Please suggest me what can i do?
oh, um... hm. there is no quick solution I can suggest (assuming that
the lockup was actually caused by printk).
try to disable CONFIG_IP_ROUTE_VERBOSE?
-ss
next prev parent reply other threads:[~2017-05-24 8:27 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 ` Watchdog detected hard lockup Sergey Senozhatsky
[not found] ` <CAD6qDH6e7HChVg0N8myc5g82ovWAbsqXTD5+=bT6b8ADv8MVYA@mail.gmail.com>
[not found] ` <CAD6qDH6r76dv6pucTpOOmq_GCi=Yt9mW1yTOHSMLitHVf3CqpQ@mail.gmail.com>
2017-05-24 8:26 ` Sergey Senozhatsky [this message]
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
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=20170524082653.GB3311@jagdpanzerIV.localdomain \
--to=sergey.senozhatsky.work@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--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;
as well as URLs for NNTP newsgroup(s).