[Bug 1551828] Re: kpartx causes kernel oops when NVMe devices is not in blacklist

2016-03-19 Thread Ivan Suzdal
Hi all! Any ETA with series file? Can I help you somehow? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1551828 Title: kpartx causes kernel oops when NVMe devices is not

[Bug 1551828] Re: kpartx causes kernel oops when NVMe devices is not in blacklist

2016-03-09 Thread Ivan Suzdal
Looks like you forgot to add nvme patch to debian/patches/series # ls debian/patches/ | grep nvme dm-multipath-backlist-nvme-5c412e47.patch # grep nvme debian/patches/series # ** Tags removed: verification-needed ** Tags added: verification-failed -- You received this bug notification because

[Bug 1551828] Re: kpartx causes kernel oops when NVMe devices is not in blacklist

2016-03-01 Thread Ivan Suzdal
** Description changed: - When on bare metal uses NVMe devices - kpartx cause kernel oops. Also any tools which works with disks (e.g. fdisk, lsblk) hangs in D state (uninterruptible sleep) while trying to to read /dev/dm-X. + When on bare metal uses NVMe devices - kpartx cause kernel oops. +

[Bug 1551828] Re: kpartx cause kernel oops when NVMe devices is not in blacklist

2016-03-01 Thread Ivan Suzdal
** Patch added: "xenial nvme blacklist" https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1551828/+attachment/4585637/+files/xenial-blacklist-nvme-devices.patch ** Summary changed: - kpartx cause kernel oops when NVMe devices is not in blacklist + kpartx causes kernel oops when

[Bug 1551828] [NEW] kpartx causes kernel oops when NVMe devices is not in blacklist

2016-03-01 Thread Ivan Suzdal
Public bug reported: When on bare metal uses NVMe devices - kpartx cause kernel oops. Also any tools which works with disks (e.g. fdisk, lsblk) hangs in D state (uninterruptible sleep) while trying to to read /dev/dm-X. This bug is already described and fixed in upstream