From owner-freebsd-bugs@freebsd.org Mon Mar 25 20:16:55 2019 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 31460154C95E for ; Mon, 25 Mar 2019 20:16:55 +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 A38C885D2F for ; Mon, 25 Mar 2019 20:16:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 5C96F154C95D; Mon, 25 Mar 2019 20:16:54 +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 1B787154C95C for ; Mon, 25 Mar 2019 20:16:54 +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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 908C685D2C for ; Mon, 25 Mar 2019 20:16:53 +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 C97391E41B for ; Mon, 25 Mar 2019 20:16:52 +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 x2PKGqu0021222 for ; Mon, 25 Mar 2019 20:16:52 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x2PKGqcx021221 for bugs@FreeBSD.org; Mon, 25 Mar 2019 20:16:52 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 236513] AMD Jaguar: Only CPU core 0 detects C2 state Date: Mon, 25 Mar 2019 20:16:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: stockhausen@collogia.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Mar 2019 20:16:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236513 --- Comment #23 from stockhausen@collogia.de --- ok. ignore comment #22 i try to explain it once again. The problem seems to= be the other way round. CPU wants to register port 0x414 for C state handling. This should be cover= ed by BIOS ACPI tables starting at port 0x3e0 with a total of 2328 (0x918) por= ts. Due to misconfiguaration this port range is attached to the PCIe bridge. acpi_set_resource() simply ignores this registration /* * Ignore most resources for PCI root bridges. Some BIOSes * incorrectly enumerate the memory ranges they decode as plain * memory resources instead of as ResourceProducer ranges. Other * BIOSes incorrectly list system resource entries for I/O ranges * under the PCI bridge. Do allow the one known-correct case on * x86 of a PCI bridge claiming the I/O ports used for PCI config * access. */ #if defined(__i386__) || defined(__amd64__) if (type =3D=3D SYS_RES_MEMORY || type =3D=3D SYS_RES_IOPORT) { if (ACPI_SUCCESS(AcpiGetObjectInfo(ad->ad_handle, &devinfo))) { if ((devinfo->Flags & ACPI_PCI_ROOT_BRIDGE) !=3D 0) { if (!(type =3D=3D SYS_RES_IOPORT && start =3D=3D CONF1_ADDR= _PORT)) { printf("ADBG: acpi_set_resource(%lx,%lu) inside root bridge\n", start,count); AcpiOsFree(devinfo); return (0); } } AcpiOsFree(devinfo); } } #endif So we are left without port 0x414. This gets registered later under CPU0. S= ee devinfo: cpu0 pnpinfo _HID=3Dnone _UID=3D0 at handle=3D\_PR_.P000 I/O ports: 0x414 If registragtion works fine this should read "ACPI I/o port" and port 0x414 should be visible below acpi0 node. To fix that situation in a clean way acpi_cpu_cx_cst() should re-register t= he port below acpi0 just for safety. No idea how to do that... --=20 You are receiving this mail because: You are the assignee for the bug.=