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


Groups > linux.debian.kernel > #68665

Fwd: EDAC amd64: Error:F0 not found, device 0x1650 (broken BIOS?)

From Mark James <tarotapprentice@yahoo.com>
Newsgroups linux.debian.kernel
Subject Fwd: EDAC amd64: Error:F0 not found, device 0x1650 (broken BIOS?)
Date 2020-11-25 06:30 +0100
Message-ID <BeVxn-3Tf-3@gated-at.bofh.it> (permalink)
References <BeVxn-3Tf-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


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


Begin forwarded message:

> From: Mark James <tarotapprentice@yahoo.com>
> Date: 25 November 2020 at 4:01:13 pm AEDT
> To: submit@bugs.debian.org
> Subject: EDAC amd64: Error:F0 not found, device 0x1650 (broken BIOS?)
> 
> Package: linux-image-amd64
> Version: 5.8.10-1~bpo10+1
> 
> Recently upgraded a Ryzen 3900X system to a 5900X. Upon boot I get this message repeated 24 times.
> 
> EDAC amd64: Error: F0 not found, device 0x1650 (broken BIOS?)
> 
> I also tried the 5.9.6 kernel from buster and it did the same. Is there an upstream patch to enable device 0x1650 in the amd64 EDAC code?
> 
> A search suggests (for other Linux distributions) to upgrade the kernel, however I am running a fairly recent one from buster-backports and have tried the one from bullseye.
> 

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


Thread

Fwd: EDAC amd64: Error:F0 not found, device 0x1650 (broken BIOS?) Mark James <tarotapprentice@yahoo.com> - 2020-11-25 06:30 +0100

csiph-web