From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264432AbTLCAKQ (ORCPT ); Tue, 2 Dec 2003 19:10:16 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264437AbTLCAKQ (ORCPT ); Tue, 2 Dec 2003 19:10:16 -0500 Received: from fw.osdl.org ([65.172.181.6]:22941 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S264432AbTLCAKL (ORCPT ); Tue, 2 Dec 2003 19:10:11 -0500 Date: Tue, 2 Dec 2003 16:03:03 -0800 From: "Randy.Dunlap" To: Vince Cc: mfedyk@matchmail.com, zwane@arm.linux.org.uk, linux-kernel@vger.kernel.org Subject: Re: [kernel panic @ reboot] 2.6.0-test10-mm1 Message-Id: <20031202160303.2af39da0.rddunlap@osdl.org> In-Reply-To: <3FC53A3B.50601@free.fr> References: <3FC4DA17.4000608@free.fr> <3FC4E42A.40906@free.fr> <3FC4E8C8.4070902@free.fr> <20031126233738.GD1566@mis-mike-wstn.matchmail.com> <3FC53A3B.50601@free.fr> Organization: OSDL X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i686-pc-linux-gnu) X-Face: +5V?h'hZQPB9kW Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 27 Nov 2003 00:41:47 +0100 Vince wrote: | Mike Fedyk wrote: | > Interesting. It would be nice to have a boot option that halts the system | > after the first oops, instead of trying to continue. You mean like the "panic_on_oops" sysctl?? (implemented in i386 & ppc64) | > Vince/Randy: | > Did you use the 2.5.65 patch at http://w.ods.org/tools/kmsgdump/ or is there | > some other place that has newer patches? | > | > BTW, http://www.xenotime.net/linux/kmsgdump gives a 404 error. | | My version comes from: | http://developer.osdl.org/rddunlap/kmsgdump/ Yes, kmsgdump is now here ^^^^^^^^^^^^^^^^^^. Sorry about any confusion there. >>From Vince: | It worked, but I had -- as expected -- to write the oops by hand. | (user request to Randy: would it be possible to have an option in | kmsgdump to only write the first oops on floppy ???) Um, could you elaborate on why you would want that? kmsgdump assumes that the entire floppy belongs to it, so there should be plenty of room for multiple oopsen (although I don't know what it does on disk-full....). I plan to add support for > 32 KB log buf sizes, but that's all I have planned for now. -- ~Randy MOTD: Always include version info.