linux-kernel - "swiotlb buffer is full" with 4.3.0-rc1 but not 4.2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <07F70BBF6832E34FA1C923241E8833AB7CD40E08@BBYEXM02.pmc-sierra.internal>
Date:	Mon, 21 Sep 2015 15:08:20 +0000
From:	Don Brace <Don.Brace@...s.com>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:	"Elliott, Robert (Persistent Memory)" <elliott@....com>
Subject: "swiotlb buffer is full" with 4.3.0-rc1 but not 4.2

Testing hpsa on 4.3.0-rc1+ I am seeing pci_alloc_consistent failures
during driver initialization.

Are there memory allocation changes that I need to address?

I was not seeing this issue on 4.2.

Rob mentions a s similar issue:
https://lkml.org/lkml/2013/11/30/141




[  838.484555] hpsa 0000:02:00.0: swiotlb buffer is full (sz: 786432 bytes)
[  838.517469] swiotlb: coherent allocation failed for device 0000:02:00.0 size=786432
[  838.554853] CPU: 0 PID: 921 Comm: kworker/0:2 Tainted: G        W  OE   4.3.0-rc1+ #6
[  838.593695] Hardware name: HP ProLiant DL580 Gen8, BIOS P79 05/06/2015
[  838.626936] Workqueue: events work_for_cpu_fn
[  838.647969]  0000000000000000 00000000ce42ca56 ffff880857167c90 ffffffff81311430
[  838.684766]  00000000000c0000 ffff880857167cd0 ffffffff813397b9 ffff880800000008
[  838.721455]  0000000000000220 ffff88185aef9098 00000000000c0000 ffff8808596081b8
[  838.759204] Call Trace:
[  838.771064]  [<ffffffff81311430>] dump_stack+0x44/0x64
[  838.796393]  [<ffffffff813397b9>] swiotlb_alloc_coherent+0x149/0x160
[  838.827266]  [<ffffffff81060ca3>] x86_swiotlb_alloc_coherent+0x43/0x50
[  838.859722]  [<ffffffffa047a1e8>] hpsa_init_one+0x918/0x1c40 [hpsa]
[  838.890547]  [<ffffffff8134e395>] local_pci_probe+0x45/0xa0
[  838.917319]  [<ffffffff8108fde4>] work_for_cpu_fn+0x14/0x20
[  838.944524]  [<ffffffff81092fbc>] process_one_work+0x14c/0x3c0
[  838.972971]  [<ffffffff81093954>] worker_thread+0x244/0x470
[  839.000235]  [<ffffffff81093710>] ? rescuer_thread+0x310/0x310
[  839.028701]  [<ffffffff81099361>] kthread+0xe1/0x100
[  839.052865]  [<ffffffff81099280>] ? kthread_park+0x50/0x50
[  839.080077]  [<ffffffff81669edf>] ret_from_fork+0x3f/0x70
[  839.107368]  [<ffffffff81099280>] ? kthread_park+0x50/0x50

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/