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


Groups > linux.debian.kernel > #68665 > unrolled thread

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

Started byMark James <tarotapprentice@yahoo.com>
First post2020-11-25 06:30 +0100
Last post2020-11-25 06:30 +0100
Articles 1 — 1 participant

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.


Contents

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

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

FromMark James <tarotapprentice@yahoo.com>
Date2020-11-25 06:30 +0100
SubjectFwd: EDAC amd64: Error:F0 not found, device 0x1650 (broken BIOS?)
Message-ID<BeVxn-3Tf-3@gated-at.bofh.it>

[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.
> 

[toc] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web