Bug#945055: linux: CPU runs at considerably higher temperatures
btw: 5.3.15-1 seems to be still affected. While I see mostly "normal" temperatures right after boot (and when everything has settled)... after some point in time, tmeperatures get up and remain at high levels, e.g. : Package id 0: +81.0°C (high = +100.0°C, crit = +100.0°C) Core 0:+75.0°C (high = +100.0°C, crit = +100.0°C) Core 1:+74.0°C (high = +100.0°C, crit = +100.0°C) even though top shows an effectively idle system. Cheers, Chris.
Processed: linux: CPU runs at considerably higher temperatures
Processing control commands: > reassign -1 linux Bug #945055 [intel-microcode] intel-microcode: CPU runs at considerably higher temperatures Bug reassigned from package 'intel-microcode' to 'linux'. No longer marked as found in versions intel-microcode/3.20191115.1. Ignoring request to alter fixed versions of bug #945055 to the same values previously set > retitle -1 linux: CPU runs at considerably higher temperatures Bug #945055 [linux] intel-microcode: CPU runs at considerably higher temperatures Changed Bug title to 'linux: CPU runs at considerably higher temperatures' from 'intel-microcode: CPU runs at considerably higher temperatures'. -- 945055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#934781: firmware-iwlwifi: iwl4965: Microcode SW error detected
On Fri, 13 Dec 2019 15:29:23 +1030 Andrew Bettison wrote: > On Sun, 08 Sep 2019 23:43:04 -0400 Celejar wrote: > > > Package: firmware-iwlwifi > > Version: 20190717-2 > > Followup-For: Bug #934781 > > > > I did some further digging - in my case, at least, the problem seems to > > be triggered by some relatively recent kernel change. I combed through > > the system journal for the last few months, and the problem first starts > > appearing in the logs a few days after I began running kernel 5.2.x > > (from 5.2.7 through 5.2.9). Previously, while running 4.19.x, the > > problem never appears. > > > > I haven't done a bisection, but it seems pretty clear at this point that > > there's a microcode bug that has begun to be triggered by something in > > newer kernels. > As an experiment, I downloaded the tarball from > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tag/?h=20190815 > > (as recommended in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939262 ), and manually > copied its intel/* and iwlwifi-* files into /lib/firmware (overwriting > the ones installed by the firmware-iwlwifi package). > > After rebooting kernel 5.3.0-2 (amd64) I still get "iwlwifi: Microcode > SW error" messages accompanied by "ieee80211 phy0: Hardware restart was > requested" during periods of high Wi-Fi throughput, but they do not > cause the Wi-Fi to hang. So the newer firmware appears to rectify the > worst part of the problem (Wi-Fi freeze) but does not fully resolve the > problem. On my system, the problem last appeared on Sep. 17 (with a Debian kernel version 5.2.9-2). Since then, I have not seen any "Microcode SW" errors. I've been running 4.19.72 (self-built), 5.2.17-1, 5.3.7-1, 5.3.9 (-1, -2, -3), and 5.3.15-1 (Debian). [I examined the boot logs with: ~# journalctl -S 2019-06-01 | grep "Linux ver\|Microcode SW" ] Celejar
Re: [PATCH] libbpf: Fix readelf output parsing for Fedora
On Fri, Dec 13, 2019 at 2:11 AM Thadeu Lima de Souza Cascardo
wrote:
>
> Fedora binutils has been patched to show "other info" for a symbol at the
> end of the line. This was done in order to support unmaintained scripts
> that would break with the extra info. [1]
>
> [1]
> https://src.fedoraproject.org/rpms/binutils/c/b8265c46f7ddae23a792ee8306fbaaeacba83bf8
>
> This in turn has been done to fix the build of ruby, because of checksec.
> [2] Thanks Michael Ellerman for the pointer.
>
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1479302
>
> As libbpf Makefile is not unmaintained, we can simply deal with either
> output format, by just removing the "other info" field, as it always comes
> inside brackets.
>
> Cc: Aurelien Jarno
> Fixes: 3464afdf11f9 (libbpf: Fix readelf output parsing on powerpc with
> recent binutils)
> Reported-by: Justin Forbes
> Signed-off-by: Thadeu Lima de Souza Cascardo
> ---
I was briefly playing with it and trying to make it use nm to dump
symbols, instead of parsing more human-oriented output of readelf, but
somehow nm doesn't output symbols with @@LIBBPF.* suffix at the end,
so I just gave up. So I think this one is good.
This should go through bpf-next tree.
Acked-by: Andrii Nakryiko
> tools/lib/bpf/Makefile | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tools/lib/bpf/Makefile b/tools/lib/bpf/Makefile
> index defae23a0169..23ae06c43d08 100644
> --- a/tools/lib/bpf/Makefile
> +++ b/tools/lib/bpf/Makefile
> @@ -147,6 +147,7 @@ TAGS_PROG := $(if $(shell which etags
> 2>/dev/null),etags,ctags)
>
> GLOBAL_SYM_COUNT = $(shell readelf -s --wide $(BPF_IN_SHARED) | \
>cut -d "@" -f1 | sed 's/_v[0-9]_[0-9]_[0-9].*//' |
> \
> + sed 's/\[.*\]//' | \
>awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$NF}'
> | \
>sort -u | wc -l)
> VERSIONED_SYM_COUNT = $(shell readelf -s --wide $(OUTPUT)libbpf.so | \
> @@ -213,6 +214,7 @@ check_abi: $(OUTPUT)libbpf.so
> "versioned in $(VERSION_SCRIPT)." >&2; \
> readelf -s --wide $(BPF_IN_SHARED) | \
> cut -d "@" -f1 | sed 's/_v[0-9]_[0-9]_[0-9].*//' | \
> + sed 's/\[.*\]//' | \
> awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$NF}'| \
> sort -u > $(OUTPUT)libbpf_global_syms.tmp; \
> readelf -s --wide $(OUTPUT)libbpf.so | \
> --
> 2.24.0
>
Re: [PATCH] libbpf: fix readelf output parsing on powerpc with recent binutils
On Thu, 2019-12-12 at 11:53 +1100, Michael Ellerman wrote: > Thadeu Lima de Souza Cascardo writes: [...] > > This is a patch on binutils carried by Fedora: > > > > https://src.fedoraproject.org/rpms/binutils/c/b8265c46f7ddae23a792ee8306fbaaeacba83bf8 > > > > " b8265c Have readelf display extra symbol information at the end of the > > line. " > > > > It has the following comment: > > > > # FIXME:The proper fix would be to update the scripts that are expecting > > # a fixed output from readelf. But it seems that some of them are > > # no longer being maintained. > > > > This commit is from 2017, had it been on binutils upstream, maybe the > > situation > > right now would be different. > > Bleeping bleep. > > Looks like it was actually ruby that was the original problem: > > https://bugzilla.redhat.com/show_bug.cgi?id=1479302 > > > Why it wasn't hacked around in the ruby package I don't know, doing it in > the distro binutils package is not ideal. That wouldn't help people building Ruby from upstream. Any tool generating tabular output like this should add new fields at the end (or show them only if requested), since there are bound to be scripts that parse the output like this. So I think Fedora's change to readelf was reasonable, but should have been pushed upstream as soon as possible. Now everyone is going to have to deal with both formats. Ben. -- Ben Hutchings Horngren's Observation: Among economists, the real world is often a special case. signature.asc Description: This is a digitally signed message part
[PATCH] libbpf: Fix readelf output parsing for Fedora
Fedora binutils has been patched to show "other info" for a symbol at the
end of the line. This was done in order to support unmaintained scripts
that would break with the extra info. [1]
[1]
https://src.fedoraproject.org/rpms/binutils/c/b8265c46f7ddae23a792ee8306fbaaeacba83bf8
This in turn has been done to fix the build of ruby, because of checksec.
[2] Thanks Michael Ellerman for the pointer.
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1479302
As libbpf Makefile is not unmaintained, we can simply deal with either
output format, by just removing the "other info" field, as it always comes
inside brackets.
Cc: Aurelien Jarno
Fixes: 3464afdf11f9 (libbpf: Fix readelf output parsing on powerpc with recent
binutils)
Reported-by: Justin Forbes
Signed-off-by: Thadeu Lima de Souza Cascardo
---
tools/lib/bpf/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/lib/bpf/Makefile b/tools/lib/bpf/Makefile
index defae23a0169..23ae06c43d08 100644
--- a/tools/lib/bpf/Makefile
+++ b/tools/lib/bpf/Makefile
@@ -147,6 +147,7 @@ TAGS_PROG := $(if $(shell which etags
2>/dev/null),etags,ctags)
GLOBAL_SYM_COUNT = $(shell readelf -s --wide $(BPF_IN_SHARED) | \
cut -d "@" -f1 | sed 's/_v[0-9]_[0-9]_[0-9].*//' | \
+ sed 's/\[.*\]//' | \
awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$NF}' |
\
sort -u | wc -l)
VERSIONED_SYM_COUNT = $(shell readelf -s --wide $(OUTPUT)libbpf.so | \
@@ -213,6 +214,7 @@ check_abi: $(OUTPUT)libbpf.so
"versioned in $(VERSION_SCRIPT)." >&2; \
readelf -s --wide $(BPF_IN_SHARED) | \
cut -d "@" -f1 | sed 's/_v[0-9]_[0-9]_[0-9].*//' | \
+ sed 's/\[.*\]//' | \
awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$NF}'| \
sort -u > $(OUTPUT)libbpf_global_syms.tmp; \
readelf -s --wide $(OUTPUT)libbpf.so | \
--
2.24.0
