All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <tch@virtall.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: kernel crashes with btrfs and busy database IO - how to debug?
Date: Fri, 12 Jun 2015 17:35:11 +0900	[thread overview]
Message-ID: <73cb882c23a71c9039a0e7bbfddfab64@admin.virtall.com> (raw)
In-Reply-To: <557A8691.6070908@cn.fujitsu.com>

On 2015-06-12 16:13, Qu Wenruo wrote:

>> Remote syslog does not capture anything.
> No backtrace?

No (nothing saved on disk, don't have VNC access).

The only way to capture anything is:

while true; do dmesg -c ; done

but that's usually incomplete.


> Without backtrace, it's much harder to debug for us.
> It's quite possible that some codes go mad and pass a NULL pointer,
> and then wait_event() is called on the NULL->some_member.
> 
> Anyway, backtrace is needed to debug this.
> 
> If syslog can't help, what about kdump + crash to get the backtrace?

I'll try to get a kdump + crash.

-- 
Tomasz Chmielewski
http://wpkg.org


  reply	other threads:[~2015-06-12  8:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11 11:33 kernel crashes with btrfs and busy database IO - how to debug? Tomasz Chmielewski
2015-06-12  7:13 ` Qu Wenruo
2015-06-12  8:35   ` Tomasz Chmielewski [this message]
2015-06-12  9:09     ` Qu Wenruo
2015-06-12 23:23       ` Tomasz Chmielewski
2015-06-14  0:30         ` Tomasz Chmielewski
2015-06-14  7:58           ` Tomasz Chmielewski
2015-06-15  8:10             ` Qu Wenruo
2015-06-15 10:31               ` Tomasz Chmielewski
2015-06-12  7:53 ` Duncan
2015-06-12 16:26 ` Chris Mason

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=73cb882c23a71c9039a0e7bbfddfab64@admin.virtall.com \
    --to=tch@virtall.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo@cn.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.