From: Vivek Goyal <vgoyal@redhat.com>
To: Kent Overstreet <koverstreet@google.com>
Cc: lsf-pc@lists.linux-foundation.org, nauman@google.com,
linux-scsi@vger.kernel.org, dm-devel@redhat.com
Subject: Re: [Lsf-pc] [Topic] Bcache
Date: Thu, 15 Mar 2012 15:43:36 -0400 [thread overview]
Message-ID: <20120315194336.GH3253@redhat.com> (raw)
In-Reply-To: <CAH+dOxKxZYSdZfewt5mHsvOk68VfNKzMQveibGLM+qunV6mOMw@mail.gmail.com>
On Wed, Mar 14, 2012 at 01:24:08PM -0400, Kent Overstreet wrote:
[..]
>
> Can you post the full log? There was a bug where if it encountered an
> error during registration, it wouldn't wait for a uuid read or write
> before tearing everything down - that's what your backtrace looks like
> to me.
>
> You could try the bcache-3.2-dev branch, too. I have a newer branch
> with a ton of bugfixes but I'm waiting until it's seen more testing
> before I post it.
Faced the same issue on bcache-3.2-dev branch too.
login: [ 167.532932] bio: create slab <bio-1> at 1
[ 167.539071] bcache: invalidating existing data
[ 167.547604] general protection fault: 0000 [#1] SMP DEBUG_PAGEALLOC
[ 167.548573] CPU 2
[ 167.548573] Modules linked in: floppy [last unloaded: scsi_wait_scan]
[ 167.548573]
[ 167.548573] Pid: 0, comm: swapper/2 Not tainted 3.2.0-bcache+ #4
Hewlett-Packard HP xw6600 Workstation/0A9Ch
[ 167.548573] RIP: 0010:[<ffffffff8144d6fe>] [<ffffffff8144d6fe>]
closure_put+0xe/0x20
[ 167.548573] RSP: 0018:ffff88013fc83c60 EFLAGS: 00010246
[ 167.548573] RAX: 0000000000000000 RBX: ffff8801385b04a0 RCX:
0000000000000000
[ 167.548573] RDX: 0000000000000000 RSI: 00000000ffffffff RDI:
6b6b6b6b6b6b6b6b
[ 167.548573] RBP: ffff88013fc83c60 R08: 0000000000000000 R09:
0000000000000001
[ 167.548573] R10: 0000000000000000 R11: 0000000000000000 R12:
0000000000000000
[ 167.548573] R13: ffff880137719580 R14: 0000000000080000 R15:
0000000000000000
[ 167.548573] FS: 0000000000000000(0000) GS:ffff88013fc80000(0000)
knlGS:0000000000000000
[ 167.548573] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 167.548573] CR2: 00007f6e84f70240 CR3: 000000013707d000 CR4:
00000000000006e0
[ 167.548573] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[ 167.548573] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
0000000000000400
[ 167.548573] Process swapper/2 (pid: 0, threadinfo ffff88013a454000,
task ffff88013a458000)
[ 167.548573] Stack:
[ 167.548573] ffff88013fc83c80 ffffffff814448c6 ffffffff00000000
ffff8801385b04a0
[ 167.548573] ffff88013fc83c90 ffffffff8117ae8d ffff88013fc83cc0
ffffffff812e2273
[ 167.548573] ffff88013a454000 0000000000000000 ffff8801385b04a0
0000000000080000
[ 167.548573] Call Trace:
[ 167.548573] <IRQ>
[ 167.548573] [<ffffffff814448c6>] uuid_endio+0x36/0x40
[ 167.548573] [<ffffffff8117ae8d>] bio_endio+0x1d/0x40
[ 167.548573] [<ffffffff812e2273>] req_bio_endio+0x83/0xc0
[ 167.548573] [<ffffffff812e53e1>] blk_update_request+0x101/0x5c0
[ 167.548573] [<ffffffff812e5612>] ? blk_update_request+0x332/0x5c0
[ 167.548573] [<ffffffff812e58d1>] blk_update_bidi_request+0x31/0x90
[ 167.548573] [<ffffffff812e595c>] blk_end_bidi_request+0x2c/0x80
[ 167.548573] [<ffffffff812e59f0>] blk_end_request+0x10/0x20
[ 167.548573] [<ffffffff81458fdc>] scsi_io_completion+0x9c/0x5f0
[ 167.548573] [<ffffffff8144fcd0>] scsi_finish_command+0xb0/0xe0
[ 167.548573] [<ffffffff81458dc5>] scsi_softirq_done+0xa5/0x140
[ 167.548573] [<ffffffff812ec55b>] blk_done_softirq+0x7b/0x90
[ 167.548573] [<ffffffff810512ae>] __do_softirq+0xce/0x3c0
[ 167.548573] [<ffffffff817e84ac>] call_softirq+0x1c/0x30
[ 167.548573] [<ffffffff8100417d>] do_softirq+0x8d/0xc0
[ 167.548573] [<ffffffff810518de>] irq_exit+0xae/0xe0
[ 167.548573] [<ffffffff817e8bb3>] do_IRQ+0x63/0xe0
[ 167.548573] [<ffffffff817de1f0>] common_interrupt+0x70/0x70
[ 167.548573] <EOI>
[ 167.548573] [<ffffffff8100a5f6>] ? mwait_idle+0xb6/0x490
[ 167.548573] [<ffffffff8100a5ed>] ? mwait_idle+0xad/0x490
[ 167.548573] [<ffffffff810011e6>] cpu_idle+0x96/0xe0
[ 167.548573] [<ffffffff817cb475>] start_secondary+0x1be/0x1c2
[ 167.548573] Code: ee 01 00 00 10 e8 03 ff ff ff 48 85 db 75 de 5b 41 5c
5d c3 66 0f 1f 84 00 00 00 00 00 55 48 89 e5 66 66 66 66 90 be ff ff ff ff
<f0> 0f c1 77 48 83 ee 01 e8 d5 fe ff ff 5d c3 0f 1f 00 55 48 89
[ 167.548573] RIP [<ffffffff8144d6fe>] closure_put+0xe/0x20
[ 167.548573] RSP <ffff88013fc83c60>
Thanks
Vivek
next prev parent reply other threads:[~2012-03-15 19:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 13:32 [Topic] Bcache Kent Overstreet
2012-03-14 15:53 ` [Lsf-pc] " Vivek Goyal
2012-03-14 17:24 ` Kent Overstreet
2012-03-14 22:01 ` Bcache Mike Snitzer
2012-03-14 22:09 ` [Lsf-pc] Bcache Williams, Dan J
2012-03-15 17:27 ` Bcache Kent Overstreet
2012-03-15 20:17 ` Bcache Mike Snitzer
2012-03-15 22:59 ` Bcache Kent Overstreet
2012-03-16 1:45 ` Bcache Mike Snitzer
2012-03-15 19:43 ` Vivek Goyal [this message]
2012-03-15 23:46 ` [Lsf-pc] [Topic] Bcache Kent Overstreet
2012-03-14 18:12 ` chetan loke
2012-03-14 18:17 ` Kent Overstreet
2012-03-14 18:33 ` chetan loke
2012-03-14 18:41 ` Kent Overstreet
2012-03-14 18:47 ` Christoph Hellwig
2012-03-14 19:04 ` chetan loke
2012-03-15 17:01 ` Kent Overstreet
2012-03-14 18:54 ` Ted Ts'o
2012-03-14 19:22 ` chetan loke
2012-03-15 17:02 ` Kent Overstreet
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=20120315194336.GH3253@redhat.com \
--to=vgoyal@redhat.com \
--cc=dm-devel@redhat.com \
--cc=koverstreet@google.com \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=nauman@google.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