Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #65073 > unrolled thread
| Started by | Celejar <celejar@gmail.com> |
|---|---|
| First post | 2019-09-09 05:50 +0200 |
| Last post | 2019-12-15 23:30 +0100 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.debian.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#934781: firmware-iwlwifi: iwl4965: Microcode SW error detected Celejar <celejar@gmail.com> - 2019-09-09 05:50 +0200
Bug#934781: firmware-iwlwifi: iwl4965: Microcode SW error detected Celejar <celejar@gmail.com> - 2019-12-13 18:50 +0100
Bug#934781: firmware-iwlwifi: iwl4965: Microcode SW error detected Tomas Janousek <tomi@nomi.cz> - 2019-12-15 23:30 +0100
| From | Celejar <celejar@gmail.com> |
|---|---|
| Date | 2019-09-09 05:50 +0200 |
| Subject | Bug#934781: firmware-iwlwifi: iwl4965: Microcode SW error detected |
| Message-ID | <yEiQF-5ph-1@gated-at.bofh.it> |
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. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled firmware-iwlwifi depends on no packages. firmware-iwlwifi recommends no packages. Versions of packages firmware-iwlwifi suggests: ii initramfs-tools 0.135 -- no debconf information
[toc] | [next] | [standalone]
| From | Celejar <celejar@gmail.com> |
|---|---|
| Date | 2019-12-13 18:50 +0100 |
| Message-ID | <zcXeF-7la-3@gated-at.bofh.it> |
| In reply to | #65073 |
On Fri, 13 Dec 2019 15:29:23 +1030 Andrew Bettison <andrew@iverin.com.au> wrote: > On Sun, 08 Sep 2019 23:43:04 -0400 Celejar <celejar@gmail.com> 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
[toc] | [prev] | [next] | [standalone]
| From | Tomas Janousek <tomi@nomi.cz> |
|---|---|
| Date | 2019-12-15 23:30 +0100 |
| Message-ID | <zdKyK-4ht-3@gated-at.bofh.it> |
| In reply to | #65073 |
Hi, On Fri, Dec 13, 2019 at 03:29:23PM +1030, Andrew Bettison wrote: > 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. Can you perhaps try the current version as well? There's been one additional change to iwlwifi firmwares since then: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=40e4162adfc91390f6fbbd8269f9439832af1dde (I haven't tested either, I just downgraded to 20190502-1. Don't have the mental budget to deal with another broken thing now.) -- Tomáš Janoušek, a.k.a. Pivník, a.k.a. Liskni_si, http://work.lisk.in/
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web