From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758127AbcIHQRE (ORCPT ); Thu, 8 Sep 2016 12:17:04 -0400 Received: from mail-it0-f43.google.com ([209.85.214.43]:34871 "EHLO mail-it0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757951AbcIHQRB (ORCPT ); Thu, 8 Sep 2016 12:17:01 -0400 Subject: Re: kernel 4.8-rc5 kernel BUG at block/blk-core.c:2032! To: Stefan Priebe - Profihost AG , linux-block@vger.kernel.org References: <56e78c6a-5996-d106-2952-d985ceca9e34@profihost.ag> Cc: linux-kernel@vger.kernel.org, Shaohua Li From: Jens Axboe Message-ID: <7ad7efe2-ef46-e1d5-bb0d-c7ed0e8d47db@kernel.dk> Date: Thu, 8 Sep 2016 10:16:59 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <56e78c6a-5996-d106-2952-d985ceca9e34@profihost.ag> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/08/2016 02:23 AM, Stefan Priebe - Profihost AG wrote: > Hi, > > while trying Kernel 4.8-rc5 my raid5 breaks every few minutes. > > Trace: > ------------[ cut here ]------------ > kernel BUG at block/blk-core.c:2032! > invalid opcode: 0000 [#1] SMP > Modules linked in: netconsole ipt_REJECT nf_reject_ipv4 xt_multiport > iptable_filter ip_tables x_tables 8021q garp bonding sb_edac edac_core > x86_pkg_temp_thermal coretemp kvm_intel kvm i2c_i801 irqbypass i2c_smbus > ipmi_si crc32_pclmul i2c_core ghash_clmulni_intel shpchp ipmi_msghandler > button loop fuse btrfs dm_mod raid10 raid0 multipath linear raid456 > async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq > raid1 md_mod sg sd_mod ixgbe i40e mdio usbhid ehci_pci ehci_hcd ahci > usbcore ptp libahci usb_common megaraid_sas pps_core > CPU: 8 PID: 1105 Comm: md0_raid5 Not tainted 4.8.0-rc5-00003-g3abda5c #2 > Hardware name: Supermicro X10DRH/X10DRH-iT, BIOS 1.0c 02/18/2015 > task: ffff97de5e1e0000 task.stack: ffff97de597a0000 > RIP: 0010:[] [] > generic_make_request+0x1c0/0x1d0 > RSP: 0018:ffff97de597a3aa0 EFLAGS: 00010286 > RAX: ffff97de5e1e0000 RBX: ffff97dd227e5030 RCX: 0000000000000000 > RDX: ffffffffc0000001 RSI: 0000000000000001 RDI: ffff97de5e7d9db8 > RBP: ffff97de597a3ad8 R08: 0000000000000008 R09: 0000000000000000 > R10: 0000000000000000 R11: 0000000000000001 R12: 00000000ffffffff > R13: ffff97de5aa20c00 R14: 00000000000002f0 R15: ffff97e65dce0e00 > FS: 0000000000000000(0000) GS:ffff97e67f200000(0000) knlGS:0000000000000000 > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: 00007f0e4e1ec000 CR3: 0000000078c06000 CR4: 00000000001406e0Stack: > ffff97de597a3b50 0000000000001000 0000000000000000 ffff97dd227e4c80 > ffff97de5aa20c00 00000000000002f0 ffff97e65dce0e00 ffff97de597a3ba0 > ffffffffc02595db ffffffffc025e04b 00000001597a3b01 0000000200000006 > Call Trace: > [] ops_run_io+0x3bb/0x990 [raid456] > [] ? raid_run_ops+0xefb/0x1520 [raid456] > [] handle_stripe+0x9a6/0x2280 [raid456] > [] ? default_wake_function+0x12/0x20 > [] ? autoremove_wake_function+0x12/0x40 > [] handle_active_stripes.isra.54+0x193/0x4b0 [raid456] > [] ? __release_stripe+0x15/0x20 [raid456] > [] raid5d+0x4a9/0x740 [raid456] > [] ? init_timer_key+0xa0/0xa0 > [] md_thread+0x12b/0x130 [md_mod] > [] ? wait_woken+0x90/0x90 > [] ? find_pers+0x70/0x70 [md_mod] > [] kthread+0xdb/0x100 > [] ret_from_fork+0x1f/0x40 > [] ? kthread_park+0x60/0x60 > Code: bd 70 08 00 00 f0 49 83 ad 70 08 00 00 01 74 05 e9 5a ff ff ff 41 > ff 95 80 08 00 00 e9 4e ff ff ff 48 c7 40 08 00 00 00 00 eb 8c <0f> 0b > 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 > RIP [] generic_make_request+0x1c0/0x1d0 > RSP > ---[ end trace 457dbe5e9cdd3473 ]--- CC'ing Shaohua - this is: BUG_ON(bio->bi_next); which doesn't look healthy. -- Jens Axboe