From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sergey Senozhatsky Subject: Re: Serial console is causing system lock-up Date: Fri, 8 Mar 2019 10:39:52 +0900 Message-ID: <20190308013952.GA9085@jagdpanzerIV> References: <20190306152218.eocv4zulf7tv2mkc@pathway.suse.cz> <20190306163003.GA31858@mit.edu> <20190306171943.12345598@oasis.local.home> <87ftrzbp3y.fsf@linutronix.de> <23681.9703.524330.948156@quad.stoffel.home> <20190308012242.GA4063@jagdpanzerIV> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20190308012242.GA4063@jagdpanzerIV> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Mikulas Patocka Cc: Petr Mladek , Nigel Croxon , "Theodore Y. Ts'o" , Sergey Senozhatsky , John Ogness , Greg Kroah-Hartman , John Stoffel , Steven Rostedt , Sergey Senozhatsky , dm-devel@redhat.com, linux-serial@vger.kernel.org List-Id: linux-serial@vger.kernel.org On (03/08/19 10:22), Sergey Senozhatsky wrote: > > Perhaps a proper solution would be to drop excessive messages to serial > > console unless Oops or BUG has happened? > > Technically, we can have a per-console loglevel configuration. We have > several use cases for this already. JFI, lore.kernel.org/r/cover.1551486732.git.calvinowens@fb.com -ss