Re: source line numbers with x86_64 modules? [Was: Re: [patch] measurements, numbers about CONFIG_OPTIMIZE_INLINING=y impact]

["Mike Snitzer" <snitzer@gmail.com>]

On Sun, Jan 11, 2009 at 5:11 AM, Andreas Dilger <adilger@sun.com> wrote:
> 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.

Less usable in terms of ease of configuration and use?  Or
reliability?  In practice netdump's non-interrupt-driven polling mode
proved fairly reliable but it seems to me kdump provides more reliable
dumping than netdump.  Because you're performing the kdump from a
reliable new dump kernel (provided the initial kexec transition to the
dump kernel works properly).

Mike