[Bug 1551828] Re: kpartx causes kernel oops when NVMe devices is not in blacklist
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 in blacklist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1551828/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1551828] Re: kpartx causes kernel oops when NVMe devices is not in blacklist
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 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 in blacklist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1551828/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1551828] Re: kpartx causes kernel oops when NVMe devices is not in blacklist
** 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. + http://paste.openstack.org/show/488638/ + + 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 (http://git.opensvc.com/gitweb.cgi?p=multipath-tools/.git;a=commitdiff;h=5c412e47e589b5325ed7de6cba86d906a671d9df) I made patches for trusty and xenial versions of multipath-tools. Patches which fix issue is in attach. Could you apply this patches please, at least for trusty version? -- 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 in blacklist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1551828/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1551828] Re: kpartx cause kernel oops when NVMe devices is not in blacklist
** 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 NVMe devices is not in blacklist ** 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. This bug is already described and fixed in upstream (http://git.opensvc.com/gitweb.cgi?p=multipath-tools/.git;a=commitdiff;h=5c412e47e589b5325ed7de6cba86d906a671d9df) - I made patches for trusty and xenail versions of multipath-tools. + I made patches for trusty and xenial versions of multipath-tools. Patches which fix issue is in attach. Could you apply this patches please, at least for trusty version? -- 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 in blacklist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1551828/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1551828] [NEW] kpartx causes kernel oops when NVMe devices is not in blacklist
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 (http://git.opensvc.com/gitweb.cgi?p=multipath-tools/.git;a=commitdiff;h=5c412e47e589b5325ed7de6cba86d906a671d9df) I made patches for trusty and xenial versions of multipath-tools. Patches which fix issue is in attach. Could you apply this patches please, at least for trusty version? ** Affects: multipath-tools (Ubuntu) Importance: Undecided Status: New ** Patch added: "trusty nvme blacklist" https://bugs.launchpad.net/bugs/1551828/+attachment/4585636/+files/trusty-blacklist-nvme-devices.patch -- 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 in blacklist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1551828/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
