[Kernel-packages] [Bug 1633128] Re: ISST-LTE:pVM nvme 0000:a0:00.0: iommu_alloc failed on NVMe card
This bug was fixed in the package linux - 4.8.0-30.32 --- linux (4.8.0-30.32) yakkety; urgency=low * CVE-2016-8655 (LP: #1646318) - packet: fix race condition in packet_set_ring -- Brad FiggThu, 01 Dec 2016 08:02:53 -0800 ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-8655 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1633128 Title: ISST-LTE:pVM nvme :a0:00.0: iommu_alloc failed on NVMe card Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: == Comment: #0 - Chanh H. Nguyen - 2016-06-02 14:22:00 == There are a huge iommu_alloc failure on the dmesg log during our ST run on the nvme card. root@br502lp2:~# uname -r 4.4.0-22-generic root@br502lp2:~# free -g totalusedfree shared buff/cache available Mem:376 1 101 0 273 373 Swap:10 0 10 root@br502lp2:~# dmesg |grep "iommu_alloc" [ 844.572656] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572658] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c351 npages 16 [ 844.572664] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c026 npages 16 [ 844.572694] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c35b npages 16 [ 844.572700] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572703] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 844.572718] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c35b npages 16 [ 844.572727] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572730] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 844.572746] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 1033.500635] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c02a6450 npages 16 [ 1033.500894] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c02a6450 npages 16 [ 1033.501290] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c03b80d1 npages 16 [ 1033.501337] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c0290391 npages 16 [ 1033.501590] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 root@br502lp2:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.4.0-22-generic root=UUID=2852021a-6954-42a9-8c69-7a58ccfbb65d ro xmon=on disable_ddw splash quiet crashkernel=384M-:128M root@br502lp2:~# lsmcode Version of System Firmware is FW840.20 (SC840_100) (t) FW840.10 (SC840_079) (p) FW840.20 (SC840_100) (b) Version of PFW is 14492016042881CF0681 == Comment: #4 - Mauricio Faria De Oliveira - 2016-10-13 10:16:40 == Hi Canonical, This patch series that resolves this problem made linux mainline in the 4.9 merge window: ("dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute") Can you please apply it on 16.04.x? Thanks! Links/commits --- [1] "dma-mapping: introduce the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a9a62c9384417545620aee1b5ad1d9357350c17a [2] "powerpc: implement the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=af8a24988e48f9ed20acf4d5230ac216d5baf723 [3] "nvme: use the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2b6b535d9158b822a45080b3d6d5b2993fd49e5a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1633128] Re: ISST-LTE:pVM nvme 0000:a0:00.0: iommu_alloc failed on NVMe card
The PATCH v2 series (backports for Xenial) has been submitted to the kernel-team mailing list [1], and ACKed by Tim. [1] https://lists.ubuntu.com/archives/kernel- team/2016-November/081197.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1633128 Title: ISST-LTE:pVM nvme :a0:00.0: iommu_alloc failed on NVMe card Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: == Comment: #0 - Chanh H. Nguyen- 2016-06-02 14:22:00 == There are a huge iommu_alloc failure on the dmesg log during our ST run on the nvme card. root@br502lp2:~# uname -r 4.4.0-22-generic root@br502lp2:~# free -g totalusedfree shared buff/cache available Mem:376 1 101 0 273 373 Swap:10 0 10 root@br502lp2:~# dmesg |grep "iommu_alloc" [ 844.572656] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572658] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c351 npages 16 [ 844.572664] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c026 npages 16 [ 844.572694] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c35b npages 16 [ 844.572700] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572703] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 844.572718] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c35b npages 16 [ 844.572727] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572730] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 844.572746] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 1033.500635] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c02a6450 npages 16 [ 1033.500894] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c02a6450 npages 16 [ 1033.501290] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c03b80d1 npages 16 [ 1033.501337] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c0290391 npages 16 [ 1033.501590] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 root@br502lp2:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.4.0-22-generic root=UUID=2852021a-6954-42a9-8c69-7a58ccfbb65d ro xmon=on disable_ddw splash quiet crashkernel=384M-:128M root@br502lp2:~# lsmcode Version of System Firmware is FW840.20 (SC840_100) (t) FW840.10 (SC840_079) (p) FW840.20 (SC840_100) (b) Version of PFW is 14492016042881CF0681 == Comment: #4 - Mauricio Faria De Oliveira - 2016-10-13 10:16:40 == Hi Canonical, This patch series that resolves this problem made linux mainline in the 4.9 merge window: ("dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute") Can you please apply it on 16.04.x? Thanks! Links/commits --- [1] "dma-mapping: introduce the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a9a62c9384417545620aee1b5ad1d9357350c17a [2] "powerpc: implement the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=af8a24988e48f9ed20acf4d5230ac216d5baf723 [3] "nvme: use the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2b6b535d9158b822a45080b3d6d5b2993fd49e5a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1633128] Re: ISST-LTE:pVM nvme 0000:a0:00.0: iommu_alloc failed on NVMe card
This bug was fixed in the package linux - 4.8.0-28.30 --- linux (4.8.0-28.30) yakkety; urgency=low [ Luis Henriques ] * Release Tracking Bug - LP: #1641083 * lxc-attach to malicious container allows access to host (LP: #1639345) - Revert "UBUNTU: SAUCE: (noup) ptrace: being capable wrt a process requires mapped uids/gids" - (upstream) mm: Add a user_ns owner to mm_struct and fix ptrace permission checks * [Feature] AVX-512 new instruction sets (avx512_4vnniw, avx512_4fmaps) (LP: #1637526) - x86/cpufeature: Add AVX512_4VNNIW and AVX512_4FMAPS features * zfs: importing zpool with vdev on zvol hangs kernel (LP: #1636517) - SAUCE: (noup) Update zfs to 0.6.5.8-0ubuntu4.1 * Move some device drivers build from kernel built-in to modules (LP: #1637303) - [Config] CONFIG_TIGON3=m for all arches - [Config] CONFIG_VIRTIO_BLK=m, CONFIG_VIRTIO_NET=m * I2C touchpad does not work on AMD platform (LP: #1612006) - pinctrl/amd: Configure GPIO register using BIOS settings * guest experiencing Transmit Timeouts on CX4 (LP: #1636330) - powerpc/64: Re-fix race condition between going idle and entering guest - powerpc/64: Fix race condition in setting lock bit in idle/wakeup code * QEMU throws failure msg while booting guest with SRIOV VF (LP: #1630554) - KVM: PPC: Always select KVM_VFIO, plus Makefile cleanup * [Feature] KBL - New device ID for Kabypoint(KbP) (LP: #1591618) - SAUCE: mfd: lpss: Fix Intel Kaby Lake PCH-H properties * hio: SSD data corruption under stress test (LP: #1638700) - SAUCE: hio: set bi_error field to signal an I/O error on a BIO - SAUCE: hio: splitting bio in the entry of .make_request_fn * cleanup primary tree for linux-hwe layering issues (LP: #1637473) - [Config] switch Vcs-Git: to yakkety repository - [Packaging] handle both linux-lts* and linux-hwe* as backports - [Config] linux-tools-common and linux-cloud-tools-common are one per series - [Config] linux-source-* is in the primary linux namespace - [Config] linux-tools -- always suggest the base package * SRU: sync zfsutils-linux and spl-linux changes to linux (LP: #1635656) - SAUCE: (noup) Update spl to 0.6.5.8-2, zfs to 0.6.5.8-0ubuntu4 (LP: #1635656) * [Feature] SKX: perf uncore PMU support (LP: #1591810) - perf/x86/intel/uncore: Add Skylake server uncore support - perf/x86/intel/uncore: Remove hard-coded implementation for Node ID mapping location - perf/x86/intel/uncore: Handle non-standard counter offset * [Feature] Purley: Memory Protection Keys (LP: #1591804) - x86/pkeys: Add fault handling for PF_PK page fault bit - mm: Implement new pkey_mprotect() system call - x86/pkeys: Make mprotect_key() mask off additional vm_flags - x86/pkeys: Allocation/free syscalls - x86: Wire up protection keys system calls - generic syscalls: Wire up memory protection keys syscalls - pkeys: Add details of system call use to Documentation/ - x86/pkeys: Default to a restrictive init PKRU - x86/pkeys: Allow configuration of init_pkru - x86/pkeys: Add self-tests * kernel invalid opcode in intel_powerclamp (LP: #1630774) - SAUCE: (no-up) thermal/powerclamp: correct cpu support check * please include mlx5_core modules in linux-image-generic package (LP: #1635223) - [Config] Include mlx5 in main package * [LTCTest] vfio_pci not loaded on Ubuntu 16.10 by default (LP: #1636733) - [Config] CONFIG_VFIO_PCI=y for ppc64el * Yakkety update to v4.8.6 stable release (LP: #1638748) - drm/vc4: Fix races when the CS reads from render targets. - drm/prime: Pass the right module owner through to dma_buf_export() - drm/i915/backlight: setup and cache pwm alternate increment value - drm/i915/backlight: setup backlight pwm alternate increment on backlight enable - drm/amdgpu: fix IB alignment for UVD - drm/amdgpu/dce10: disable hpd on local panels - drm/amdgpu/dce8: disable hpd on local panels - drm/amdgpu/dce11: disable hpd on local panels - drm/amdgpu/dce11: add missing drm_mode_config_cleanup call - drm/amdgpu: initialize the context reset_counter in amdgpu_ctx_init - drm/amdgpu: change vblank_time's calculation method to reduce computational error. - drm/radeon: narrow asic_init for virtualization - drm/radeon/si/dpm: fix phase shedding setup - drm/radeon: change vblank_time's calculation method to reduce computational error. - drm/vmwgfx: Limit the user-space command buffer size - drm/fsl-dcu: fix endian issue when using clk_register_divider - drm/amd/powerplay: fix mclk not switching back after multi-head was disabled - HID: add quirk for Akai MIDImix. - drm/i915/skl: Update plane watermarks atomically during plane updates - drm/i915: Move CRTC updating in atomic_commit into it's own hook - drm/i915/skl: Update DDB values
[Kernel-packages] [Bug 1633128] Re: ISST-LTE:pVM nvme 0000:a0:00.0: iommu_alloc failed on NVMe card
This bug was fixed in the package linux - 4.4.0-51.72 --- linux (4.4.0-51.72) xenial; urgency=low [ Luis Henriques ] * Release Tracking Bug - LP: #1644611 * 4.4.0-1037-snapdragon #41: kernel panic on boot (LP: #1644596) - Revert "dma-mapping: introduce the DMA_ATTR_NO_WARN attribute" - Revert "powerpc: implement the DMA_ATTR_NO_WARN attribute" - Revert "nvme: use the DMA_ATTR_NO_WARN attribute" linux (4.4.0-50.71) xenial; urgency=low [ Luis Henriques ] * Release Tracking Bug - LP: #1644169 * xenial 4.4.0-49.70 kernel breaks LXD userspace (LP: #1644165) - Revert "UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts by default" - Revert "UBUNTU: SAUCE: (namespace) fs: Don't remove suid for CAP_FSETID for userns root" - Revert "(namespace) Revert "UBUNTU: SAUCE: fs: Don't remove suid for CAP_FSETID in s_user_ns"" - Revert "UBUNTU: SAUCE: (namespace) fs: Allow superblock owner to change ownership of inodes" - Revert "(namespace) Revert "UBUNTU: SAUCE: fs: Allow superblock owner to change ownership of inodes with unmappable ids"" - Revert "UBUNTU: SAUCE: (namespace) security/integrity: Harden against malformed xattrs" - Revert "(namespace) Revert "UBUNTU: SAUCE: ima/evm: Allow root in s_user_ns to set xattrs"" - Revert "(namespace) dquot: For now explicitly don't support filesystems outside of init_user_ns" - Revert "(namespace) quota: Handle quota data stored in s_user_ns in quota_setxquota" - Revert "(namespace) quota: Ensure qids map to the filesystem" - Revert "(namespace) Revert "UBUNTU: SAUCE: quota: Convert ids relative to s_user_ns"" - Revert "(namespace) Revert "UBUNTU: SAUCE: quota: Require that qids passed to dqget() be valid and map into s_user_ns"" - Revert "(namespace) vfs: Don't create inodes with a uid or gid unknown to the vfs" - Revert "(namespace) vfs: Don't modify inodes with a uid or gid unknown to the vfs" - Revert "UBUNTU: SAUCE: (namespace) fuse: Translate ids in posix acl xattrs" - Revert "UBUNTU: SAUCE: (namespace) posix_acl: Export posix_acl_fix_xattr_userns() to modules" - Revert "(namespace) vfs: Verify acls are valid within superblock's s_user_ns." - Revert "(namespace) Revert "UBUNTU: SAUCE: fs: Update posix_acl support to handle user namespace mounts"" - Revert "(namespace) fs: Refuse uid/gid changes which don't map into s_user_ns" - Revert "(namespace) Revert "UBUNTU: SAUCE: fs: Refuse uid/gid changes which don't map into s_user_ns"" - Revert "(namespace) mnt: Move the FS_USERNS_MOUNT check into sget_userns" linux (4.4.0-49.70) xenial; urgency=low [ Luis Henriques ] * Release Tracking Bug - LP: #1640921 * Infiniband driver (kernel module) needed for Azure (LP: #1641139) - SAUCE: RDMA Infiniband for Windows Azure - [Config] CONFIG_HYPERV_INFINIBAND_ND=m - SAUCE: Makefile RDMA infiniband driver for Windows Azure - [Config] Add hv_network_direct.ko to generic inclusion list - SAUCE: RDMA Infiniband for Windows Azure is dependent on amd64 linux (4.4.0-48.69) xenial; urgency=low [ Luis Henriques ] * Release Tracking Bug - LP: #1640758 * lxc-attach to malicious container allows access to host (LP: #1639345) - Revert "UBUNTU: SAUCE: (noup) ptrace: being capable wrt a process requires mapped uids/gids" - (upstream) mm: Add a user_ns owner to mm_struct and fix ptrace permission checks * take 'P' command from upstream xmon (LP: #1637978) - powerpc/xmon: Add xmon command to dump process/task similar to ps(1) * zfs: importing zpool with vdev on zvol hangs kernel (LP: #1636517) - SAUCE: (noup) Update zfs to 0.6.5.6-0ubuntu15 * I2C touchpad does not work on AMD platform (LP: #1612006) - pinctrl/amd: Configure GPIO register using BIOS settings - pinctrl/amd: switch to using a bool for level * [LTCTest] vfio_pci not loaded on Ubuntu 16.10 by default (LP: #1636733) - [Config] CONFIG_VFIO_PCI=y for ppc64el * QEMU throws failure msg while booting guest with SRIOV VF (LP: #1630554) - KVM: PPC: Always select KVM_VFIO, plus Makefile cleanup * Allow fuse user namespace mounts by default in xenial (LP: #1634964) - (namespace) mnt: Move the FS_USERNS_MOUNT check into sget_userns - (namespace) Revert "UBUNTU: SAUCE: fs: Refuse uid/gid changes which don't map into s_user_ns" - (namespace) fs: Refuse uid/gid changes which don't map into s_user_ns - (namespace) Revert "UBUNTU: SAUCE: fs: Update posix_acl support to handle user namespace mounts" - (namespace) vfs: Verify acls are valid within superblock's s_user_ns. - SAUCE: (namespace) posix_acl: Export posix_acl_fix_xattr_userns() to modules - SAUCE: (namespace) fuse: Translate ids in posix acl xattrs - (namespace) vfs: Don't modify inodes with a uid
[Kernel-packages] [Bug 1633128] Re: ISST-LTE:pVM nvme 0000:a0:00.0: iommu_alloc failed on NVMe card
The backport of the commits that fix this bug introduce a regression in xenial and these patches are going to be reverted for the current SRU cycle (in xenial only). For completion, the regression is bug #1644596. ** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => In Progress ** Tags removed: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1633128 Title: ISST-LTE:pVM nvme :a0:00.0: iommu_alloc failed on NVMe card Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Committed Bug description: == Comment: #0 - Chanh H. Nguyen- 2016-06-02 14:22:00 == There are a huge iommu_alloc failure on the dmesg log during our ST run on the nvme card. root@br502lp2:~# uname -r 4.4.0-22-generic root@br502lp2:~# free -g totalusedfree shared buff/cache available Mem:376 1 101 0 273 373 Swap:10 0 10 root@br502lp2:~# dmesg |grep "iommu_alloc" [ 844.572656] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572658] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c351 npages 16 [ 844.572664] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c026 npages 16 [ 844.572694] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c35b npages 16 [ 844.572700] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572703] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 844.572718] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c35b npages 16 [ 844.572727] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572730] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 844.572746] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 1033.500635] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c02a6450 npages 16 [ 1033.500894] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c02a6450 npages 16 [ 1033.501290] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c03b80d1 npages 16 [ 1033.501337] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c0290391 npages 16 [ 1033.501590] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 root@br502lp2:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.4.0-22-generic root=UUID=2852021a-6954-42a9-8c69-7a58ccfbb65d ro xmon=on disable_ddw splash quiet crashkernel=384M-:128M root@br502lp2:~# lsmcode Version of System Firmware is FW840.20 (SC840_100) (t) FW840.10 (SC840_079) (p) FW840.20 (SC840_100) (b) Version of PFW is 14492016042881CF0681 == Comment: #4 - Mauricio Faria De Oliveira - 2016-10-13 10:16:40 == Hi Canonical, This patch series that resolves this problem made linux mainline in the 4.9 merge window: ("dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute") Can you please apply it on 16.04.x? Thanks! Links/commits --- [1] "dma-mapping: introduce the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a9a62c9384417545620aee1b5ad1d9357350c17a [2] "powerpc: implement the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=af8a24988e48f9ed20acf4d5230ac216d5baf723 [3] "nvme: use the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2b6b535d9158b822a45080b3d6d5b2993fd49e5a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1633128] Re: ISST-LTE:pVM nvme 0000:a0:00.0: iommu_alloc failed on NVMe card
--- Comment From mauri...@br.ibm.com 2016-11-21 10:14 EDT--- Verification OK on Xenial and Yakkety. ** Tags removed: verification-needed-xenial verification-needed-yakkety ** Tags added: verification-done-xenial verification-done-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1633128 Title: ISST-LTE:pVM nvme :a0:00.0: iommu_alloc failed on NVMe card Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: == Comment: #0 - Chanh H. Nguyen- 2016-06-02 14:22:00 == There are a huge iommu_alloc failure on the dmesg log during our ST run on the nvme card. root@br502lp2:~# uname -r 4.4.0-22-generic root@br502lp2:~# free -g totalusedfree shared buff/cache available Mem:376 1 101 0 273 373 Swap:10 0 10 root@br502lp2:~# dmesg |grep "iommu_alloc" [ 844.572656] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572658] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c351 npages 16 [ 844.572664] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c026 npages 16 [ 844.572694] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c35b npages 16 [ 844.572700] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572703] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 844.572718] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c35b npages 16 [ 844.572727] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572730] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 844.572746] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 1033.500635] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c02a6450 npages 16 [ 1033.500894] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c02a6450 npages 16 [ 1033.501290] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c03b80d1 npages 16 [ 1033.501337] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c0290391 npages 16 [ 1033.501590] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 root@br502lp2:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.4.0-22-generic root=UUID=2852021a-6954-42a9-8c69-7a58ccfbb65d ro xmon=on disable_ddw splash quiet crashkernel=384M-:128M root@br502lp2:~# lsmcode Version of System Firmware is FW840.20 (SC840_100) (t) FW840.10 (SC840_079) (p) FW840.20 (SC840_100) (b) Version of PFW is 14492016042881CF0681 == Comment: #4 - Mauricio Faria De Oliveira - 2016-10-13 10:16:40 == Hi Canonical, This patch series that resolves this problem made linux mainline in the 4.9 merge window: ("dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute") Can you please apply it on 16.04.x? Thanks! Links/commits --- [1] "dma-mapping: introduce the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a9a62c9384417545620aee1b5ad1d9357350c17a [2] "powerpc: implement the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=af8a24988e48f9ed20acf4d5230ac216d5baf723 [3] "nvme: use the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2b6b535d9158b822a45080b3d6d5b2993fd49e5a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1633128] Re: ISST-LTE:pVM nvme 0000:a0:00.0: iommu_alloc failed on NVMe card
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1633128 Title: ISST-LTE:pVM nvme :a0:00.0: iommu_alloc failed on NVMe card Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: == Comment: #0 - Chanh H. Nguyen- 2016-06-02 14:22:00 == There are a huge iommu_alloc failure on the dmesg log during our ST run on the nvme card. root@br502lp2:~# uname -r 4.4.0-22-generic root@br502lp2:~# free -g totalusedfree shared buff/cache available Mem:376 1 101 0 273 373 Swap:10 0 10 root@br502lp2:~# dmesg |grep "iommu_alloc" [ 844.572656] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572658] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c351 npages 16 [ 844.572664] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c026 npages 16 [ 844.572694] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c35b npages 16 [ 844.572700] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572703] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 844.572718] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c35b npages 16 [ 844.572727] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572730] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 844.572746] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 1033.500635] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c02a6450 npages 16 [ 1033.500894] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c02a6450 npages 16 [ 1033.501290] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c03b80d1 npages 16 [ 1033.501337] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c0290391 npages 16 [ 1033.501590] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 root@br502lp2:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.4.0-22-generic root=UUID=2852021a-6954-42a9-8c69-7a58ccfbb65d ro xmon=on disable_ddw splash quiet crashkernel=384M-:128M root@br502lp2:~# lsmcode Version of System Firmware is FW840.20 (SC840_100) (t) FW840.10 (SC840_079) (p) FW840.20 (SC840_100) (b) Version of PFW is 14492016042881CF0681 == Comment: #4 - Mauricio Faria De Oliveira - 2016-10-13 10:16:40 == Hi Canonical, This patch series that resolves this problem made linux mainline in the 4.9 merge window: ("dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute") Can you please apply it on 16.04.x? Thanks! Links/commits --- [1] "dma-mapping: introduce the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a9a62c9384417545620aee1b5ad1d9357350c17a [2] "powerpc: implement the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=af8a24988e48f9ed20acf4d5230ac216d5baf723 [3] "nvme: use the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2b6b535d9158b822a45080b3d6d5b2993fd49e5a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1633128] Re: ISST-LTE:pVM nvme 0000:a0:00.0: iommu_alloc failed on NVMe card
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1633128 Title: ISST-LTE:pVM nvme :a0:00.0: iommu_alloc failed on NVMe card Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: == Comment: #0 - Chanh H. Nguyen- 2016-06-02 14:22:00 == There are a huge iommu_alloc failure on the dmesg log during our ST run on the nvme card. root@br502lp2:~# uname -r 4.4.0-22-generic root@br502lp2:~# free -g totalusedfree shared buff/cache available Mem:376 1 101 0 273 373 Swap:10 0 10 root@br502lp2:~# dmesg |grep "iommu_alloc" [ 844.572656] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572658] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c351 npages 16 [ 844.572664] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c026 npages 16 [ 844.572694] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c35b npages 16 [ 844.572700] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572703] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 844.572718] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c35b npages 16 [ 844.572727] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572730] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 844.572746] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 1033.500635] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c02a6450 npages 16 [ 1033.500894] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c02a6450 npages 16 [ 1033.501290] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c03b80d1 npages 16 [ 1033.501337] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c0290391 npages 16 [ 1033.501590] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 root@br502lp2:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.4.0-22-generic root=UUID=2852021a-6954-42a9-8c69-7a58ccfbb65d ro xmon=on disable_ddw splash quiet crashkernel=384M-:128M root@br502lp2:~# lsmcode Version of System Firmware is FW840.20 (SC840_100) (t) FW840.10 (SC840_079) (p) FW840.20 (SC840_100) (b) Version of PFW is 14492016042881CF0681 == Comment: #4 - Mauricio Faria De Oliveira - 2016-10-13 10:16:40 == Hi Canonical, This patch series that resolves this problem made linux mainline in the 4.9 merge window: ("dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute") Can you please apply it on 16.04.x? Thanks! Links/commits --- [1] "dma-mapping: introduce the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a9a62c9384417545620aee1b5ad1d9357350c17a [2] "powerpc: implement the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=af8a24988e48f9ed20acf4d5230ac216d5baf723 [3] "nvme: use the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2b6b535d9158b822a45080b3d6d5b2993fd49e5a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1633128] Re: ISST-LTE:pVM nvme 0000:a0:00.0: iommu_alloc failed on NVMe card
** Changed in: linux (Ubuntu Yakkety) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1633128 Title: ISST-LTE:pVM nvme :a0:00.0: iommu_alloc failed on NVMe card Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: == Comment: #0 - Chanh H. Nguyen- 2016-06-02 14:22:00 == There are a huge iommu_alloc failure on the dmesg log during our ST run on the nvme card. root@br502lp2:~# uname -r 4.4.0-22-generic root@br502lp2:~# free -g totalusedfree shared buff/cache available Mem:376 1 101 0 273 373 Swap:10 0 10 root@br502lp2:~# dmesg |grep "iommu_alloc" [ 844.572656] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572658] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c351 npages 16 [ 844.572664] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c026 npages 16 [ 844.572694] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c35b npages 16 [ 844.572700] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572703] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 844.572718] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c35b npages 16 [ 844.572727] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572730] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 844.572746] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 1033.500635] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c02a6450 npages 16 [ 1033.500894] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c02a6450 npages 16 [ 1033.501290] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c03b80d1 npages 16 [ 1033.501337] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c0290391 npages 16 [ 1033.501590] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 root@br502lp2:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.4.0-22-generic root=UUID=2852021a-6954-42a9-8c69-7a58ccfbb65d ro xmon=on disable_ddw splash quiet crashkernel=384M-:128M root@br502lp2:~# lsmcode Version of System Firmware is FW840.20 (SC840_100) (t) FW840.10 (SC840_079) (p) FW840.20 (SC840_100) (b) Version of PFW is 14492016042881CF0681 == Comment: #4 - Mauricio Faria De Oliveira - 2016-10-13 10:16:40 == Hi Canonical, This patch series that resolves this problem made linux mainline in the 4.9 merge window: ("dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute") Can you please apply it on 16.04.x? Thanks! Links/commits --- [1] "dma-mapping: introduce the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a9a62c9384417545620aee1b5ad1d9357350c17a [2] "powerpc: implement the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=af8a24988e48f9ed20acf4d5230ac216d5baf723 [3] "nvme: use the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2b6b535d9158b822a45080b3d6d5b2993fd49e5a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1633128] Re: ISST-LTE:pVM nvme 0000:a0:00.0: iommu_alloc failed on NVMe card
https://lists.ubuntu.com/archives/kernel-team/2016-October/080349.html https://lists.ubuntu.com/archives/kernel-team/2016-October/080353.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1633128 Title: ISST-LTE:pVM nvme :a0:00.0: iommu_alloc failed on NVMe card Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: == Comment: #0 - Chanh H. Nguyen- 2016-06-02 14:22:00 == There are a huge iommu_alloc failure on the dmesg log during our ST run on the nvme card. root@br502lp2:~# uname -r 4.4.0-22-generic root@br502lp2:~# free -g totalusedfree shared buff/cache available Mem:376 1 101 0 273 373 Swap:10 0 10 root@br502lp2:~# dmesg |grep "iommu_alloc" [ 844.572656] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572658] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c351 npages 16 [ 844.572664] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c026 npages 16 [ 844.572694] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c35b npages 16 [ 844.572700] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572703] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 844.572718] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c35b npages 16 [ 844.572727] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572730] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 844.572746] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 1033.500635] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c02a6450 npages 16 [ 1033.500894] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c02a6450 npages 16 [ 1033.501290] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c03b80d1 npages 16 [ 1033.501337] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c0290391 npages 16 [ 1033.501590] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 root@br502lp2:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.4.0-22-generic root=UUID=2852021a-6954-42a9-8c69-7a58ccfbb65d ro xmon=on disable_ddw splash quiet crashkernel=384M-:128M root@br502lp2:~# lsmcode Version of System Firmware is FW840.20 (SC840_100) (t) FW840.10 (SC840_079) (p) FW840.20 (SC840_100) (b) Version of PFW is 14492016042881CF0681 == Comment: #4 - Mauricio Faria De Oliveira - 2016-10-13 10:16:40 == Hi Canonical, This patch series that resolves this problem made linux mainline in the 4.9 merge window: ("dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute") Can you please apply it on 16.04.x? Thanks! Links/commits --- [1] "dma-mapping: introduce the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a9a62c9384417545620aee1b5ad1d9357350c17a [2] "powerpc: implement the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=af8a24988e48f9ed20acf4d5230ac216d5baf723 [3] "nvme: use the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2b6b535d9158b822a45080b3d6d5b2993fd49e5a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1633128] Re: ISST-LTE:pVM nvme 0000:a0:00.0: iommu_alloc failed on NVMe card
** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu Yakkety) Status: New => In Progress ** Changed in: linux (Ubuntu Yakkety) Assignee: Taco Screen team (taco-screen-team) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1633128 Title: ISST-LTE:pVM nvme :a0:00.0: iommu_alloc failed on NVMe card Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: == Comment: #0 - Chanh H. Nguyen- 2016-06-02 14:22:00 == There are a huge iommu_alloc failure on the dmesg log during our ST run on the nvme card. root@br502lp2:~# uname -r 4.4.0-22-generic root@br502lp2:~# free -g totalusedfree shared buff/cache available Mem:376 1 101 0 273 373 Swap:10 0 10 root@br502lp2:~# dmesg |grep "iommu_alloc" [ 844.572656] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572658] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c351 npages 16 [ 844.572664] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c026 npages 16 [ 844.572694] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c35b npages 16 [ 844.572700] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572703] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 844.572718] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c000c35b npages 16 [ 844.572727] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c001c1a7 npages 16 [ 844.572730] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 844.572746] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c023c7a9 npages 16 [ 1033.500635] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c02a6450 npages 16 [ 1033.500894] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c02a6450 npages 16 [ 1033.501290] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c03b80d1 npages 16 [ 1033.501337] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 vaddr c0290391 npages 16 [ 1033.501590] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00 root@br502lp2:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.4.0-22-generic root=UUID=2852021a-6954-42a9-8c69-7a58ccfbb65d ro xmon=on disable_ddw splash quiet crashkernel=384M-:128M root@br502lp2:~# lsmcode Version of System Firmware is FW840.20 (SC840_100) (t) FW840.10 (SC840_079) (p) FW840.20 (SC840_100) (b) Version of PFW is 14492016042881CF0681 == Comment: #4 - Mauricio Faria De Oliveira - 2016-10-13 10:16:40 == Hi Canonical, This patch series that resolves this problem made linux mainline in the 4.9 merge window: ("dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute") Can you please apply it on 16.04.x? Thanks! Links/commits --- [1] "dma-mapping: introduce the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a9a62c9384417545620aee1b5ad1d9357350c17a [2] "powerpc: implement the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=af8a24988e48f9ed20acf4d5230ac216d5baf723 [3] "nvme: use the DMA_ATTR_NO_WARN attribute" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2b6b535d9158b822a45080b3d6d5b2993fd49e5a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp