FS#58288 - [linux] Kernel 4.16.2-2 (Intel Wireless 8260) iwlwifi swiotlb coherent allocation failed

Attached to Project: Arch Linux
Opened by Andrea Girotto (andreagi) - Friday, 20 April 2018, 08:08 GMT
Last edited by Eli Schwartz (eschwartz) - Wednesday, 02 May 2018, 19:46 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
The iwlwifi drivers goes on OOPS with the kernel 4.16.2-2 (it is working flawlessly with previous versions and specifically 4.15.15-1 and 4.14.34-1-lts).

On the dmesg output attached the relevant part starts here:

[ 3.144427] Intel(R) Wireless WiFi driver for Linux
[ 3.144428] Copyright(c) 2003- 2015 Intel Corporation
[ 3.144511] iwlwifi 0000:02:00.0: enabling device (0000 -> 0002)
[ 3.145067] iwlwifi 0000:02:00.0: hwdev DMA mask = 0x0000000fffffffff, dev_addr = 0x000000006c000000
[ 3.145069] iwlwifi 0000:02:00.0: swiotlb: coherent allocation failed, size=4096
[ 3.145071] CPU: 5 PID: 288 Comm: systemd-udevd Tainted: G O 4.16.2-2-ARCH #1
[ 3.145072] Hardware name: Dell Inc. Precision 7510/0692Y5, BIOS 1.15.4 12/08/2017
[ 3.145073] Call Trace:
[ 3.145079] dump_stack+0x5c/0x85
[ 3.145086] swiotlb_alloc_coherent+0x1be/0x1d0

Additional info:
02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
Subsystem: Intel Corporation Wireless 8260
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

Steps to reproduce:
Boot the kernel or rmmod + modprobe the iwlwifi module.
   dmesg.txt (67.6 KiB)
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Wednesday, 02 May 2018, 19:46 GMT
Reason for closing:  Fixed
Additional comments about closing:  linux 4.16.4-1
Comment by Jan Alexander Steffens (heftig) - Friday, 20 April 2018, 09:56 GMT
Try booting with intel_iommu=on,igfx_off .
Comment by loqs (loqs) - Friday, 20 April 2018, 11:56 GMT
https://www.spinics.net/lists/kernel/msg2775293.html
https://www.spinics.net/lists/kernel/msg2773070.html
edit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/lib/swiotlb.c?id=9e7f06c8beee304ee21b791653fefcd713f48b9a
Comment by Andrea Girotto (andreagi) - Friday, 20 April 2018, 13:03 GMT
Waiting for the fix, booting with the kernel option: "intel_iommu=on" fixed (or at least is a workaround for) this issue
Comment by Jan Alexander Steffens (heftig) - Friday, 20 April 2018, 13:04 GMT
You should probably keep it enabled. SWIOTLB is a dirty hack for when the IOMMU is disabled.
Comment by loqs (loqs) - Friday, 20 April 2018, 18:03 GMT
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/queue-4.16?id=2cd6bbae7e62961b418c8e0e981be78f35774b05
queued for 4.16.4
Comment by Eli Schwartz (eschwartz) - Wednesday, 02 May 2018, 19:45 GMT
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/log/lib/swiotlb.c?h=v4.16.4

This should be fixed now.

Loading...