[lkml]   [2005]   [Sep]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectLinux Kernel Dump Summit 2005
To whom may concern

We had a Linux Kernel Dump Summit 2005.

The participants are

Dump tools Session
diskdump -- Fujitsu
mkdump -- NTT Data Intellilink
LTD -- Hitachi
kdump -- Turbolinux
Summary -- Miracle Linux

Dump Analysis tools Session
Alicia/crash -- Uniadex

Other participants are

Some discussion topics are (but not limited to)

- What kind of information do we need?
trace information
all of registers
the last log of panic, oops
LTD (Linux Tough Dump) has some nice features

- We need a partial dump
- We have to minimize the down time

- We have to dump all memory
how can we distinguish from the kernel and user if
kernel data is corrupted

- How we are not able to dump data
power management
we need a generic mechanism to reset a device

- Hang
NMI watch dog

- It is very difficult to debug a memory corrupt bug
- hardware error

- Where will we go to?
IHV and Linux Kernel community collaboration are needed

Dump Analysis tools are very important

- There is a concern that the development process of 'crash'
is not open.
- Do we have to extend gdb?
- We'd like to collaborate 'crash'

- kexec/kdump, mkdump, LTD, all of them use the second kernel
to dump it.

- We have to share the test data, check list, test tools of
dump tool developments.

We agree to have the Linux Kernel Dump Summit.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-09-21 14:02    [W:0.135 / U:1.520 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site