From: NeilBrown <neilb@suse.de>
To: lkp@lists.01.org
Subject: Re: [raid5] kernel BUG at drivers/md/raid5.c:4374!
Date: Thu, 17 Apr 2014 14:13:55 +1000 [thread overview]
Message-ID: <20140417141355.355e2f3e@notabene.brown> (raw)
In-Reply-To: <20140417035958.GE8702@localhost>
[-- Attachment #1: Type: text/plain, Size: 3731 bytes --]
On Thu, 17 Apr 2014 11:59:59 +0800 Fengguang Wu <fengguang.wu@intel.com>
wrote:
> Shaohua,
>
> We noticed the below BUG on
>
> commit e240c1839d11152b0355442f8ac6d2d2d921be36 ("raid5: get_active_stripe avoids device_lock")
>
> test case: lkp-ws02/micro/dd-write/11HDD-RAID5-cfq-ext4-10dd
Thanks. We know about this. I really should push that patch out....
Sorry
NeilBrown
>
> 27c0f68f0745218 e240c1839d11152b0355442f8
> --------------- -------------------------
> 0 +Inf% 1 ~ 0% TOTAL dmesg.kernel_BUG_at_drivers/md/raid5.c
> 0 +Inf% 1 ~ 0% TOTAL dmesg.invalid_opcode
> 0 +Inf% 1 ~ 0% TOTAL dmesg.RIP:handle_active_stripes
> 0 +Inf% 1 ~ 0% TOTAL dmesg.Kernel_panic-not_syncing:Fatal_exception
>
> Legend:
> ~XX% - stddev percent
> [+-]XX% - change percent
>
> [ 264.260444] kernel BUG at drivers/md/raid5.c:4374!
> [ 264.267590] invalid opcode: 0000 [#1] SMP
> [ 264.272076] Modules linked in: btrfs microcode ipmi_si ipmi_msghandler acpi_cpufreq processor
> [ 264.281514] CPU: 0 PID: 4005 Comm: md0_raid5 Not tainted 3.15.0-rc1-00611-g2e76799 #1
> [ 264.289823] Hardware name: Supermicro X8DTN/X8DTN, BIOS 4.6.3 01/06/2010
> [ 264.296789] task: ffff8804151e41a0 ti: ffff88041672c000 task.ti: ffff88041672c000
> [ 264.304750] RIP: 0010:[<ffffffff81804ef1>] [<ffffffff81804ef1>] handle_active_stripes.isra.24+0x254/0x360
> [ 264.314951] RSP: 0018:ffff88041672dd10 EFLAGS: 00010002
> [ 264.320527] RAX: ffff88021dc46000 RBX: ffff880220a4e000 RCX: ffff880220a4e080
> [ 264.327926] RDX: 0000000000000001 RSI: ffff88021e0d7010 RDI: ffff880220a4e000
> [ 264.335325] RBP: ffff88041672dda8 R08: 0000000000000000 R09: 0000000000000000
> [ 264.342724] R10: 0000000000000000 R11: 000000000000ef58 R12: 0000000000000000
> [ 264.350131] R13: ffff880220a4e080 R14: 0000000000000000 R15: ffff880220a4e268
> [ 264.357530] FS: 0000000000000000(0000) GS:ffff880237c00000(0000) knlGS:0000000000000000
> [ 264.366099] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> [ 264.372111] CR2: 0000000001e21d64 CR3: 000000000200f000 CR4: 00000000000007f0
> [ 264.379509] Stack:
> [ 264.381780] ffff8804173d7de0 ffff880220a4e000 ffff88041672dd38 ffffffffffffffd8
> [ 264.389907] ffffffff1e1bd000 ffff880220a4e090 ffffffff817fdba2 ffff880220a4e000
> [ 264.398043] 0000000000000021 ffff880220a4e268 0000000000000000 ffff88041672dd78
> [ 264.406172] Call Trace:
> [ 264.408893] [<ffffffff817fdba2>] ? do_release_stripe+0xdf/0x158
> [ 264.415168] [<ffffffff817fdc30>] ? __release_stripe+0x15/0x17
> [ 264.421266] [<ffffffff818054f2>] raid5d+0x3e2/0x4f2
> [ 264.426497] [<ffffffff819bcacf>] ? schedule_timeout+0x2f/0x19f
> [ 264.432681] [<ffffffff81826151>] md_thread+0x123/0x139
> [ 264.438171] [<ffffffff811148b6>] ? __wake_up_sync+0x12/0x12
> [ 264.444096] [<ffffffff8182602e>] ? md_register_thread+0xd5/0xd5
> [ 264.450368] [<ffffffff810fa267>] kthread+0xdb/0xe3
> [ 264.455511] [<ffffffff810fa18c>] ? kthread_create_on_node+0x16f/0x16f
> [ 264.462310] [<ffffffff819c7d7c>] ret_from_fork+0x7c/0xb0
> [ 264.467973] [<ffffffff810fa18c>] ? kthread_create_on_node+0x16f/0x16f
> [ 264.474764] Code: 60 00 00 00 00 48 8b 70 10 48 8b 48 18 48 8d 50 10 48 89 4e 08 48 89 31 48 89 50 10 48 89 50 18 f0 ff 40 50 8b 50 50
> ff ca 74 02 <0f> 0b 4a 89 44 d5 98 49 ff c2 49 83 fa 08 0f 85 d7 fd ff ff 41
> [ 264.498252] RIP [<ffffffff81804ef1>] handle_active_stripes.isra.24+0x254/0x360
> [ 264.506112] RSP <ffff88041672dd10>
> [ 264.509869] ---[ end trace 58f3875ff7b4e923 ]---
>
> Thanks,
> Fengguang
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: NeilBrown <neilb@suse.de>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Shaohua Li <shli@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: Re: [raid5] kernel BUG at drivers/md/raid5.c:4374!
Date: Thu, 17 Apr 2014 14:13:55 +1000 [thread overview]
Message-ID: <20140417141355.355e2f3e@notabene.brown> (raw)
In-Reply-To: <20140417035958.GE8702@localhost>
[-- Attachment #1: Type: text/plain, Size: 3731 bytes --]
On Thu, 17 Apr 2014 11:59:59 +0800 Fengguang Wu <fengguang.wu@intel.com>
wrote:
> Shaohua,
>
> We noticed the below BUG on
>
> commit e240c1839d11152b0355442f8ac6d2d2d921be36 ("raid5: get_active_stripe avoids device_lock")
>
> test case: lkp-ws02/micro/dd-write/11HDD-RAID5-cfq-ext4-10dd
Thanks. We know about this. I really should push that patch out....
Sorry
NeilBrown
>
> 27c0f68f0745218 e240c1839d11152b0355442f8
> --------------- -------------------------
> 0 +Inf% 1 ~ 0% TOTAL dmesg.kernel_BUG_at_drivers/md/raid5.c
> 0 +Inf% 1 ~ 0% TOTAL dmesg.invalid_opcode
> 0 +Inf% 1 ~ 0% TOTAL dmesg.RIP:handle_active_stripes
> 0 +Inf% 1 ~ 0% TOTAL dmesg.Kernel_panic-not_syncing:Fatal_exception
>
> Legend:
> ~XX% - stddev percent
> [+-]XX% - change percent
>
> [ 264.260444] kernel BUG at drivers/md/raid5.c:4374!
> [ 264.267590] invalid opcode: 0000 [#1] SMP
> [ 264.272076] Modules linked in: btrfs microcode ipmi_si ipmi_msghandler acpi_cpufreq processor
> [ 264.281514] CPU: 0 PID: 4005 Comm: md0_raid5 Not tainted 3.15.0-rc1-00611-g2e76799 #1
> [ 264.289823] Hardware name: Supermicro X8DTN/X8DTN, BIOS 4.6.3 01/06/2010
> [ 264.296789] task: ffff8804151e41a0 ti: ffff88041672c000 task.ti: ffff88041672c000
> [ 264.304750] RIP: 0010:[<ffffffff81804ef1>] [<ffffffff81804ef1>] handle_active_stripes.isra.24+0x254/0x360
> [ 264.314951] RSP: 0018:ffff88041672dd10 EFLAGS: 00010002
> [ 264.320527] RAX: ffff88021dc46000 RBX: ffff880220a4e000 RCX: ffff880220a4e080
> [ 264.327926] RDX: 0000000000000001 RSI: ffff88021e0d7010 RDI: ffff880220a4e000
> [ 264.335325] RBP: ffff88041672dda8 R08: 0000000000000000 R09: 0000000000000000
> [ 264.342724] R10: 0000000000000000 R11: 000000000000ef58 R12: 0000000000000000
> [ 264.350131] R13: ffff880220a4e080 R14: 0000000000000000 R15: ffff880220a4e268
> [ 264.357530] FS: 0000000000000000(0000) GS:ffff880237c00000(0000) knlGS:0000000000000000
> [ 264.366099] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> [ 264.372111] CR2: 0000000001e21d64 CR3: 000000000200f000 CR4: 00000000000007f0
> [ 264.379509] Stack:
> [ 264.381780] ffff8804173d7de0 ffff880220a4e000 ffff88041672dd38 ffffffffffffffd8
> [ 264.389907] ffffffff1e1bd000 ffff880220a4e090 ffffffff817fdba2 ffff880220a4e000
> [ 264.398043] 0000000000000021 ffff880220a4e268 0000000000000000 ffff88041672dd78
> [ 264.406172] Call Trace:
> [ 264.408893] [<ffffffff817fdba2>] ? do_release_stripe+0xdf/0x158
> [ 264.415168] [<ffffffff817fdc30>] ? __release_stripe+0x15/0x17
> [ 264.421266] [<ffffffff818054f2>] raid5d+0x3e2/0x4f2
> [ 264.426497] [<ffffffff819bcacf>] ? schedule_timeout+0x2f/0x19f
> [ 264.432681] [<ffffffff81826151>] md_thread+0x123/0x139
> [ 264.438171] [<ffffffff811148b6>] ? __wake_up_sync+0x12/0x12
> [ 264.444096] [<ffffffff8182602e>] ? md_register_thread+0xd5/0xd5
> [ 264.450368] [<ffffffff810fa267>] kthread+0xdb/0xe3
> [ 264.455511] [<ffffffff810fa18c>] ? kthread_create_on_node+0x16f/0x16f
> [ 264.462310] [<ffffffff819c7d7c>] ret_from_fork+0x7c/0xb0
> [ 264.467973] [<ffffffff810fa18c>] ? kthread_create_on_node+0x16f/0x16f
> [ 264.474764] Code: 60 00 00 00 00 48 8b 70 10 48 8b 48 18 48 8d 50 10 48 89 4e 08 48 89 31 48 89 50 10 48 89 50 18 f0 ff 40 50 8b 50 50
> ff ca 74 02 <0f> 0b 4a 89 44 d5 98 49 ff c2 49 83 fa 08 0f 85 d7 fd ff ff 41
> [ 264.498252] RIP [<ffffffff81804ef1>] handle_active_stripes.isra.24+0x254/0x360
> [ 264.506112] RSP <ffff88041672dd10>
> [ 264.509869] ---[ end trace 58f3875ff7b4e923 ]---
>
> Thanks,
> Fengguang
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-04-17 4:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 3:59 [raid5] kernel BUG at drivers/md/raid5.c:4374! Fengguang Wu
2014-04-17 3:59 ` Fengguang Wu
2014-04-17 4:13 ` NeilBrown [this message]
2014-04-17 4:13 ` NeilBrown
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=20140417141355.355e2f3e@notabene.brown \
--to=neilb@suse.de \
--cc=lkp@lists.01.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.