linux-4.15.0-23-generic RAID 5 kernel BUG

[Steve Kowalik]

I have a machine running linux-4.15.0-23-generic, and I can reliably trigger a kernel BUG under heavy write I/O using RAID 5.

$ cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
md0 : active raid5 sdd2[1] sda2[0] sdb2[2] sdc2[3]
      23440220160 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]
      bitmap: 0/59 pages [0KB], 65536KB chunk

unused devices: <none>

[35679.932015] ------------[ cut here ]------------
[35679.932017] kernel BUG at /build/linux-uT8zSN/linux-4.15.0/drivers/md/raid5.c:1757!
[35679.932044] invalid opcode: 0000 [#1] SMP PTI
[35679.932054] Modules linked in: xfs nls_iso8859_1 ppdev intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic kvm_intel snd_hda_intel kvm snd_hda_codec snd_hda_core snd_hwdep snd_pcm irqbypass intel_cstate intel_rapl_perf snd_timer acpi_pad mei_me mei input_leds mac_hid snd shpchp wmi_bmof intel_pch_thermal soundcore parport_pc parport sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid1 raid0 multipath linear raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper
[35679.932199] cryptd i2c_algo_bit drm_kms_helper e1000e syscopyarea sysfillrect sysimgblt fb_sys_fops ptp ahci pps_core drm libahci wmi video
[35679.932229] CPU: 2 PID: 272 Comm: md0_raid5 Not tainted 4.15.0-23-generic #25-Ubuntu
[35679.932245] Hardware name: Gigabyte Technology Co., Ltd. H370M-D3H/H370M D3H-CF, BIOS F3 03/01/2018
[35679.932266] RIP: 0010:raid_run_ops+0xbcc/0x15f0 [raid456]
[35679.932277] RSP: 0018:ffffa95d0133fb30 EFLAGS: 00010006
[35679.932289] RAX: 0000000000000000 RBX: ffff96231cf67a34 RCX: 0000000000000000
[35679.932304] RDX: ffff96231d2cd7c0 RSI: ffff962303321380 RDI: ffff96231d2cd828
[35679.932318] RBP: ffffa95d0133fbe8 R08: 0000000000001000 R09: ffffa95d0133fac0
[35679.932333] R10: 0000000000001000 R11: ffff96231d2cd848 R12: ffff96231d2cda08
[35679.932347] R13: ffff96231d2cd828 R14: ffff96231d2cd7c0 R15: ffff962319bc8000
[35679.932362] FS: 0000000000000000(0000) GS:ffff96232e480000(0000) knlGS:0000000000000000
[35679.932379] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[35679.932391] CR2: 0000564929900bb8 CR3: 0000000041a0a003 CR4: 00000000003606e0
[35679.932405] Call Trace:
[35679.932415] handle_stripe+0x669/0x21c0 [raid456]
[35679.932428] handle_active_stripes.isra.62+0x3da/0x5a0 [raid456]
[35679.932442] raid5d+0x407/0x5f0 [raid456]
[35679.932454] md_thread+0x129/0x170
[35679.932463] ? handle_active_stripes.isra.62+0x5a0/0x5a0 [raid456]
[35679.932477] ? md_thread+0x129/0x170
[35679.932487] ? wait_woken+0x80/0x80
[35679.932497] kthread+0x121/0x140
[35679.932505] ? find_pers+0x70/0x70
[35679.932515] ? kthread_create_worker_on_cpu+0x70/0x70
[35679.932527] ret_from_fork+0x35/0x40
[35679.932536] Code: 48 63 d2 48 8d 04 d0 48 89 45 c8 0f 84 9a 09 00 00 48 8b 7d 98 44 89 f1 31 d2 4c 89 e6 e8 9d a9 e7 ff 48 89 45 98 e9 06 f6 ff ff <0f> 0b 0f 0b e9 89 f9 ff ff 8b 4d 90 89 fe e9 7e fd ff ff 4c 8b
[35679.932588] RIP: raid_run_ops+0xbcc/0x15f0 [raid456] RSP: ffffa95d0133fb30
[35679.932603] ---[ end trace 22e551ef3119d0b0 ]---

$ cat /proc/version_signature
Ubuntu 4.15.0-23.25-generic 4.15.18
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-23-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer'
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=/dev/mapper/thrashed-swap
InstallationDate: Installed on 2018-07-07 (1 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0603:00f2 Novatek Microelectronics Corp. Keyboard (Labtec Ultra Flat Keyboard)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gigabyte Technology Co., Ltd. H370M-D3H
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=/dev/mapper/hostname-root ro
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-23-generic N/A
 linux-backports-modules-4.15.0-23-generic N/A
 linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic
Uname: Linux 4.15.0-23-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: False
dmi.bios.date: 03/01/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F3
dmi.board.asset.tag: Default string
dmi.board.name: H370M D3H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd03/01/2018:svnGigabyteTechnologyCo.,Ltd.:pnH370M-D3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH370MD3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: H370M-D3H
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1780628

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Steve Kowalik (stevenk)]

apport information

[Steve Kowalik (stevenk)]

apport information

[Steve Kowalik (stevenk)]

apport information

[Steve Kowalik (stevenk)]

apport information

[Steve Kowalik (stevenk)]

apport information

[Steve Kowalik (stevenk)]

apport information

[Steve Kowalik (stevenk)]

apport information

[Steve Kowalik (stevenk)]

apport information

[Steve Kowalik (stevenk)]

apport information

[Steve Kowalik (stevenk)]

apport information

[Steve Kowalik (stevenk)]

apport information

[Steve Kowalik (stevenk)]

apport information

[Steve Kowalik (stevenk)]

This does not occur using the 4.17.0-5-generic kernel from Cosmic, so something fixed it in the n commits between 4.15.0 and 4.17.0.

[Steve Kowalik (stevenk)]

Spoke too soon, it does still occur with 4.17.0, *however*, it much much harder to trigger.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc5

[Steve Kowalik (stevenk)]

[ 7609.135055] ------------[ cut here ]------------
[ 7609.135057] kernel BUG at /home/kernel/COD/linux/drivers/md/raid5.c:1762!
[ 7609.135065] invalid opcode: 0000 [#1] SMP PTI
[ 7609.135069] CPU: 2 PID: 302 Comm: md0_raid5 Not tainted 4.18.0-041800rc5-generic #201807152130
[ 7609.135071] Hardware name: Gigabyte Technology Co., Ltd. H370M-D3H/H370M D3H-CF, BIOS F3 03/01/2018
[ 7609.135078] RIP: 0010:raid_run_ops+0xbcb/0x15e0 [raid456]
[ 7609.135079] Code: 63 d2 48 8d 04 d0 48 89 45 c8 0f 84 8b 09 00 00 48 8b 7d 98 44 89 f1 31 d2 4c 89 e6 e8 8e 98 e6 ff 48 89 45 98 e9 07 f6 ff ff <0f> 0b 0f 0b e9 85 fb ff ff 8b 4d 90 89 fe e9 12 fd ff ff 4c 8b ad
[ 7609.135106] RSP: 0018:ffffa6c30135fb30 EFLAGS: 00010006
[ 7609.135108] RAX: 0000000000000000 RBX: ffff90c11b363405 RCX: 0000000000000000
[ 7609.135110] RDX: ffff90c0edc2d7c0 RSI: ffff90bf36edaec0 RDI: ffff90c0edc2d828
[ 7609.135113] RBP: ffffa6c30135fbe8 R08: 0000000000001000 R09: ffffa6c30135fac0
[ 7609.135115] R10: 0000000000001000 R11: ffff90c0edc2d848 R12: ffff90c0edc2da08
[ 7609.135117] R13: ffff90c0edc2d828 R14: ffff90c0edc2d7c0 R15: ffff90c158240800
[ 7609.135119] FS: 0000000000000000(0000) GS:ffff90c16e480000(0000) knlGS:0000000000000000
[ 7609.135122] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 7609.135124] CR2: 00005644e9cf7230 CR3: 000000003a80a002 CR4: 00000000003606e0
[ 7609.135126] Call Trace:
[ 7609.135132] handle_stripe+0x66c/0x21d0 [raid456]
[ 7609.135137] handle_active_stripes.isra.62+0x3d8/0x5c0 [raid456]
[ 7609.135141] raid5d+0x407/0x5f0 [raid456]
[ 7609.135147] md_thread+0x129/0x170
[ 7609.135150] ? handle_active_stripes.isra.62+0x5c0/0x5c0 [raid456]
[ 7609.135153] ? md_thread+0x129/0x170
[ 7609.135157] ? wait_woken+0x80/0x80
[ 7609.135160] kthread+0x121/0x140
[ 7609.135163] ? md_rdev_init+0xb0/0xb0
[ 7609.135165] ? kthread_create_worker_on_cpu+0x70/0x70
[ 7609.135169] ret_from_fork+0x35/0x40
[ 7609.135171] Modules linked in: xfs nls_iso8859_1 intel_rapl snd_hda_codec_hdmi x86_pkg_temp_thermal snd_hda_codec_realtek intel_powerclamp coretemp snd_hda_codec_generic kvm_intel kvm ppdev snd_hda_intel snd_hda_codec snd_hda_core irqbypass snd_hwdep snd_pcm intel_cstate mei_me mei wmi_bmof parport_pc snd_timer snd intel_rapl_perf soundcore parport input_leds intel_pch_thermal acpi_pad mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid1 raid0 multipath linear raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c hid_generic usbhid hid morus1280_avx2 morus1280_sse2 morus1280_glue morus640_sse2 morus640_glue aegis256_aesni aegis128l_aesni aegis128_aesni
[ 7609.135212] crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 i2c_algo_bit drm_kms_helper aesni_intel syscopyarea sysfillrect sysimgblt aes_x86_64 fb_sys_fops crypto_simd drm cryptd glue_helper ahci libahci e1000e wmi video pinctrl_cannonlake pinctrl_intel
[ 7609.135229] ---[ end trace 0de6b567897a8298 ]---
[ 7609.135233] RIP: 0010:raid_run_ops+0xbcb/0x15e0 [raid456]
[ 7609.135234] Code: 63 d2 48 8d 04 d0 48 89 45 c8 0f 84 8b 09 00 00 48 8b 7d 98 44 89 ...

[Kai-Heng Feng (kaihengfeng)]

Do you still see the issue under latest Bionic kernel or latest mainline kernel?

[Steve Kowalik (stevenk)]

Yes, with the most recent 4.18.12 kernel:

[26161.098830] ------------[ cut here ]------------
[26161.098832] kernel BUG at drivers/md/raid5.c:1762!
[26161.098838] invalid opcode: 0000 [#1] SMP PTI
[26161.098841] CPU: 3 PID: 290 Comm: md0_raid5 Not tainted 4.18.12-041812-generic #201810032137
[26161.098842] Hardware name: Gigabyte Technology Co., Ltd. H370M-D3H/H370M D3H-CF, BIOS F3 03/01/2018
[26161.098847] RIP: 0010:raid_run_ops+0xbda/0x15d0 [raid456]
[26161.098849] Code: 48 8d 04 d0 48 89 45 c8 83 f9 01 0f 85 f8 f5 ff ff 49 8b 75 00 31 c9 31 d2 4c 89 e7 e8 1f 90 e5 ff 48 89 45 98 e9 f0 f5 ff ff <0f> 0b 0f 0b e9 52 f9 ff ff 4c 8b 75 80 83 85 4c ff ff ff 01 e9 18
[26161.098867] RSP: 0018:ffffaab90141bb48 EFLAGS: 00010002
[26161.098869] RAX: 0000000000000178 RBX: ffff98177d78d4c0 RCX: 0000000000000000
[26161.098870] RDX: ffff98177d78d278 RSI: ffff981779cb3180 RDI: ffff98177d78d168
[26161.098872] RBP: ffffaab90141bc08 R08: 0000000000001000 R09: ffffaab90141bad8
[26161.098873] R10: ffff98177d78d188 R11: 0000000000000000 R12: ffff9817dddf4e60
[26161.098874] R13: ffff98177d78d168 R14: ffff98177d78d100 R15: ffff9817d931d000
[26161.098876] FS: 0000000000000000(0000) GS:ffff9817ee4c0000(0000) knlGS:0000000000000000
[26161.098878] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[26161.098879] CR2: 00007fd168034000 CR3: 000000023220a006 CR4: 00000000003606e0
[26161.098881] Call Trace:
[26161.098885] ? handle_stripe_dirtying+0x706/0x800 [raid456]
[26161.098888] handle_stripe+0xb9b/0x1f90 [raid456]
[26161.098891] ? __wake_up_common_lock+0x8e/0xc0
[26161.098895] handle_active_stripes.isra.72+0x3e6/0x5d0 [raid456]
[26161.098898] raid5d+0x359/0x550 [raid456]
[26161.098901] md_thread+0x98/0x160
[26161.098902] ? wait_woken+0x80/0x80
[26161.098905] kthread+0x120/0x140
[26161.098906] ? md_rdev_init+0xb0/0xb0
[26161.098908] ? kthread_bind+0x40/0x40
[26161.098923] ret_from_fork+0x35/0x40
[26161.098924] Modules linked in: xfs nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl snd_hda_intel snd_hda_codec x86_pkg_temp_thermal snd_hda_core intel_powerclamp coretemp snd_hwdep kvm_intel kvm snd_pcm ppdev snd_timer snd irqbypass wmi_bmof intel_cstate soundcore intel_rapl_perf mac_hid mei_me mei parport_pc parport intel_pch_thermal acpi_pad sch_fq_codel nfsd ib_iser rdma_cm iw_cm auth_rpcgss ib_cm nfs_acl ib_core lockd grace iscsi_tcp sunrpc libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid1 raid0 multipath linear raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 pcbc aesni_intel i2c_algo_bit drm_kms_helper aes_x86_64
[26161.098969] crypto_simd syscopyarea sysfillrect cryptd sysimgblt fb_sys_fops glue_helper e1000e drm ahci libahci wmi video pinctrl_cannonlake pinctrl_intel
[26161.098976] ---[ end trace 703874928e407df5 ]---
[26161.098979] RIP: 0010:raid_run_ops+0xbda/0x15d0 [raid456]
[26161.098980] Code: 48 8d 04 d0 48 89 45 c8 83 f9 01 0f 85 f8 f5 ff ff 49 8b 75 00 31 c9 31 d2 4c 89 e7 e8 1f 90 e5 ff 48 89 45 98 e9 f0 f5 ff ff <0f> 0b 0f 0b e9 52 f9 ff ff 4c 8b 75 80 83 8...

[Kai-Heng Feng (kaihengfeng)]

Sorry, but I meant v4.19-rc6.

[Steve Kowalik (stevenk)]

And v4.19-rc6:

[ 3635.247863] ------------[ cut here ]------------
[ 3635.247865] kernel BUG at drivers/md/raid5.c:1760!
[ 3635.247872] invalid opcode: 0000 [#1] SMP PTI
[ 3635.247875] CPU: 2 PID: 279 Comm: md0_raid5 Not tainted 4.19.0-041900rc6-generic #201809301631
[ 3635.247877] Hardware name: Gigabyte Technology Co., Ltd. H370M-D3H/H370M D3H-CF, BIOS F3 03/01/2018
[ 3635.247883] RIP: 0010:raid_run_ops+0xbda/0x15d0 [raid456]
[ 3635.247886] Code: 48 8d 04 d0 48 89 45 c8 83 f9 01 0f 85 f8 f5 ff ff 49 8b 75 00 31 c9 31 d2 4c 89 e7 e8 3f a0 d4 ff 48 89 45 98 e9 f0 f5 ff ff <0f> 0b 0f 0b e9 52 f9 ff ff 4c 8b 75 80 83 85 4c ff ff ff 01 e9 18
[ 3635.247888] RSP: 0018:ffffa0154122fb48 EFLAGS: 00010002
[ 3635.247891] RAX: 0000000000000198 RBX: ffff88dad8917800 RCX: 0000000000000000
[ 3635.247893] RDX: ffff88dad8917598 RSI: ffff88da08ead120 RDI: ffff88dad8917468
[ 3635.247895] RBP: ffffa0154122fc08 R08: 0000000000001000 R09: ffffa0154122fad8
[ 3635.247896] R10: ffff88dad8917488 R11: 0000000000000000 R12: ffff88db5a759898
[ 3635.247898] R13: ffff88dad8917468 R14: ffff88dad8917400 R15: ffff88db586c0000
[ 3635.247900] FS: 0000000000000000(0000) GS:ffff88db66280000(0000) knlGS:0000000000000000
[ 3635.247902] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 3635.247904] CR2: 00007ff2fe7f8ff8 CR3: 000000002220a005 CR4: 00000000003606e0
[ 3635.247906] Call Trace:
[ 3635.247911] ? handle_stripe_dirtying+0x706/0x800 [raid456]
[ 3635.247915] handle_stripe+0xb9b/0x1f90 [raid456]
[ 3635.247919] ? __wake_up_common_lock+0x8e/0xc0
[ 3635.247923] handle_active_stripes.isra.74+0x3e6/0x5d0 [raid456]
[ 3635.247927] raid5d+0x359/0x550 [raid456]
[ 3635.247931] md_thread+0x98/0x160
[ 3635.247934] ? wait_woken+0x80/0x80
[ 3635.247937] kthread+0x120/0x140
[ 3635.247939] ? md_rdev_init+0xb0/0xb0
[ 3635.247942] ? kthread_bind+0x40/0x40
[ 3635.247945] ret_from_fork+0x35/0x40
[ 3635.247947] Modules linked in: xfs nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_intel coretemp ppdev kvm_intel snd_hda_codec snd_hda_core snd_hwdep intel_cstate snd_pcm snd_timer sch_fq_codel snd wmi_bmof acpi_pad intel_rapl_perf soundcore parport_pc mac_hid intel_pch_thermal mei_me mei parport ib_iser rdma_cm iw_cm ib_cm ib_core nfsd iscsi_tcp libiscsi_tcp libiscsi auth_rpcgss scsi_transport_iscsi nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid1 raid0 multipath linear raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c i915 crct10dif_pclmul kvmgt crc32_pclmul vfio_mdev ghash_clmulni_intel mdev pcbc vfio_iommu_type1 vfio aesni_intel kvm
[ 3635.247984] irqbypass aes_x86_64 i2c_algo_bit crypto_simd drm_kms_helper cryptd glue_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm e1000e ahci libahci wmi video pinctrl_cannonlake pinctrl_intel
[ 3635.247996] ---[ end trace 70e03761eb30ac04 ]---
[ 3635.248000] RIP: 0010:raid_run_ops+0xbda/0x15d0 [raid456]
[ 3635.248002] Code: 48 8d 04 d0 48 89 45 c8 83 f9 01 0f 85 f8 f5 ff ff 49 8b 75 00 31 c9 31 d2 4c 89 e7 e8 3f a0 d4 ff 48 89 45 98 e9 f0 f5 ff ff <0f> 0b 0f 0b e9 52 f9 ff ff...

[Jaroslav Dytrych (dytrych)]

I have a same problem with the current version of Ubuntu 18.04.1 LTS (Bionic Beaver) with kernel 4.15.0-42-generic.

I have a new RAID 5 array with 4 12TB drives. As the array is being initialized, it takes 3 to 10 minutes to reach a kernel bug (under the additional system load less than 1 minute).

[Kai-Heng Feng (kaihengfeng)]

@Steve, sorry for the late reply.

These two are different bugs, let's ask the commit author about this issue.
Please mail me your mail address so I can include you in the mail loop.