Bug ID 1147412
Summary bcache-register fails during boot, leaving backing store busy
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware x86-64
OS Linux
Status NEW
Severity Normal
Priority P5 - None
Component Kernel
Assignee kernel-maintainers@forge.provo.novell.com
Reporter garynb@qx.net
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

have a 16GB(Ha!) Optane and a 128GB SSD both mounted to an expansion card (same
one actually) in a pcie slot.  After some fumbling around I got it to work
using the  Optane to cache the SSD.  I'm playing around here, not trying to get
anything useful done.

Works for a few weeks then apparently, some update breaks it (no I do not have
a clear idea of what/when).  I get something like the following:

 snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
------------[ cut here ]------------
kernel BUG at drivers/md/bcache/bset.h:433!
invalid opcode: 0000 [#1] SMP NOPTI
CPU: 1 PID: 668 Comm: bcache-register Not tainted 5.2.8-1-default #1 openSUSE
Tumbleweed (unreleased)
Hardware name: To be filled by O.E.M. To be filled by O.E.M./M5A97, BIOS 1605
10/25/2012
RIP: 0010:bch_extent_sort_fixup+0x724/0x730 [bcache]
Code: ff ff 4c 89 c8 e9 3e ff ff ff 49 39 f1 0f 97 c1 e9 74 ff ff ff 49 39 f2
41 0f 97 c5 e9 12 ff ff f>
RSP: 0018:ffff9773c239fa38 EFLAGS: 00010286
RAX: fffffffffffe242d RBX: ffff8ab82f878020 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff9773c239faf8
RBP: ffff9773c239fa90 R08: 000000000773e168 R09: ffff8ab8209d8860
R10: 0000000000000000 R11: 0000000000000001 R12: 000000000775bea0
R13: 000000000775bec0 R14: ffff9773c239fae0 R15: ffff8ab82f878000
FS:  00007f498bb36bc0(0000) GS:ffff8ab832a40000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fdc60a79fe8 CR3: 0000000330250000 CR4: 00000000000406e0
Call Trace:
 btree_mergesort+0x19b/0x5c0 [bcache]
 ? bch_cache_allocator_start+0x50/0x50 [bcache]
 __btree_sort+0x9e/0x1d0 [bcache]
 bch_btree_node_read_done+0x2cb/0x3c0 [bcache]
 bch_btree_node_read+0xdb/0x180 [bcache]
 ? bch_keybuf_init+0x60/0x60 [bcache]
 bch_btree_check_recurse+0x127/0x1f0 [bcache]
 ? bch_extent_to_text+0x10f/0x190 [bcache]
 bch_btree_check+0x18e/0x1b0 [bcache]
 ? wait_woken+0x70/0x70
 run_cache_set+0x487/0x730 [bcache]
 register_bcache+0xc0b/0xf90 [bcache]
 ? __seccomp_filter+0x7b/0x640
 ? kernfs_fop_write+0x10e/0x190
 kernfs_fop_write+0x10e/0x190
 vfs_write+0xb6/0x1a0
 ksys_write+0x4f/0xc0
 do_syscall_64+0x6e/0x1e0
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f498b97e874
Code: 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 48 8d
05 c9 49 0d 00 8b 00 85 c>
RSP: 002b:00007ffc7657ed38 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 000000000000000f RCX: 00007f498b97e874
RDX: 000000000000000f RSI: 0000557c6b6c0260 RDI: 0000000000000003
RBP: 0000557c6b6c0260 R08: 00000000ffffffff R09: 000000000000000f
R10: 00007ffc76580ac7 R11: 0000000000000246 R12: 000000000000000f
R13: 00007ffc7657edc0 R14: 000000000000000f R15: 00007f498ba4e7c0
Modules linked in: snd_hda_codec_realtek(+) crc32_pclmul snd_hda_codec_generic
ghash_clmulni_intel fjes>
---[ end trace 4587505d36f45756 ]---
RIP: 0010:bch_extent_sort_fixup+0x724/0x730 [bcache]
Code: ff ff 4c 89 c8 e9 3e ff ff ff 49 39 f1 0f 97 c1 e9 74 ff ff ff 49 39 f2
41 0f 97 c5 e9 12 ff ff f>
RSP: 0018:ffff9773c239fa38 EFLAGS: 00010286
RAX: fffffffffffe242d RBX: ffff8ab82f878020 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff9773c239faf8
RBP: ffff9773c239fa90 R08: 000000000773e168 R09: ffff8ab8209d8860
R10: 0000000000000000 R11: 0000000000000001 R12: 000000000775bea0
R13: 000000000775bec0 R14: ffff9773c239fae0 R15: ffff8ab82f878000
FS:  00007f498bb36bc0(0000) GS:ffff8ab832a40000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fdc60a79fe8 CR3: 0000000330250000 CR4: 00000000000406e0


afterwards the backing device is busy, and I cannot do anything with it,
presumably because bcache-register never finishes.


You are receiving this mail because: