Yup. You are right. I thought I had it enabled, I will send out the new patch soon.
Lance > -----Original Message----- > From: Joe Perches [mailto:[email protected]] > Sent: Thursday, November 29, 2012 3:12 PM > To: Ortiz, Lance E > Cc: [email protected]; [email protected]; [email protected]; > [email protected]; [email protected]; [email protected]; > [email protected]; [email protected]; linux- > [email protected]; [email protected] > Subject: Re: [PATCH 2/3] aerdrv: Enhanced AER logging > > On Thu, 2012-11-29 at 14:54 -0700, Lance Ortiz wrote: > > This patch will provide a more reliable and easy way for user-space > > applications to have access to AER logs rather than reading them from > the > > message buffer. It also provides a way to notify user-space when an > AER > > event occurs. > [] > > diff --git a/drivers/acpi/apei/cper.c b/drivers/acpi/apei/cper.c > > index e6defd8..ef1e1c0 100644 > > --- a/drivers/acpi/apei/cper.c > > +++ b/drivers/acpi/apei/cper.c > > @@ -281,9 +281,16 @@ static void cper_print_pcie(const char *pfx, > const struct cper_sec_pcie *pcie, > > "%s""bridge: secondary_status: 0x%04x, control: 0x%04x\n", > > pfx, pcie->bridge.secondary_status, pcie->bridge.control); > > #ifdef CONFIG_ACPI_APEI_PCIEAER > > - if (pcie->validation_bits & CPER_PCIE_VALID_AER_INFO) { > > + dev = pci_get_domain_bus_and_slot(pcie->device_id.segment, > > + pcie->device_id.bus, pcie->device_id.function); > > + if (!dev) > > + pr_info(KERN_INFO, "PCI AER Cannot get PCI device > %04x:%02x:%02x.%d\n", > > + domain, bus, slot, func); > > You've not tried this with CONFIG_ACPI_APEI_PCIEAER enabled. > > pr_info("PCI AER Cannot get PCI device > %04x:%02x:%02x.%d\n", > domain, bus, slot, func); > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
