Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161234AbWAHXIl (ORCPT ); Sun, 8 Jan 2006 18:08:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161236AbWAHXIk (ORCPT ); Sun, 8 Jan 2006 18:08:40 -0500 Received: from gprs189-60.eurotel.cz ([160.218.189.60]:51351 "EHLO amd.ucw.cz") by vger.kernel.org with ESMTP id S1161234AbWAHXIk (ORCPT ); Sun, 8 Jan 2006 18:08:40 -0500 Date: Mon, 9 Jan 2006 00:08:27 +0100 From: Pavel Machek To: Josef Sipek Cc: Dave Jones , David Lang , Jan Engelhardt , Bernd Eckenfels , linux-kernel@vger.kernel.org Subject: Re: oops pauser. / boot_delayer Message-ID: <20060108230827.GB1686@elf.ucw.cz> References: <20060106053609.GB32105@redhat.com> <20060108132132.GA1952@elf.ucw.cz> <20060108193000.GB10232@filer.fsl.cs.sunysb.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20060108193000.GB10232@filer.fsl.cs.sunysb.edu> X-Warning: Reading this can be dangerous to your mental health. User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2005 Lines: 41 On Ne 08-01-06 14:30:00, Josef Sipek wrote: > On Sun, Jan 08, 2006 at 02:21:32PM +0100, Pavel Machek wrote: > > On P? 06-01-06 00:36:09, Dave Jones wrote: > > > On Thu, Jan 05, 2006 at 05:28:59PM -0800, David Lang wrote: > > > > On Thu, 5 Jan 2006, Jan Engelhardt wrote: > > > > > > > > >Also note that the kernel generates a lot of noise^W text - if now the > > > > >start scripts from $YOUR_FAVORITE_DISTRO also fill up, I can barely reach > > > > >the top of the kernel when it says > > > > > Linux version 2.6.15 (jengelh@gwdg-wb04.gwdg.de) (gcc version 4.0.2 > > > > > 20050901 (prerelease) (SUSE Linux)) #1 Tue Jan 3 09:21:27 CET 2006 > > > > > > > > enable a few different types of encryption and you have to enlarge the > > > > buffer (by quite a bit). the fact that all the encryption tests print > > > > several lines each out and can't be turned off (short of a quiet boot > > > > where you loose everything) is one of the more annoying things to me right > > > > now. > > > > > > > > this large boot message issue also slows your boot significantly if you > > > > have a fast box that has a serial console, it takes a long time to dump > > > > all that info out the serial port. > > > > > > So disable CONFIG_CRYPTO_TEST. There's no reason to test this stuff every boot. > > > > Maybe even with CRYPTO_TEST enabled we could only report _failures_? > > Why? As far as I know, it is intended for developers as a regression test. I say > if you don't like the output, make the thing a module or don't compile it at all. I don't like the output, but if it only reported failures, I could leave it running and potentially catch some strange failures. Is reporting successes actually useful? Pavel -- Thanks, Sharp! - 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/