Bug#589187: mcelog: problem reading memory diagnosis

notfound 589187 1.0~pre3-3 close 589187 thanks Andi Kleen wrote: >> AMD Phenom(tm) II X4 945 Processor stepping 02 > > There's no code to decode DIMMs for that CPU (I'm not sure > So should probably disable the message for those systems. > I'll look into that. Thanks Andi. With that I'll be c

Bug#589187: mcelog: problem reading memory diagnosis

On Sat, Jul 17, 2010 at 11:30:19AM +0200, Julien BLACHE wrote: > > standard does not have a standardized way to do the matching mcelog > > wants to do, but my test boxes allowed it through the non standard > > parsing so I implemented it this way. > > Is there anything you'd need beside the dmidec

Bug#589187: mcelog: problem reading memory diagnosis

On Sat, Jul 17, 2010 at 10:48:19AM +0200, Julien BLACHE wrote: > Toni Mueller wrote: > > Hi Toni, Andi, > > Andi: We're trying to diagnose a DMI table parsing failure in > memdb.c. The output below is a patched mcelog that outputs the DMI > string it's failing to parse. > > Looks like the DMI t

Bug#589187: mcelog: problem reading memory diagnosis

Andi Kleen wrote: Hi, >> Looks like the DMI table is crap, I think you'll confirm that :) > > Well it's not crap -- the format for the bank locator is not standardized > and I just made it work on some common systems. So actually failures > for the prefill happen quite often. Unfortunately the S

Bug#589187: mcelog: problem reading memory diagnosis

Toni Mueller wrote: Hi Toni, Andi, Andi: We're trying to diagnose a DMI table parsing failure in memdb.c. The output below is a patched mcelog that outputs the DMI string it's failing to parse. Looks like the DMI table is crap, I think you'll confirm that :) > I've applied the patch. This is w

Bug#589187: mcelog: problem reading memory diagnosis

Hi Julien, On Fri, 16.07.2010 at 12:17:19 +0200, Julien BLACHE wrote: > Toni Mueller wrote: > > Jul 15 21:44:02 spruce mcelog: Failed to parse DMI data > OK, new patch, new output ;) I've applied the patch. This is what I get: Jul 16 21:40:31 spruce mcelog: Failed to parse DMI data: [BANK0] J

Bug#589187: mcelog: problem reading memory diagnosis

Toni Mueller wrote: Hi, > Jul 15 21:44:02 spruce mcelog: Failed to parse DMI data OK, new patch, new output ;) JB. -- Julien BLACHE | Debian, because code matters more Debian & GNU/Linux Developer| Public key available on

Bug#589187: mcelog: problem reading memory diagnosis

Hi Julien, On Thu, 15.07.2010 at 21:24:13 +0200, Julien BLACHE wrote: > Apply the attached patch and rebuild mcelog, install the package and > restart the daemon; you should get some more output to syslog. done. I get: Jul 15 21:44:02 spruce mcelog: Failed to parse DMI data Jul 15 21:44:02 spr

Bug#589187: mcelog: problem reading memory diagnosis

Toni Mueller wrote: Hi Toni, >> There are two reasons why this message can appear, so could you >> instrument memdb.c:prefill_memdb() to distinguish between parse errors > ^^ > > maybe, if I figure out what that means, or if you explain it to me. ;| > > So far, I understand: Compile wi

Bug#589187: mcelog: problem reading memory diagnosis

Hi Julien, On Thu, 15.07.2010 at 19:03:17 +0200, Julien BLACHE wrote: > Toni Mueller wrote: > > Jul 15 10:47:08 debian mcelog: failed to prefill DIMM database from DMI data > > > dmidecode has no problems showing detailed information about my memory. > > There are two reasons why this message

Bug#589187: mcelog: problem reading memory diagnosis

Toni Mueller wrote: Hi, > on system startup, mcelog has this to say: > > Jul 15 10:47:08 debian mcelog: failed to prefill DIMM database from DMI data > dmidecode has no problems showing detailed information about my memory. There are two reasons why this message can appear, so could you instru

Bug#589187: mcelog: problem reading memory diagnosis

Package: mcelog Version: 1.0~pre3-3 Severity: normal Tags: upstream Hi, on system startup, mcelog has this to say: Jul 15 10:47:08 debian mcelog: failed to prefill DIMM database from DMI data Jul 15 10:47:08 debian mcelog: Kernel does not support page offline interface dmidecode has no proble