[2/3] 2.6.22-rc2: known regressions v2

[Vivek Goyal]

On Fri, May 25, 2007 at 09:33:54AM -0700, Andrew Morton wrote:
> On Fri, 25 May 2007 14:34:56 +0200 Ingo Molnar <mingo at elte.hu> wrote:
> 
> > * Chris Newport <crn at netunix.com> wrote:
> > 
> > > There is a fundamental problem in getting a decent log to debug a 
> > > crashed kernel.  Maybe we should take a hint from Solaris. If the 
> > > kernel crashes Solaris dumps core to swap and sets a flag. At the next 
> > > boot this image is copied to /var/adm/crashdump where it is preserved 
> > > for future debugging. Obviously swap needs to be larger than core, but 
> > > this is usually the case.
> > 
> > we've got kdump, but it's not usually enabled by default by distros.
> 
> Isn't that awful?
> 

I think kdump should be enabled by default. Or at least user should be
given an option to enable/configure this service at installation time.

Things are still good atleast in RHEL5. It gives user a option to
enable/disable kdump at firstboot after installation. A fall side of
doing it at firstboot time is that a user has to go for an extra reboot
if he chooses to enable kdump (Because of kernel command line crashkernel=).
An improvemnt could be that these options should be given at installation
time so that a user does not have to go through an extra reboot to enable
kdump service. 

It also has got graphical scripts to configure kdump serivce and enable it.
Other distributions are catching up but there seems to be a reluctance
to enable kdump by default primarily because of a chunk of memory being
reserved for kdump kernel which can not be used by regular kernel.

As of today RHEL reserves 128MB of memory for x86/x86_64 arch if kdump
is enabled. Some people are also reluctant to change the installer to
include a screen which can help user enable/disable/configure kdump. They
think it increases installer complexity and user is likely to get confused.

> By now we should be in the situation where if a tester is hitting a
> kernel crash we can say to them "please turn on crashdumps and send me
> the image".  But we're not - kernel developers don't know how to turn the
> thing on in $RANDOM_DISTRO, testers have no experience with the feature
> and kernel developers don't have experience handling the crash images.
> 
> And I'm not sure that the (required) "don't dump user memory and pagecache"
> feature has been implemented yet?
> 

Yes. It has been implemented and integrated with RHEL5. Not sure about others.
NEC developers have developed a user space filtering utility which can filter
out pagecache, user memory and zero pages.

http://sourceforge.net/projects/makedumpfile

In RHEL5, one can pre-configure filtering options and a filtered crash
dump will automatically be saved to user configured destination.
 
Thanks
Vivek