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 S1032114AbdEYJ4u (ORCPT <rfc822;w@1wt.eu>);
        Thu, 25 May 2017 05:56:50 -0400
Received: from mx2.suse.de ([195.135.220.15]:39685 "EHLO mx1.suse.de"
        rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP
        id S933324AbdEYJ4r (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 25 May 2017 05:56:47 -0400
Date: Thu, 25 May 2017 11:56:45 +0200
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.
Message-ID: <20170525095645.GE26699@pathway.suse.cz>
References: <CAD6qDH6e7HChVg0N8myc5g82ovWAbsqXTD5+=bT6b8ADv8MVYA@mail.gmail.com>
 <CAD6qDH6r76dv6pucTpOOmq_GCi=Yt9mW1yTOHSMLitHVf3CqpQ@mail.gmail.com>
 <20170524082653.GB3311@jagdpanzerIV.localdomain>
 <20170524083914.GC3311@jagdpanzerIV.localdomain>
 <CAD6qDH6zyP535vm4VQ+R0JFRXupvXsxj2xUmDKcd3=iJAfY1Dg@mail.gmail.com>
 <20170524125907.GA463@jagdpanzerIV.localdomain>
 <CAD6qDH6+G6WYdP8-aOhLk0VJV1QX1yXLD-dwxLk=o3ZLmG_-JQ@mail.gmail.com>
 <20170525052952.GA386@jagdpanzerIV.localdomain>
 <CAD6qDH6C2umiP-UOB2nkwawQO+1JBw8Xc+a0NFRCOZHTjnqmtQ@mail.gmail.com>
 <20170525055014.GB386@jagdpanzerIV.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20170525055014.GB386@jagdpanzerIV.localdomain>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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