[Bug 206235] New: kernel BUG at mm/slub.c:294

All of lore.kernel.org
 help / color / mirror / Atom feed

From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 206235] New: kernel BUG at mm/slub.c:294
Date: Fri, 17 Jan 2020 13:38:51 +0000	[thread overview]
Message-ID: <bug-206235-62941@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=206235

            Bug ID: 206235
           Summary: kernel BUG at mm/slub.c:294
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.19.94
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: steffen@sdaoden.eu
        Regression: No

during a "sudo rfkill block all" with a bluealsa device still paired (normally
i unpair first, first time i did not i think) i got this oops:

Jan 17 01:34:05 kent kernel: ------------[ cut here ]------------
Jan 17 01:34:05 kent kernel: kernel BUG at mm/slub.c:294!
Jan 17 01:34:05 kent kernel: invalid opcode: 0000 [#1] PREEMPT SMP PTI
Jan 17 01:34:05 kent kernel: CPU: 0 PID: 16328 Comm: rfkill Tainted: G        
C        4.19.94-kent #1
Jan 17 01:34:05 kent kernel: Hardware name: LENOVO 81EU/LNVNB161216, BIOS
7PCN35WW 09/25/2018
Jan 17 01:34:05 kent kernel: RIP: 0010:__slab_free.isra.20+0x1b8/0x290
Jan 17 01:34:05 kent kernel: Code: 75 6a 80 7c 24 4b 00 79 05 40 84 f6 74 1e 48
8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 80 4c 24 4b 80 4d 89 ef e9 03 ff ff
ff <0f> 0b 48 8d 65 d8 4c 89 e6 4c 89 f7 ba 01 00 00 00 5b 41 5c 41 5d
Jan 17 01:34:05 kent kernel: RSP: 0018:ffffa6b840cebcc0 EFLAGS: 00010246
Jan 17 01:34:05 kent kernel: RAX: ffff95323b657a00 RBX: ffff95323b657a00 RCX:
ffff95323b657a00
Jan 17 01:34:05 kent kernel: RDX: 0000000080200005 RSI: ffffdd2dc5ed9580 RDI:
ffff953324d2b080
Jan 17 01:34:05 kent kernel: RBP: ffffa6b840cebd50 R08: 0000000000000001 R09:
ffff95323b657a00
Jan 17 01:34:05 kent kernel: R10: 00001a05f5d98974 R11: 0000000000001400 R12:
ffffdd2dc5ed9580
Jan 17 01:34:05 kent kernel: R13: ffff95323b657a00 R14: ffff953324d2b080 R15:
0000000000000000
Jan 17 01:34:05 kent kernel: FS:  00007f21f93c3740(0000)
GS:ffff953326a00000(0000) knlGS:0000000000000000
Jan 17 01:34:05 kent kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 17 01:34:05 kent kernel: CR2: 00007ffb6241f9d8 CR3: 000000010dbee002 CR4:
00000000003606f0
Jan 17 01:34:05 kent kernel: Call Trace:
Jan 17 01:34:05 kent kernel:  ? finish_wait+0x2a/0x60
Jan 17 01:34:05 kent kernel:  ? __hci_cmd_sync_ev+0x20a/0x230
Jan 17 01:34:05 kent kernel:  kmem_cache_free+0x195/0x1c0
Jan 17 01:34:05 kent kernel:  btrtl_shutdown_realtek+0x2b/0x50
Jan 17 01:34:05 kent kernel:  hci_dev_do_close+0x402/0x4c0
Jan 17 01:34:05 kent kernel:  hci_rfkill_set_block+0x37/0x50
Jan 17 01:34:05 kent kernel:  rfkill_set_block+0x8f/0x140
Jan 17 01:34:05 kent kernel:  rfkill_fop_write+0x12a/0x1d0
Jan 17 01:34:05 kent kernel:  __vfs_write+0x31/0x180
Jan 17 01:34:05 kent kernel:  vfs_write+0xa4/0x190
Jan 17 01:34:05 kent kernel:  ksys_write+0x52/0xd0
Jan 17 01:34:05 kent kernel:  do_syscall_64+0x5a/0x190
Jan 17 01:34:05 kent kernel:  ? prepare_exit_to_usermode+0x66/0x90
Jan 17 01:34:05 kent kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jan 17 01:34:05 kent kernel: RIP: 0033:0x7f21f94b0644
Jan 17 01:34:05 kent kernel: Code: 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b3
0f 1f 80 00 00 00 00 48 8d 05 b9 50 0d 00 8b 00 85 c0 75 13 b8 01 00 00 00 0f
05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 41 54 49 89 d4 55 48 89 f5 53
Jan 17 01:34:05 kent kernel: RSP: 002b:00007ffc78824028 EFLAGS: 00000246
ORIG_RAX: 0000000000000001
Jan 17 01:34:05 kent kernel: RAX: ffffffffffffffda RBX: 0000000000000003 RCX:
00007f21f94b0644
Jan 17 01:34:05 kent kernel: RDX: 0000000000000008 RSI: 00007ffc78824040 RDI:
0000000000000003
Jan 17 01:34:05 kent kernel: RBP: 0000000000000001 R08: 0000000000000003 R09:
0000000000000000
Jan 17 01:34:05 kent kernel: R10: fffffffffffff088 R11: 0000000000000246 R12:
0000000000000000
Jan 17 01:34:05 kent kernel: R13: 0000000000000000 R14: 0000000000000000 R15:
0000000000000000
Jan 17 01:34:05 kent kernel: Modules linked in: r8822be(C)
Jan 17 01:34:05 kent kernel: ---[ end trace 56293fc55f5cc3e0 ]---
Jan 17 01:34:05 kent kernel: RIP: 0010:__slab_free.isra.20+0x1b8/0x290
Jan 17 01:34:05 kent kernel: Code: 75 6a 80 7c 24 4b 00 79 05 40 84 f6 74 1e 48
8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 80 4c 24 4b 80 4d 89 ef e9 03 ff ff
ff <0f> 0b 48 8d 65 d8 4c 89 e6 4c 89 f7 ba 01 00 00 00 5b 41 5c 41 5d
Jan 17 01:34:05 kent kernel: RSP: 0018:ffffa6b840cebcc0 EFLAGS: 00010246
Jan 17 01:34:05 kent kernel: RAX: ffff95323b657a00 RBX: ffff95323b657a00 RCX:
ffff95323b657a00
Jan 17 01:34:05 kent kernel: RDX: 0000000080200005 RSI: ffffdd2dc5ed9580 RDI:
ffff953324d2b080
Jan 17 01:34:05 kent kernel: RBP: ffffa6b840cebd50 R08: 0000000000000001 R09:
ffff95323b657a00
Jan 17 01:34:05 kent kernel: R10: 00001a05f5d98974 R11: 0000000000001400 R12:
ffffdd2dc5ed9580
Jan 17 01:34:05 kent kernel: R13: ffff95323b657a00 R14: ffff953324d2b080 R15:
0000000000000000
Jan 17 01:34:05 kent kernel: FS:  00007f21f93c3740(0000)
GS:ffff953326a00000(0000) knlGS:0000000000000000
Jan 17 01:34:05 kent kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 17 01:34:05 kent kernel: CR2: 00007ffb6241f9d8 CR3: 000000010dbee002 CR4:
00000000003606f0

Linux kent 4.19.94-kent #1 SMP PREEMPT Sat Jan 11 22:44:47 CET 2020 x86_64
Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz GenuineIntel GNU/Linux

-- 
You are receiving this mail because:
You are the assignee for the bug.

next             reply	other threads:[~2020-01-17 13:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 13:38 bugzilla-daemon [this message]
2020-01-17 13:42 ` [Bug 206235] kernel BUG at mm/slub.c:294 bugzilla-daemon
2020-03-07 20:21 ` bugzilla-daemon
2020-03-07 20:25 ` bugzilla-daemon
2020-03-07 21:36 ` bugzilla-daemon
2020-07-04 15:26 ` bugzilla-daemon

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=bug-206235-62941@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    /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.