From: Hiro Yoshioka <hyoshiok@miraclelinux.com>
To: linux-kernel@vger.kernel.org
Cc: hyoshiok@miraclelinux.com
Subject: Linux Kernel Dump Summit 2005
Date: Wed, 21 Sep 2005 20:55:50 +0900 (JST) [thread overview]
Message-ID: <20050921.205550.927509530.hyoshiok@miraclelinux.com> (raw)
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
VA Linux/NEC/NSSOL/IPA/OSDL/Toshiba
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
device
power management
we need a generic mechanism to reset a device
- Hang
NMI watch dog
mount
- 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.
Regards,
Hiro
next reply other threads:[~2005-09-21 12:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 11:55 Hiro Yoshioka [this message]
2005-10-06 12:17 ` OBATA Noboru
2005-10-06 14:39 ` Hiro Yoshioka
2005-10-10 8:45 ` Pavel Machek
2005-10-12 8:28 ` OBATA Noboru
2005-10-12 9:02 ` Felix Oxley
2005-10-12 9:09 ` Pavel Machek
2005-10-12 9:56 ` Felix Oxley
2005-10-12 10:07 ` Pavel Machek
2005-10-12 18:03 ` Andy Isaacson
2005-10-12 22:34 ` Felix Oxley
2005-10-12 11:05 ` jerome lacoste
2005-10-12 21:10 ` Felix Oxley
2005-10-18 13:47 ` OBATA Noboru
2005-10-18 14:10 ` Hugh Dickins
2005-10-19 19:00 ` Theodore Ts'o
2005-10-27 7:48 ` OBATA Noboru
2005-10-11 0:49 ` Andrew Morton
2005-10-11 4:41 ` Hiro Yoshioka
2005-10-12 8:30 ` OBATA Noboru
2005-10-13 5:49 ` Maneesh Soni
2005-10-27 7:45 ` OBATA Noboru
2005-10-13 14:28 ` Troy Heber
2005-10-17 11:19 ` Takao Indoh
2005-10-18 13:48 ` OBATA Noboru
2005-10-19 3:17 ` Takao Indoh
2005-10-27 7:45 ` OBATA Noboru
2005-10-18 14:54 ` Carsten Otte
2005-10-14 9:19 hideki.takahashi
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=20050921.205550.927509530.hyoshiok@miraclelinux.com \
--to=hyoshiok@miraclelinux.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
all inboxes | Powered by JetHome®