From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753927AbcGLMwt (ORCPT ); Tue, 12 Jul 2016 08:52:49 -0400 Received: from mx2.suse.de ([195.135.220.15]:41067 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753524AbcGLMws (ORCPT ); Tue, 12 Jul 2016 08:52:48 -0400 Date: Tue, 12 Jul 2016 14:52:43 +0200 From: Petr Mladek To: Sergey Senozhatsky Cc: Viresh Kumar , Jan Kara , Sergey Senozhatsky , Tejun Heo , Greg Kroah-Hartman , Linux Kernel Mailing List , vlevenetz@mm-sol.com, vaibhav.hiremath@linaro.org, alex.elder@linaro.org, johan@kernel.org, akpm@linux-foundation.org, rostedt@goodmis.org Subject: Re: [Query] Preemption (hogging) of the work handler Message-ID: <20160712125243.GA8597@pathway.suse.cz> References: <20160701165959.GR12473@ubuntu> <20160701172232.GD28719@htj.duckdns.org> <20160706182842.GS2671@ubuntu> <20160711102603.GI12410@quack2.suse.cz> <20160711154438.GA528@swordfish> <20160711223501.GI4695@ubuntu> <20160712093805.GA498@swordfish> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160712093805.GA498@swordfish> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 2016-07-12 18:38:05, Sergey Senozhatsky wrote: > Hello, > > On (07/11/16 15:35), Viresh Kumar wrote: > [..] > > Sometimes, the platform doesn't come back after suspend. I have tried > > enabling no-console-suspend and the last line it prints is: > > > > Disabling non-boot CPUs I guess that the printk() kthread is not longer scheduled when there is only one CPU left. > > And nothing after that at all. We have to forcefully reboot the phone > > after that. Moving the prints to they synchronous way (using > > echo 1 > /sys/module/printk/parameters/synchronous), fixes that issue. > > hm... I'll take a look. We might try to explicitly flush the consoles in suspend_console(). But I am not sure if we always want to do so because it might take a while. Also it need not help if someone already owns the console_sem. Note the console_unlock() calls the cond_resched() when in safe context. Well, we might do the best effort when no_console_suspend is enabled. Best Regards, Petr