From: David Sterba <dsterba@suse.cz>
To: Anatoly Pugachev <matorola@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
debian-sparc <debian-sparc@lists.debian.org>
Subject: Re: [sparc64] mkfs.btrfs bus error / align issue?
Date: Fri, 29 Jul 2016 14:41:30 +0200 [thread overview]
Message-ID: <20160729124129.GA30795@suse.cz> (raw)
In-Reply-To: <CADxRZqzt8m6j_GktpKYYmDar=hDYy07DhyiuPJ-gMgtGfiGhXQ@mail.gmail.com>
On Thu, Jul 28, 2016 at 11:34:58PM +0300, Anatoly Pugachev wrote:
> well, I think mkfs.btrfs is fixed, since I just tested it with :
Good news, thanks.
> Not sure what we need to do with sparc64 btrfs module TPC messages.
> Probably fill kernel bugzilla report?
Yes please.
> [1] http://u163.east.ru/btrfs/xfstests-btrfs-06x-results.tar.gz
> [2] http://u163.east.ru/btrfs/kernel-4.7.0+-logs-xfstests-06x.txt.gz
quick stats of the TPC messages:
23 __btrfs_map_block+0x36c/0x1180
9 __remove_rbio_from_cache+0x38/0x140
6 lock_stripe_add+0xb0/0x360
4 __btrfs_map_block+0x3d4/0x1180
3 __btrfs_map_block+0xca0/0x1180
running in 'gdb btrfs.ko' for each of the addresses should tell us what are the
locations:
gdb> l *(__btrfs_map_block+0x36c)
...
Thanks.
next prev parent reply other threads:[~2016-07-29 12:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 13:59 [sparc64] mkfs.btrfs bus error / align issue? Anatoly Pugachev
2016-07-27 19:56 ` David Sterba
2016-07-28 9:44 ` David Sterba
2016-07-28 11:58 ` Anatoly Pugachev
2016-07-28 12:02 ` John Paul Adrian Glaubitz
2016-07-28 12:09 ` John Paul Adrian Glaubitz
2016-07-28 12:24 ` David Sterba
2016-07-28 14:01 ` Anatoly Pugachev
2016-07-28 14:25 ` John Paul Adrian Glaubitz
2016-07-28 14:28 ` John Paul Adrian Glaubitz
2016-07-28 14:32 ` Patrick Baggett
2016-07-28 18:04 ` David Sterba
2016-07-28 20:34 ` Anatoly Pugachev
2016-07-29 9:40 ` Anatoly Pugachev
2016-07-29 12:41 ` David Sterba [this message]
2016-07-29 15:03 ` Anatoly Pugachev
2016-07-29 10:20 ` John Paul Adrian Glaubitz
2016-07-27 20:39 ` Patrick Baggett
2016-07-27 20:41 ` Patrick Baggett
2016-07-27 20:40 ` John Paul Adrian Glaubitz
2016-07-27 20:48 ` Patrick Baggett
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=20160729124129.GA30795@suse.cz \
--to=dsterba@suse.cz \
--cc=debian-sparc@lists.debian.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=matorola@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 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.