From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S939078AbdEXIoc (ORCPT <rfc822;w@1wt.eu>);
        Wed, 24 May 2017 04:44:32 -0400
Received: from mail-pg0-f66.google.com ([74.125.83.66]:33753 "EHLO
        mail-pg0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1764677AbdEXIjR (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 24 May 2017 04:39:17 -0400
Date: Wed, 24 May 2017 17:39:14 +0900
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Sumit Gemini <sumit.gemini0@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.
Message-ID: <20170524083914.GC3311@jagdpanzerIV.localdomain>
References: <CAD6qDH4cw1BSHpHoqzFGYkcxBJcFy=AjjoYuY1-a+HAwgDDY1g@mail.gmail.com>
 <20170518073125.GA458@jagdpanzerIV.localdomain>
 <CAD6qDH6e7HChVg0N8myc5g82ovWAbsqXTD5+=bT6b8ADv8MVYA@mail.gmail.com>
 <CAD6qDH6r76dv6pucTpOOmq_GCi=Yt9mW1yTOHSMLitHVf3CqpQ@mail.gmail.com>
 <20170524082653.GB3311@jagdpanzerIV.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170524082653.GB3311@jagdpanzerIV.localdomain>
User-Agent: Mutt/1.8.2 (2017-04-18)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On (05/24/17 17:26), Sergey Senozhatsky wrote:
> 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?

unless you want to play with RFC/untested patchset:

lkml.kernel.org/r/20170509082859.854-1-sergey.senozhatsky@gmail.com

which you'll have to backport to your kernel.

	-ss