Em Tue, 13 Aug 2013 17:11:18 +0530 "Naveen N. Rao" <naveen.n.rao@xxxxxxxxxxxxxxxxxx> escreveu: > On 08/12/2013 08:14 PM, Mauro Carvalho Chehab wrote: > >> But, this only seems to expose the APEI data as a string > >> and doesn't look to really make all the fields available to user-space > >> in a raw manner. Not sure how well this can be utilised by a user-space > >> tool. Do you have suggestions on how we can do this? > > > > There's already an userspace tool that handes it: > > https://git.fedorahosted.org/cgit/rasdaemon.git/ > > > > What is missing there on the current version is the bits that would allow > > to translate from APEI way to report an error (memory node, card, module, > > bank, device) into a DIMM label[1]. > > If I'm reading this right, all APEI data seems to be squashed into a > string in mc_event. Yes. We had lots of discussion about how to map memory errors over the last couple years. Basically, it was decided that the information that could be decoded into a DIMM to be mapped as integers, and all other driver-specific data to be added as strings. On the tests I did, different machines/vendors fill the APEI data on a different way, with makes harder to associate them to a DIMM. > Also, the fru id/text don't seem to be passed to user-space. That's likely because on the systems I tested, those fields were not filled (or maybe they appeared on a latter ACPI version). We should add them also the same string as the other fields there at ghes_edac. Regards, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
