Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751216AbXEXQOj (ORCPT ); Thu, 24 May 2007 12:14:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750748AbXEXQOc (ORCPT ); Thu, 24 May 2007 12:14:32 -0400 Received: from mailer.gwdg.de ([134.76.10.26]:35692 "EHLO mailer.gwdg.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750738AbXEXQOb (ORCPT ); Thu, 24 May 2007 12:14:31 -0400 Date: Thu, 24 May 2007 18:13:17 +0200 (MEST) From: Jan Engelhardt To: Randy Dunlap cc: lkml , akpm Subject: Re: [PATCH] add "notime" boot option In-Reply-To: <20070522120938.db67f1e9.randy.dunlap@oracle.com> Message-ID: References: <20070522120938.db67f1e9.randy.dunlap@oracle.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Report: Content analysis: 0.0 points, 6.0 required _SUMMARY_ Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 886 Lines: 27 On May 22 2007 12:09, Randy Dunlap wrote: >From: Randy Dunlap > >Add "notime" boot option to prevent timing data from being printed on >each printk message line. > >We've seen a few cases of 'time' data locking problems (possibly >involving netconsole or net drivers). If a kernel is built with >CONFIG_PRINTK_TIME=y, it may have a boot locking hang. Booting >with "notime" may (i.e., could) prevent the lock hang and allow the >kernel to boot successfully, without requiring a kernel rebuild. Wonderful, now we have _three_ options to control time... time= printk.time= notime= Jan -- - 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/