Your message dated Sat, 14 Dec 2019 18:05:19 +0200 with message-id <[🔎] 20191214160519.bdocuy4l563vqcbj@localhost> and subject line Re: Bug#944479: EDAC amd64 regression has caused the Debian Bug report #944479, regarding EDAC amd64 regression to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 944479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944479 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: EDAC amd64 regression
- From: Antonio Russo <antonio.e.russo@gmail.com>
- Date: Sun, 10 Nov 2019 10:00:54 -0700
- Message-id: <36ffcb86-f6f3-aead-612d-6d0b9389e086@gmail.com>
Package: linux-image-5.3.0-2-amd64 Version: 5.3.9-1 Severity: normal --- Please enter the report below this line. --- Upgraded from kernel 5.2.17, and started getting lines like Nov 10 09:13:08 REDACTED kernel: EDAC amd64: Node 0: DRAM ECC enabled. Nov 10 09:13:08 REDACTED kernel: EDAC amd64: F17h detected (node 0). Nov 10 09:13:08 REDACTED kernel: EDAC amd64: Error: F0 not found, device 0x1460 (broken BIOS?) Nov 10 09:13:08 REDACTED kernel: EDAC amd64: Error: Error probing instance: 0 I do have ECC ram, and it claims to be supported, lshw shows "errordetection=multi-bit-ecc", on both 5.2.17 and 5.3.9. This would seem to be a regression, since I didn't have this error on 5.2.17. --- System information. --- Motherboard: X470 Taichi Ultimate Processor: AMD Ryzen 7 3700X Architecture: Kernel: Linux 5.3.0-2-amd64 Debian Release: bullseye/sid
--- End Message ---
--- Begin Message ---
- To: Antonio Russo <antonio.e.russo@gmail.com>
- Cc: 944479-done@bugs.debian.org, debian-kernel@lists.debian.org
- Subject: Re: Bug#944479: EDAC amd64 regression
- From: andreimpopescu@gmail.com
- Date: Sat, 14 Dec 2019 18:05:19 +0200
- Message-id: <[🔎] 20191214160519.bdocuy4l563vqcbj@localhost>
- In-reply-to: <[🔎] b9403e05-3732-28b2-0e67-faccefdeac92@gmail.com>
- References: <36ffcb86-f6f3-aead-612d-6d0b9389e086@gmail.com> <[🔎] 20191214105941.4fhzpv2wtaj7kjgs@localhost> <[🔎] b9403e05-3732-28b2-0e67-faccefdeac92@gmail.com>
Control: fixed 5.4.2-1~exp1 On Sb, 14 dec 19, 08:43:10, Antonio Russo wrote: > Thanks for checking in on this. > > On 12/14/19 3:59 AM, andreimpopescu@gmail.com wrote: > > In the meantime unstable has 5.3.17, you should check if maybe this was > > fixed. > > I moved to Linux 5.4 (trunk, 5.4.2), and the problem is resolved > there. Thank you for confirming. > I'm not sure the correct way to close this bug report given that > version is still in experimental. Doing so with this message, assuming you meant the current version in experimental. Kind regards, Andrei -- Looking after bugs reported against inexistent or removed packagesAttachment: signature.asc
Description: PGP signature
--- End Message ---