public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Maneesh Soni <maneesh@in.ibm.com>
To: Folkert van Heusden <folkert@vanheusden.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: capturing oopses
Date: Mon, 28 Nov 2005 10:41:25 +0530	[thread overview]
Message-ID: <20051128051124.GA3849@in.ibm.com> (raw)
In-Reply-To: <20051122130754.GL32512@vanheusden.com>

On Tue, Nov 22, 2005 at 02:07:54PM +0100, Folkert van Heusden wrote:

> the stacktrace. The crash dump patches mentioned in oops-tracing.txt all
> don't work for 2.6.14 it seems. So: what should I do? Get my digicam and

could you try kdump (Documentation/kdump/kdump.txt) to capture the crash 
dump. It is part of mainline kernel atleast for i386 architecture. It 
should work for 2.6.14 also.

Thanks
Maneesh

-- 
Maneesh Soni
Linux Technology Center, 
IBM India Software Labs,
Bangalore, India
email: maneesh@in.ibm.com
Phone: 91-80-25044990

  parent reply	other threads:[~2005-11-28  5:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22 13:07 capturing oopses Folkert van Heusden
2005-11-22 14:08 ` bert hubert
2005-11-23  1:27   ` Brice Goglin
2005-11-23 10:55   ` Folkert van Heusden
2005-11-23 11:17     ` bert hubert
2005-11-26 15:56 ` Adrian Bunk
2005-11-26 19:33   ` Ville Herva
2005-11-28  4:41     ` Randy.Dunlap
2005-11-28 16:20       ` mgross
2005-11-28 16:42         ` Christopher Friesen
2005-11-28 19:35         ` Ville Herva
2005-11-28  5:11 ` Maneesh Soni [this message]
     [not found] <5bG4q-8ks-17@gated-at.bofh.it>
     [not found] ` <5daDm-1Cg-15@gated-at.bofh.it>
     [not found]   ` <5de3Z-6CJ-13@gated-at.bofh.it>
2005-11-27  1:10     ` Bodo Eggert
2005-11-27 12:16       ` Ville Herva
2005-11-27 13:55         ` Sander
2005-11-27 14:44           ` Ville Herva
2005-11-27 14:56             ` Ville Herva

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051128051124.GA3849@in.ibm.com \
    --to=maneesh@in.ibm.com \
    --cc=folkert@vanheusden.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox