From owner-freebsd-bugs@freebsd.org Wed Oct 3 19:14:40 2018 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6F33510AAD3B for ; Wed, 3 Oct 2018 19:14:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 08E7A8BB18 for ; Wed, 3 Oct 2018 19:14:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id BFE2710AAD3A; Wed, 3 Oct 2018 19:14:39 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8458910AAD39 for ; Wed, 3 Oct 2018 19:14:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 06D4A8BB16 for ; Wed, 3 Oct 2018 19:14:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 468372033 for ; Wed, 3 Oct 2018 19:14:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w93JEcig025989 for ; Wed, 3 Oct 2018 19:14:38 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w93JEceU025986 for bugs@FreeBSD.org; Wed, 3 Oct 2018 19:14:38 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 231923] [pci] AMD Ryzen X370 chipset PCIe bridge failed to allocate initial memory window Date: Wed, 03 Oct 2018 19:14:38 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: greg@unrelenting.technology X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Oct 2018 19:14:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231923 Bug ID: 231923 Summary: [pci] AMD Ryzen X370 chipset PCIe bridge failed to allocate initial memory window Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: greg@unrelenting.technology Running fairly recent modified CURRENT (actually ALPHA7) from September 26. (Haven't noticed PCIe related changes in the commits since then.) Moved the system from a SATA SSD to an NVMe one. The Mellanox network card = that was installed in the bottom (connected to the X370 chipset) PCIe slot stopp= ed working: pcib8: irq 32 at device 4.0 on pci3 pcib3: attempting to grow memory window for (0xfdf00000-0xfe0fffff,0x200000) front candidate range: 0xfdf00000-0xfe0fffff pcib8: failed to allocate initial memory window: 0xfdf00000-0xfe0fffff pcib3: allocated prefetch range (0xf0800000-0xf0ffffff) for rid 24 of pcib8 pcib8: domain 0 pcib8: secondary bus 36 pcib8: subordinate bus 36 pcib8: prefetched decode 0xf0800000-0xf0ffffff pcib8: could not get PCI interrupt routing table for \134_SB_.PCI0.GPP2.PT02.PT24 - AE_NOT_FOUND pci8: on pcib8 pcib8: allocated bus range (36-36) for rid 0 of pci8 pci8: domain=3D0, physical bus=3D36 pcib3: attempting to grow memory window for (0xfe000000-0xfe0fffff,0x100000) front candidate range: 0xfe000000-0xfe0fffff pcib8: failed to allocate initial memory window (0xfe000000-0xfe0fffff,0x100000) pci8: pci0:36:0:0 bar 0x10 failed to allocate map[18]: type Prefetchable Memory, range 64, base 0xf0800000, size = 23, memory disabled pcib8: allocated prefetch range (0xf0800000-0xf0ffffff) for rid 18 of pci0:36:0:0 pcib2: matched entry for 3.0.INTA pcib2: slot 0 INTA hardwired to IRQ 32 pcib3: slot 4 INTA is routed to irq 32 pcib8: slot 0 INTA is routed to irq 32 pci8: at device 0.0 (no driver attached) [...] mlx4_core0: mem 0xf0800000-0xf0ffffff irq 32 at device 0.0 on p= ci8 mlx4_core: Mellanox ConnectX core driver v3.4.1 (October 2017) mlx4_core: Initializing mlx4_core pcib3: attempting to grow memory window for (0-0xffffffff,0x100000) front candidate range: 0xfe100000-0xfe1fffff back candidate range: 0xfe300000-0xfe3fffff pcib8: failed to allocate initial memory window (0-0xffffffff,0x100000) mlx4_core0: 0x100000 bytes of rid 0x10 res 3 failed (0, 0xffffffffffffffff). mlx4_core0: Couldn't get PCI resources, aborting device_attach: mlx4_core0 attach returned 22 The same thing is happening to pcib9, which has one of the XHCI controllers= on it (so some USB3 ports aren't working), but that's been happening even befo= re the NVMe drive: xhci2: irq 32 at device 0.0 on pci9 pcib3: attempting to grow memory window for (0-0xffffffff,0x100000) front candidate range: 0xfe100000-0xfe1fffff back candidate range: 0xfe300000-0xfe3fffff pcib9: failed to allocate initial memory window (0-0xffffffff,0x8000) xhci2: 0x8000 bytes of rid 0x10 res 3 failed (0, 0xffffffffffffffff). xhci2: Could not map memory device_attach: xhci2 attach returned 12 pciconf looks like this: pcib8@pci0:22:4:0: class=3D0x060400 card=3D0x33061b21 chip=3D0x43b4102= 2 rev=3D0x02 hdr=3D0x01 vendor =3D 'Advanced Micro Devices, Inc. [AMD]' device =3D '300 Series Chipset PCIe Port' class =3D bridge subclass =3D PCI-PCI bus range =3D 36-36 window[1c] =3D type I/O Port, range 32, addr 0xfff000-0xfff, disabled window[20] =3D type Memory, range 32, addr 0xfff00000-0xfffff, disabled window[24] =3D type Prefetchable Memory, range 64, addr 0xf0800000-0xf0ffffff, enabled cap 05[50] =3D MSI supports 1 message, 64 bit=20 cap 01[78] =3D powerspec 3 supports D0 D3 current D0 cap 10[80] =3D PCI-Express 2 downstream port max data 128(512) RO NS link x4(x4) speed 5.0(5.0) ASPM disabled(L0s/L1) slot 1 power limit 26000 mW cap 0d[c0] =3D PCI Bridge card=3D0x33061b21 ecap 0001[100] =3D AER 1 0 fatal 0 non-fatal 1 corrected ecap 0019[200] =3D PCIe Sec 1 lane errors 0 ecap 001e[400] =3D unknown 1 Corrected =3D Receiver Error none1@pci0:36:0:0: class=3D0x020000 card=3D0x002115b3 chip=3D0x675015b= 3 rev=3D0xb0 hdr=3D0x00 vendor =3D 'Mellanox Technologies' device =3D 'MT26448 [ConnectX EN 10GigE, PCIe 2.0 5GT/s]' class =3D network subclass =3D ethernet bar [10] =3D type Memory, range 64, base 0xfe000000, size 1048576, di= sabled bar [18] =3D type Prefetchable Memory, range 64, base 0xf0800000, size 8388608, disabled cap 01[40] =3D powerspec 3 supports D0 D3 current D0 cap 03[48] =3D VPD cap 11[9c] =3D MSI-X supports 128 messages Table in map 0x10[0x7c000], PBA in map 0x10[0x7d000] cap 10[60] =3D PCI-Express 2 endpoint max data 128(256) FLR link x4(x8) speed 5.0(5.0) ASPM disabled(L0s) ecap 000e[100] =3D ARI 1 ecap 0003[148] =3D Serial 1 0002c903004d7392 Moving the network card to the middle slot (taking away half the lanes from= the GPU in the top slot, but it's not like it needs them) fixed it. But I physically can't apply that fix to the XHCI controller :) What's interesting is that the network card *did* work before the NVMe SSD = was installed =E2=80=94 even though the M.2 NVMe lanes are not chipset lanes, t= hey are direct CPU ones. --=20 You are receiving this mail because: You are the assignee for the bug.=