From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Theodore Y. Ts'o" Subject: Re: Serial console is causing system lock-up Date: Wed, 6 Mar 2019 11:30:04 -0500 Message-ID: <20190306163003.GA31858@mit.edu> References: <20190306152218.eocv4zulf7tv2mkc@pathway.suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: 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 , Greg Kroah-Hartman , Steven Rostedt , Sergey Senozhatsky , dm-devel@redhat.com, linux-serial@vger.kernel.org List-Id: linux-serial@vger.kernel.org On Wed, Mar 06, 2019 at 11:07:55AM -0500, Mikulas Patocka wrote: > This bug only happens if we select large logbuffer (millions of > characters). With smaller log buffer, there are messages "** X printk > messages dropped", but there's no lockup. > > The kernel apparently puts 2 million characters into a console log buffer, > then takes some lock and than tries to write all of them to a slow serial > line. What are the messages; from what kernel subsystem? Why are you seeing so many log messages? - Ted