Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 603464 - app-emulation/xen-4.6.4-r3 + sys-kernel/gentoo-sources-4.4.26 + DRBD + Raid 5 Soft - Kernel Oops
Summary: app-emulation/xen-4.6.4-r3 + sys-kernel/gentoo-sources-4.4.26 + DRBD + Raid 5...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal critical (vote)
Assignee: Gentoo Xen Devs
Depends on:
Reported: 2016-12-22 13:55 UTC by MasterPrenium
Modified: 2018-01-15 04:49 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---

Dmesg erros (DmesgError.txt,288.92 KB, text/plain)
2016-12-22 13:55 UTC, MasterPrenium
Emerge --info (EmergeInfo.txt,5.54 KB, text/plain)
2016-12-22 13:58 UTC, MasterPrenium

Note You need to log in before you can comment on or make changes to this bug.
Description MasterPrenium 2016-12-22 13:55:52 UTC
Created attachment 457110 [details]
Dmesg erros

Hello Guys,

I've having some trouble on a new system I'm setting up.

Dmesg errors attached.

Kernels version impacted (at least):
- gentoo-sources-4.4.26
- gentoo-sources-4.8.15
- gentoo-sources-4.9.0

With or without experimental patch, it's the same issue.

Xen Version : 
(same issue with xen 4.8)

Kernel config (gentoo-sources 4.8.15) :

This is happening when I'm making "huge" I/O (20MB/s with and rsync for example) on a raid 5 RAID stack.
I've to reset system to make it work again.

Reproducible : ALWAYS (making the i/o, it crash in 2-5mins)

Here is configuration :
- 3x Hard Drives running on RAID 5 Software raid created by mdadm
- On top of it, I'm running DRBD for replication over another node (Active/passive cluster)
- On top of it, a BTRFS FileSystem with a few subvolumes
- On top of it, XEN VMs running.

All buit with : gcc (Gentoo 4.9.3 p1.5, pie-0.6.4) 4.9.3

Kernel bug ? Any idea on how to fix it ?
Comment 1 MasterPrenium 2016-12-22 13:58:19 UTC
Created attachment 457112 [details]
Emerge --info

Don't think is relevant but just in case, emerge --info
Comment 2 MasterPrenium 2016-12-26 11:56:18 UTC
I can confirm this bug doesn't exist with a RAID 1 stack instead of the RAID 5...
Comment 3 Doug Goldstein gentoo-dev 2016-12-26 20:20:01 UTC
So what's not clear to me is this a domU or dom0? Is the oops in the kernel or the hypervisor? Does it appear to affect any other domUs if its a domU?
Comment 4 MasterPrenium 2016-12-27 06:58:36 UTC
Hi Doug,

The RAID stack of course is done on dom0.
As the kernel crashes, everything is affected.

Oops visible in the kernel.

In order to reproduce, I can make the I/O even on dom0 or domU, same issue.

Note : issue is happening even if no domU are running.
Comment 5 Tomáš Mózes 2018-01-15 04:49:39 UTC
Is still still an issue on a more recent kernel/xen?