Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #64126

Bug#924895: Updating microcode files didn't help, maybe a kernel problem after all

From Diederik de Haas <didi.debian@cknow.org>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#924895: Updating microcode files didn't help, maybe a kernel problem after all
Date 2019-05-18 15:20 +0200
Message-ID <xZ7pL-5zj-3@gated-at.bofh.it> (permalink)
References <xFW1P-51X-1@gated-at.bofh.it> <xCOtQ-2ON-3@gated-at.bofh.it> <xFW1P-51X-1@gated-at.bofh.it>
Organization Connecting Knowledge

Cross-posted to 2 groups.

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On dinsdag 26 maart 2019 16:11:47 CEST Diederik de Haas wrote:
> I updated /lib/firmware/amd-ucode/*.bin from upstream git (commit
> 7bc246451318b3536d9bfd3c4e46d541a9831b33) and updated initramfs (I'm not
> sure that's the right place) and since then I haven't had the problem
> anymore.

Correction: it still does happen :-/

I reported this bug hoping that a fix for this would fix an issue I'm having 
since I build this AMD Ryzen system in October 2017, namely freezes and 
spontaneous reboots.

I have replaced basically every component, except CPU and RAM.
I have installed every BIOS update hoping that it would fix my issues, but no.
I've had this issue with every kernel version I tried since Oct 2017 (I run 
Debian Sid).
I _think_ the chipset driver 18.50.x 'issue' I mentioned in OP is now fixed 
with updated firmware-nonfree package (although I got a different issue with 
that, see bug #928631)

Doing another search for "microcode 8001137", I found https://
community.amd.com/thread/225795 and through that I found
https://bugzilla.kernel.org/show_bug.cgi?id=196683

And that sounds a LOT like the issue I'm having for 1.5 years now.

So maybe this bug should be re-assigned to the Linux kernel instead (and 
retitled and set Forwarded to that bugzilla report)?
OTOH it very much sounds like a hardware/CPU bug which may be able to be fixed 
with an(other) microcode update?

I'm now trying to figure out how to compile my own kernel so I can enable 
CONFIG_RCU_NOCB_CPU and see whether that makes a difference


Full system spec:
MB: Asus ROG CROSSHAIR VII HERO (BIOS: 2203)
CPU: AMD Ryzen 7 1800X Eight-Core Processor (family: 0x17, model: 0x1, 
stepping: 0x1)
RAM: 2x F4-3200C16D-32GTZ (making for 4x16GB)
PSU: Corsair AX1600i 1600W
GPU: Asus ROG Strix RX VEGA64 OC edition 8GB
OS: Debian GNU/Linux Sid with currently kernel 4.19.37-3

Back to linux.debian.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#924895: No problems since updating ucodes from upstream git Diederik de Haas <didi.debian@cknow.org> - 2019-03-26 16:20 +0100
  Bug#924895: Updating microcode files didn't help, maybe a kernel problem after all Diederik de Haas <didi.debian@cknow.org> - 2019-05-18 15:20 +0200
    Bug#924895: Updating microcode files didn't help, maybe a kernel problem after all Jose R R <Jose.r.r@metztli-it.com> - 2019-05-19 01:40 +0200

csiph-web