Date: Sun, 28 Aug 2022 18:51:19 +0000 From: bugzilla-noreply@freebsd.org To: acpi@FreeBSD.org Subject: [Bug 264775] [PATCH] acpi_thermal: passive cooling only throttles cpu0 Message-ID: <bug-264775-16045-puO1o4wqJ9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-264775-16045@https.bugs.freebsd.org/bugzilla/> References: <bug-264775-16045@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D264775 --- Comment #6 from rkoberman@gmail.com --- (In reply to crahman from comment #4) You are correct in that I see little change to my problem with this patch. = I've now been running it for about 3 weeks. One thing that really surprised me was that the weird case where I see cpu0= at 2101 and all others at a reduced speed, usually 400, the lowest speed, but occasionally at a speed between 2100 and 400 still occurs. I didn't think t= hat this should be possible! Obviously having a CPU showing different speeds for the two threads is not possible. I suspect that this is related to the issu= e I am having. I can say that the sysctl lies. I can see all eight "CPUs" reporting 2101 a= nd a compile of audio/taglib taking over 2 minutes to build while, when really running at 2101, it takes 15 seconds. Clearly something is broken, but this= is not it. This may be going away as I am about to install CURRENT on my new laptop. (= Just partitioned the SSD.) Hopefully, it will be better behaved, but I am concer= ned as it has cores running at different speeds and different numbers of hyper-threads, (AlderLake) and FreeBSD will not really know how to deal with this. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-264775-16045-puO1o4wqJ9>