Soft lockup messages when syncing RAID10(md) array

Issue

• Creating a RAID6 with 24 disks which results into a kernel panic and call trace in the messages file. The issue also reproducible when try to re-sync the disk after removing a disk.

#mdadm --create /dev/md_d1 --metadata=1.0 --level=6 --raid-devices=24 /dev/sdd1 /dev/sdh1 /dev/sdl1 /dev/sdp1 /dev/sdt1 /dev/sdx1 /dev/sdab1 /dev/sdaf1 /dev/sdaj1 /dev/sdan1 /dev/sdar1 /dev/sdav1 /dev/sdc1 /dev/sdg1 /dev/sdk1 /dev/sdo1 /dev/sds1 /dev/sdw1 /dev/sdaa1 /dev/sdae1 /dev/sdai1 /dev/sdam1 /dev/sdaq1 /dev/sdau1

Jan 27 17:05:14 example kernel: md: syncing RAID array md_d1
Jan 27 17:05:14 example kernel: md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc.
Jan 27 17:05:14 example kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction.
Jan 27 17:05:14 example kernel: md: using 128k window, over a total of 976759808 blocks.
Jan 27 17:05:14 example kernel:  md_d1: unknown partition table
Jan 27 17:05:26 example kernel: BUG: soft lockup - CPU#1 stuck for 10s! [md_d1_raid5:6923]
Jan 27 17:05:26 example kernel: CPU 1:
Jan 27 17:05:26 example kernel: Modules linked in: raid456 xor ipv6 xfrm_nalgo crypto_api mptctl autofs4 ipmi_devintf ipmi_si ipmi_msghandler hidp l2cap bluetooth sunrpc dm_mirror dm_multipath dm_mod video sbs backlight i2c_ec button battery asus_acpi acpi_memhotplug ac parport_pc lp parport joydev sg shpchp i2c_nforce2 mlx4_core forcedeth i2c_core pcspkr usb_storage mptsas mptscsih mptbase scsi_transport_sas sd_mod scsi_mod raid1 ext3 jbd uhci_hcd ohci_hcd ehci_hcd
Jan 27 17:05:26 example kernel: Pid: 6923, comm: md_d1_raid5 Not tainted 2.6.18-92.1.22.el5 #1
Jan 27 17:05:56 example kernel: RIP: 0010:[<ffffffff8000b5c7>]  [<ffffffff8000b5c7>] memcmp+0x1a/0x22
..
Jan 27 17:05:56 example kernel: Call Trace:
Jan 27 17:05:56 example kernel:  [<ffffffff883f7d10>] :raid456:handle_stripe+0xe5b/0x24d4
Jan 27 17:05:56 example kernel:  [<ffffffff800892a6>] __wake_up_common+0x3e/0x68
Jan 27 17:05:56 example kernel:  [<ffffffff8002e284>] __wake_up+0x38/0x4f
Jan 27 17:05:56 example kernel:  [<ffffffff8009dc54>] keventd_create_kthread+0x0/0xc4
Jan 27 17:05:56 example kernel:  [<ffffffff8009dc54>] keventd_create_kthread+0x0/0xc4
Jan 27 17:05:56 example kernel:  [<ffffffff883f94d6>] :raid456:raid5d+0x14d/0x17b
Jan 27 17:05:56 example kernel:  [<ffffffff8003a940>] prepare_to_wait+0x34/0x5c
Jan 27 17:05:56 example kernel:  [<ffffffff802030c7>] md_thread+0xf8/0x10e
Jan 27 17:05:56 example kernel:  [<ffffffff8009de6c>] autoremove_wake_function+0x0/0x2e
Jan 27 17:05:56 example kernel:  [<ffffffff80202fcf>] md_thread+0x0/0x10e
Jan 27 17:05:56 example kernel:  [<ffffffff80032569>] kthread+0xfe/0x132
Jan 27 17:05:56 example kernel:  [<ffffffff8005dfb1>] child_rip+0xa/0x11
Jan 27 17:05:56 example kernel:  [<ffffffff8009dc54>] keventd_create_kthread+0x0/0xc4
Jan 27 17:05:56 example kernel:  [<ffffffff8003246b>] kthread+0x0/0x132
Jan 27 17:05:56 example kernel:  [<ffffffff8005dfa7>] child_rip+0x0/0x11