From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from out01.mta.xmission.com ([166.70.13.231]) by bombadil.infradead.org with esmtp (Exim 4.69 #1 (Red Hat Linux)) id 1MGS1I-0000gZ-LR for kexec@lists.infradead.org; Tue, 16 Jun 2009 06:19:51 +0000 References: <9c8decfb07c.00000038dseetharam@inbox.com> <913da90c6c8.0000039bdseetharam@inbox.com> From: ebiederm@xmission.com (Eric W. Biederman) Date: Mon, 15 Jun 2009 23:19:33 -0700 In-Reply-To: (Dharmosoth Seetharam's message of "Mon\, 15 Jun 2009 20\:43\:02 -0800") Message-ID: MIME-Version: 1.0 Subject: Re: /var/log/messages doesn't have crash info when kernel gets panic/oops/crash List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: kexec-bounces@lists.infradead.org Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Dharmosoth Seetharam Cc: Neil Horman , vgoyal@in.ibm.com, kexec@lists.infradead.org, fastboot@lists.linux-foundation.org Dharmosoth Seetharam writes: > Hi, > > I have experimented few things and results are below. > > Case 1) echo 0 > /proc/sys/kernel/panic_on_oops > When BUG/oops occurred it is able to log the diagnostics to /var/log/messages > and then continue(not switching to dump-saving kernel). > > What I am looking is - I want both the things to be happen. > that is - it should log the appropriate messages in /var/log/messsages and > should be able to take kernel dump. You can't have it. Sorry. Keeping user space alive is something that simply can not be done reliably. > Please advice me, What we can do to achieve those things. The only scenario I see possible is to take the dump. Use makedumpfile or the crash log command to extract the kernel messages and put them in the /var/log/messages. Eric _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec