From: Andreas Dilger <adilger@sun.com>
To: Theodore Tso <tytso@mit.edu>, Mike Snitzer <snitzer@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Nicholas Miell <nmiell@comcast.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
jim
Subject: Re: source line numbers with x86_64 modules? [Was: Re: [patch] measurements, numbers about CONFIG_OPTIMIZE_INLINING=y impact]
Date: Sun, 11 Jan 2009 18:11:35 +0800 [thread overview]
Message-ID: <20090111101135.GA3306@webber.adilger.int> (raw)
In-Reply-To: <20090110211531.GD31579@mit.edu>
On Jan 10, 2009 16:15 -0500, Theodore Ts'o wrote:
> In my experience, there are very few kernel versions and hardware for
> which kdump works. I've talked to the people who have to make kdump
> work, and every 12-18 months, with a new set of enterprise kernels
> comes out, they have to go and fix kdump so it works again for the set
> of hardware that they care about, and for the kernel version involved.
I'm sad that netconsole/netdump never made it big. It was fairly useful,
and extending the eth drivers to add the polling mode was trivial to do.
We were using that for a few years, but it got replaced by kdump and it
appears to be less usable IMHO.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Dilger <adilger@sun.com>
To: Theodore Tso <tytso@mit.edu>, Mike Snitzer <snitzer@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Nicholas Miell <nmiell@comcast.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
jim owens <jowens@hp.com>, "H. Peter Anvin" <hpa@zytor.com>,
Chris Mason <chris.mason@oracle.com>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
paulmck@linux.vnet.ibm.com, Gregory Haskins <ghaskins@novell.com>,
Matthew Wilcox <matthew@wil.cx>, Andi Kleen <andi@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Nick Piggin <npiggin@suse.de>,
Peter Morreale <pmorreale@novell.com>,
Sven Dietrich <SDietrich@novell.com>,
sam@ravnborg.org, Dave Anderson <anderson@redhat.com>
Subject: Re: source line numbers with x86_64 modules? [Was: Re: [patch] measurements, numbers about CONFIG_OPTIMIZE_INLINING=y impact]
Date: Sun, 11 Jan 2009 18:11:35 +0800 [thread overview]
Message-ID: <20090111101135.GA3306@webber.adilger.int> (raw)
In-Reply-To: <20090110211531.GD31579@mit.edu>
On Jan 10, 2009 16:15 -0500, Theodore Ts'o wrote:
> In my experience, there are very few kernel versions and hardware for
> which kdump works. I've talked to the people who have to make kdump
> work, and every 12-18 months, with a new set of enterprise kernels
> comes out, they have to go and fix kdump so it works again for the set
> of hardware that they care about, and for the kernel version involved.
I'm sad that netconsole/netdump never made it big. It was fairly useful,
and extending the eth drivers to add the polling mode was trivial to do.
We were using that for a few years, but it got replaced by kdump and it
appears to be less usable IMHO.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2009-01-11 10:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 14:21 source line numbers with x86_64 modules? [Was: Re: [patch] measurements, numbers about CONFIG_OPTIMIZE_INLINING=y impact] Mike Snitzer
2009-01-10 15:34 ` Ingo Molnar
2009-01-10 18:21 ` Mike Snitzer
2009-01-10 21:15 ` Theodore Tso
2009-01-10 22:21 ` Andi Kleen
2009-01-10 22:21 ` Andi Kleen
2009-01-10 22:58 ` Linus Torvalds
2009-01-10 23:22 ` Ingo Molnar
2009-01-10 22:21 ` Andi Kleen
2009-01-11 10:11 ` Andreas Dilger
2009-01-11 10:11 ` Andreas Dilger [this message]
2009-01-11 10:11 ` Andreas Dilger
2009-01-11 15:31 ` Mike Snitzer
2009-01-11 15:31 ` Mike Snitzer
2009-01-11 20:45 ` Theodore Tso
2009-01-11 1:28 ` Ingo Molnar
2009-01-11 4:52 ` Mike Snitzer
2009-01-13 3:19 ` Eric W. Biederman
2009-01-13 3:19 ` Eric W. Biederman
2009-01-13 3:19 ` Eric W. Biederman
2009-01-11 18:05 ` Andi Kleen
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=20090111101135.GA3306@webber.adilger.int \
--to=adilger@sun.com \
--cc=mingo@elte.hu \
--cc=nmiell@comcast.net \
--cc=snitzer@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.