Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753840Ab1CYOsY (ORCPT ); Fri, 25 Mar 2011 10:48:24 -0400 Received: from bombadil.infradead.org ([18.85.46.34]:54741 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753659Ab1CYOsX (ORCPT ); Fri, 25 Mar 2011 10:48:23 -0400 Subject: Re: deadlock caused by printk From: Peter Zijlstra To: Ming Lei Cc: torvalds@osdl.org, Ingo Molnar , Linux Kernel Mailing List In-Reply-To: References: <1301055698.2250.198.camel@laptop> <1301055960.2250.202.camel@laptop> Content-Type: text/plain; charset="UTF-8" Date: Fri, 25 Mar 2011 15:50:27 +0100 Message-ID: <1301064627.2250.215.camel@laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 557 Lines: 18 On Fri, 2011-03-25 at 22:30 +0800, Ming Lei wrote: > > But seems ftrace can't dump out the messages if system hangs, True. > so could > we introduce a smart and simple "printk" which can be used in any > contexts? I think you could use early_printk() for that, it doesn't bother with all the syslog muck. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/