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

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

Bug#944479: EDAC amd64 regression

Back to article view | Back to linux.debian.kernel

Contents

  Bug#944479: EDAC amd64 regression Antonio Russo <antonio.e.russo@gmail.com> - 2019-11-10 18:10 +0100
    Processed: Re: Bug#944479: EDAC amd64 regression "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-12-14 12:10 +0100
    Bug#944479: EDAC amd64 regression andreimpopescu@gmail.com - 2019-12-14 12:10 +0100
      Bug#944479: EDAC amd64 regression Antonio Russo <antonio.e.russo@gmail.com> - 2019-12-14 16:50 +0100
    Bug#944479: marked as done (EDAC amd64 regression) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-12-14 17:10 +0100
    Processed: Re: Bug#944479: EDAC amd64 regression "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-12-14 17:20 +0100
    Bug#944479: EDAC amd64 regression andreimpopescu@gmail.com - 2019-12-14 17:20 +0100

#65605 — Bug#944479: EDAC amd64 regression

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

[toc] | [next] | [standalone]

#65867 — Processed: Re: Bug#944479: EDAC amd64 regression

Processing control commands:

> reassign -1 src:linux
Bug #944479 [linux-image-5.3.0-2-amd64] EDAC amd64 regression
Warning: Unknown package 'linux-image-5.3.0-2-amd64'
Bug reassigned from package 'linux-image-5.3.0-2-amd64' to 'src:linux'.
No longer marked as found in versions linux-signed-amd64/5.3.9+1.
Ignoring request to alter fixed versions of bug #944479 to the same values previously set

-- 
944479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944479
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#65868

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

Control: reassign -1 src:linux

On Du, 10 nov 19, 10:00:54, Antonio Russo wrote:
> 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.

In the meantime unstable has 5.3.17, you should check if maybe this was 
fixed.

> --- System information. ---
> Motherboard: X470 Taichi Ultimate
> Processor: AMD Ryzen 7 3700X
> 
> Architecture:
> Kernel: Linux 5.3.0-2-amd64
> 
> Debian Release: bullseye/sid

Kind regards,
Andrei
-- 
Looking after bugs reported against inexistent or removed packages

[toc] | [prev] | [next] | [standalone]

#65870

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.  I'm
not sure the correct way to close this bug report given that version is still
in experimental.

Antonio

[toc] | [prev] | [next] | [standalone]

#65871 — Bug#944479: marked as done (EDAC amd64 regression)

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

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

[toc] | [prev] | [next] | [standalone]

#65872 — Processed: Re: Bug#944479: EDAC amd64 regression

Processing control commands:

> fixed -1 5.4.2-1~exp1
Bug #944479 {Done: andreimpopescu@gmail.com} [src:linux] EDAC amd64 regression
Marked as fixed in versions linux/5.4.2-1~exp1.

-- 
944479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944479
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#65873

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

Control: fixed -1 5.4.2-1~exp1

On Sb, 14 dec 19, 18:05:19, andreimpopescu@gmail.com wrote:
> 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.

Ugh, messed up the syntax, should be correct now.

Kind regards,
Andrei
-- 
Looking after bugs reported against inexistent or removed packages

[toc] | [prev] | [standalone]

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

csiph-web