Summary: | app-emulation/xen-4.6.4-r3 + sys-kernel/gentoo-sources-4.4.26 + DRBD + Raid 5 Soft - Kernel Oops | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | MasterPrenium <masterprenium> |
Component: | Current packages | Assignee: | Gentoo Xen Devs <xen> |
Status: | RESOLVED OBSOLETE | ||
Severity: | critical | CC: | hydrapolic, marci_r |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Dmesg erros
Emerge --info |
Description
MasterPrenium
2016-12-22 13:55:52 UTC
Created attachment 457112 [details]
Emerge --info
Don't think is relevant but just in case, emerge --info
I can confirm this bug doesn't exist with a RAID 1 stack instead of the RAID 5... 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? Hi Doug, dom0. 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. Is still still an issue on a more recent kernel/xen? |