![](https://seccdn.libravatar.org/avatar/ab45a2435cd3d6457b6510bb63114bed.jpg?s=120&d=mm&r=g)
On Thu, Apr 23, 2015, at 08:00 AM, Jan Beulich wrote:
Unclear if that entry/value is relevant.
Indeed this very much looks like what you need. But you want to adjust it towards the 1.0 Gb value, not the 3.25 Gb one.
Manually changing the TOLUD value Dynamic -> 1.0GB does leave the system bootable, but does NOT change the issue. Still, dmesg | grep "BAR 14" [ 0.282672] pci 0000:08:00.0: BAR 14: no space for [mem size 0x00400000] [ 0.282673] pci 0000:08:00.0: BAR 14: failed to assign [mem size 0x00400000] [ 0.282674] pci 0000:08:00.0: BAR 14: no space for [mem size 0x00400000] [ 0.282675] pci 0000:08:00.0: BAR 14: failed to assign [mem size 0x00400000] [ 0.282678] pci 0000:09:01.0: BAR 14: no space for [mem size 0x00400000] [ 0.282678] pci 0000:09:01.0: BAR 14: failed to assign [mem size 0x00400000] [ 0.282680] pci 0000:09:01.0: BAR 14: no space for [mem size 0x00400000] [ 0.282680] pci 0000:09:01.0: BAR 14: failed to assign [mem size 0x00400000] Would an interim value -- BETWEEN 1 & 3.25 GB -- make a difference? Or is the min/max test sufficient? Logs next. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org