From owner-freebsd-bugs@freebsd.org Tue Mar 26 18:09:58 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 25F2E155A8E5 for ; Tue, 26 Mar 2019 18:09:58 +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 AB4C57765D for ; Tue, 26 Mar 2019 18:09:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 65059155A8E0; Tue, 26 Mar 2019 18:09:57 +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 42E14155A8DE for ; Tue, 26 Mar 2019 18:09:57 +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 D450977659 for ; Tue, 26 Mar 2019 18:09:56 +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 156C4A5BE for ; Tue, 26 Mar 2019 18:09:56 +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 x2QI9tX1015363 for ; Tue, 26 Mar 2019 18:09:55 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x2QI9tod015353 for bugs@FreeBSD.org; Tue, 26 Mar 2019 18:09:55 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: Tue, 26 Mar 2019 18:09:56 +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: Tue, 26 Mar 2019 18:09:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236513 --- Comment #24 from stockhausen@collogia.de --- One step further: The wrong ACPI definitions are indeed the culprit of the wrong C2 state registration. I implemented a lousy patch in acpi.c: /* * Pre-allocate/manage all memory and IO resources. Since rman can't handle * duplicates, we merge any in the sysresource attach routine. */ static int acpi_sysres_alloc(device_t dev) { ... rl =3D BUS_GET_RESOURCE_LIST(device_get_parent(dev), dev); STAILQ_FOREACH(rle, rl, link) { if (rle->res !=3D NULL) { device_printf(dev, "duplicate resource for %jx\n", rle->start); continue; } if (rle->start =3D=3D 0x40b=20 && rle->count =3D=3D 1=20 && rle->type =3D=3D SYS_RES_IOPORT) { printf("ACPI: fake IO port range 0x40b/1 -> 0x400/32\n"); rle->start =3D 0x400; rle->count =3D 32; } So when ACPI wants to register a single port 0x40b we expand the range to 0x400-0x420.=20 With that devinfo -rv shows: nexus0 ... acpi0 Interrupt request lines: 0x9 I/O ports: ... 0x400-0x41f ... cpu0 pnpinfo _HID=3Dnone _UID=3D0 at handle=3D\_PR_.P000 ACPI I/O ports: 0x414 acpi_perf0 acpi_throttle0 hwpstate0 cpufreq0 cpu1 pnpinfo _HID=3Dnone _UID=3D0 at handle=3D\_PR_.P001 ACPI I/O ports: 0x414 acpi_perf1 acpi_throttle1 hwpstate1 Yeah! The second and following cores can register I/O port 0x414. And final= ly sysctl shows all C2 states: # sysctl -a | grep cx_suppo dev.cpu.3.cx_supported: C1/1/0 C2/2/400 dev.cpu.2.cx_supported: C1/1/0 C2/2/400 dev.cpu.1.cx_supported: C1/1/0 C2/2/400 dev.cpu.0.cx_supported: C1/1/0 C2/2/400 Now I need some assistance: 1. Either patch the BIOS. But how? 2. Implement a workaround in CPU registration if port is not yet registered. But how? Thanks in advance. --=20 You are receiving this mail because: You are the assignee for the bug.=