k...@munnari.oz.au (Robert Elz) writes:
>When the
>cpu frequency target is changed to 3400, all the core temp values drop
>to lower than room air temp (which according to my probably inaccurate
>desk lamp, is currently 22.5, the coretemp values are all in the 15-18
>range at the minute).
When
Updating src tree:
P src/doc/3RDPARTY
P src/doc/CHANGES
P src/external/bsd/tmux/dist/CHANGES
P src/external/bsd/tmux/dist/Makefile.am
P src/external/bsd/tmux/dist/Makefile.in
P src/external/bsd/tmux/dist/README
P src/external/bsd/tmux/dist/README.ja
P src/external/bsd/tmux/dist/arguments.c
P
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
first successful build:
2023.06.29.01.30.31 kre src/external/bsd/tmux/dist/cmd-display-menu.c 1.6
Logs can be found at:
Date:Wed, 28 Jun 2023 23:46:24 + (UTC)
From:RVP
Message-ID:
| You can set a lower "critical-max" property on the CPU temps. in
| /etc/envsys.conf to make powerd trigger a shutdown at a lower temperature.
| Say, 75C?
Yex, I know, but at the minute I am not
Date:Wed, 28 Jun 2023 15:08:17 +0900
From:Masanobu SAITOH
Message-ID: <1b1763d8-f565-612c-9336-9fb71d496...@execsw.org>
| Please test the following diff:
| https://www.netbsd.org/~msaitoh/coretemp-20230628-0.dif
Done that, doesn't seem to make any diff
On Thu, 29 Jun 2023, Robert Elz wrote:
The second issue (the one I started investigating) is that (with the
cpu freq at 3401, enabling turbo mode, and I assume, actual frequencies
up to 5500MHz) the temperatures recorded start creeping upwards (when
the system is mostly idle, and nothing is
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2023.06.28.22.24.15.
An extract from the build.sh output follows:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
NetBSD Security Advisory 2023-006
=
Topic: KDC-spoofing in pam_krb5
Version:NetBSD-current: affected prior to 2023-06-20
NetBSD 10.0_BETA:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
NetBSD Security Advisory 2023-005
=
Topic: su(1) bypass via pam_ksu(8)
Version:NetBSD-current: affected prior to 2023-06-20
NetBSD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
NetBSD Security Advisory 2023-004
=
Topic: procfs environ exposure
Version:NetBSD-current: affected prior to 9.99.78
NetBSD 10.0_BETA:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
NetBSD Security Advisory 2023-003
=
Topic: Structure padding memory disclosures
Version:NetBSD-current: affected prior to 2021-09-09
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
NetBSD Security Advisory 2023-002
=
Topic: Various compatibility syscall memory access issues
Version:NetBSD-current: affected before 2020-05-15
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
NetBSD Security Advisory 2023-001
=
Topic: Multiple buffer overflows in USB drivers
Version:NetBSD-current: affected up to 9.99.32
NetBSD
T's value is not fixed
| on newer chips. Please test the following diff:
|
| https://www.netbsd.org/~msaitoh/coretemp-20230628-0.dif
I have fetched it, and will do that. Thanks. I will let you know
the results (will take at least hours, if my system decides not to
co-operate, perhaps longer). My build is starting now.
kre
dmesg -t | grep Tjmax
It seems that the MSR_TEMPERATURE_TARGET's value is not fixed
on newer chips. Please test the following diff:
https://www.netbsd.org/~msaitoh/coretemp-20230628-0.dif
Thanks in advance.
> There are two caveats:
>
> Our driver ignores Tjmax of > 110 C (and uses 100 C as default)
15 matches
Mail list logo
