From: Cong Wang <xiyou.wangcong@gmail.com>
To: Chester <somethingsome2000@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: How to get trace during crash?
Date: Wed, 01 Feb 2012 10:07:50 +0800 [thread overview]
Message-ID: <4F289E76.8070103@gmail.com> (raw)
In-Reply-To: <CAAE6i0ianz6CvFNLRCEPOyoQ4UPwZDg3WYqk+pj0AL-mjfac5Q@mail.gmail.com>
On 02/01/2012 02:04 AM, Chester wrote:
> In the event of a filesystem crash, how do I extract the debugging
> info for the mailing list? My attempts to SSH into the machine are
> unresponsive.
>
In this case, probably you need netconsole, see
Documentation/networking/netconsole.txt for details.
prev parent reply other threads:[~2012-02-01 2:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 18:04 How to get trace during crash? Chester
2012-02-01 2:07 ` Cong Wang [this message]
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=4F289E76.8070103@gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=somethingsome2000@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).