gmane.linux.acpi.devel

[PATCH] ACPI: Fix potential NULL pointer dereference in acpi_processor_add()

Hanjun Guo — 2013-05-23T12:44:26

In acpi_processor_add(), get_cpu_device() will return NULL sometimes,
although the chances are small, I think it should be fixed.

Signed-off-by: Hanjun Guo <hanjun.guo< at >linaro.org>
---
 drivers/acpi/processor_driver.c |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)

diff --git a/drivers/acpi/processor_driver.c b/drivers/acpi/processor_driver.c
index bec717f..dd64f23 100644
--- a/drivers/acpi/processor_driver.c
+++ b/drivers/acpi/processor_driver.c
< at >< at > -579,6 +579,10 < at >< at > static int __cpuinit acpi_processor_add(struct acpi_device
*device)
        per_cpu(processors, pr->id) = pr;

        dev = get_cpu_device(pr->id);
+       if (!dev) {
+               result = -ENODEV;
+               goto err_clear_processor;
+       }
        if (sysfs_create_link(&device->dev.kobj, &dev->kobj, "sysdev")) {
                result = -EFAULT;
                goto err_clear_processor;

Parameter check for EINJ error injection - V3

Chen Gong — 2013-05-23T02:32:01

[PATCH 1/2 V3] ACPI/APEI: Add parameter check before error injection
[PATCH 2/2 V3] ACPI/APEI: Update einj documentation for param1/param2

These two patches are employed to enhance the check for param1/param2
when einj is used. Param1/param2 are very subtle for the guy
who lacks of experience. These two patches add some extra checks to
avoid happening further errors to confuse users.

V3: only update the 1st patch based on Tony and Boris' suggestion.
V2: only update the 1st patch based on Boris' suggestion.
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo< at >vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

ACPI v5 sleep registers broken on Toshiba laptops

Michael Marineau — 2013-05-22T13:39:12

Greetings,

On the recently released Toshiba Kirabook and kernels >= 3.4
suspend/resume only works once. After resume input from things like
the power button, brightness buttons, lid switch, etc. no longer work
and the laptop simply hangs when suspended for a second time. This
appears to also impact other recent Toshiba laptops (although the bug
claims the hang is during the second resume rather than the second
suspend as is my case).
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1094800

Suspend/resume and all the buttons work just fine on v3.3. I bisected
the v3.3->v3.4 change (with the help of patching in a kvm clock fix as
needed) and tracked it down to this commit:

commit 2feec47d4c5f80b05f1650f5a24865718978eea4
Author: Bob Moore <robert.moore< at >intel.com>
Date: Tue Feb 14 15:00:53 2012 +0800

    ACPICA: ACPI 5: Support for new FADT SleepStatus, SleepControl registers

    Adds sleep and wake support for systems with these registers.
    One new file, hwxfsleep.c

    Signed-off-by: Bob Moore <ro

[PATCH] ACPI:add _STA evaluating at do_acpi_find_child()

2013-05-21T11:19:33

From: Jeff Wu <zlinuxkernel< at >gmail.com>

Once do_acpi_find_child() found the first matching handle, it makes the acpi_get_child()
loop stop and return the matching handle. But, at some of the platforms, a "_ADR" is
with the multiple devices, and if one is enabled, the others will be disabled.
Just like a case:
Address : 0x1FFFF ; handle : SB_PCI0.SATA.DEV0
Address : 0x1FFFF ; handle : SB_PCI0.SATA.DEV1
Address : 0x1FFFF ; handle : SB_PCI0.SATA.DEV2

If DEV0 and DEV1 are disabled and DEV2 is enabled, the target is to get DEV2 handle, but
actually it always return the first disabled device DEV0 handle. So add a _STA evaluating
at do_acpi_find_child() to check the device status. If the object exists, but it is disabled,
acpi_get_child() will continue looping to get the correct handle that the object exists and
is enabled.
 

Signed-off-by: Jeff Wu <zlinuxkernel< at >gmail.com>
---
 drivers/acpi/glue.c | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/drivers/acpi/glue.c b/drivers/acpi/glue.c
ind

[PATCH] ACPI / resource: call acpi_get_override_irq() only for legacy IRQ resources

Mika Westerberg — 2013-05-20T15:41:45

acpi_get_override_irq() was added because there was a problem with buggy
BIOSes passing wrong IRQ() resource for the RTC IRQ. Commit that added
the workaround is 61fd47e0c8476 (ACPI: fix two IRQ8 issues in IOAPIC
mode).

With ACPI 5 enumerated devices there are typically one or more extended IRQ
resources for a device (and these IRQs can be shared). However, the
acpi_get_override_irq() workaround forces all IRQs in range 0 - 15 (the
legacy ISA IRQs) to be edge triggered, active high as can be seen from the
dmesg below:

ACPI: IRQ 6 override to edge, high
ACPI: IRQ 7 override to edge, high
ACPI: IRQ 7 override to edge, high
ACPI: IRQ 13 override to edge, high

Also /proc/interrupts for the I2C controllers (INT33C2 and INT33C3) shows
the same thing:

7:          4          0          0          0   IO-APIC-edge INT33C2:00, INT33C3:00

The _CSR method for INT33C2 (and INT33C3) device returns following
resource:

Interrupt (ResourceConsumer, Level, ActiveLow, Shared,,, )
{
0x00000007,
}

which states t

[PATCH] acpi: blacklist win8 OSI for ASUS Zenbok Prime UX31A

Felipe Contreras — 2013-05-20T08:16:33

Otherwise the backlight can't be changed, presumably because the DSDT
contains stub code when in conjunction with Windows 8.

https://wiki.archlinux.org/index.php/ASUS_Zenbook_Prime_UX31A

Signed-off-by: Felipe Contreras <felipe.contreras< at >gmail.com>
---
 drivers/acpi/blacklist.c | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/drivers/acpi/blacklist.c b/drivers/acpi/blacklist.c
index cb96296..a404127 100644
--- a/drivers/acpi/blacklist.c
+++ b/drivers/acpi/blacklist.c
< at >< at > -192,6 +192,12 < at >< at > static int __init dmi_disable_osi_win7(const struct dmi_system_id *d)
 acpi_osi_setup("!Windows 2009");
 return 0;
 }
+static int __init dmi_disable_osi_win8(const struct dmi_system_id *d)
+{
+printk(KERN_NOTICE PREFIX "DMI detected: %s\n", d->ident);
+acpi_osi_setup("!Windows 2012");
+return 0;
+}
 
 static struct dmi_system_id acpi_osi_dmi_table[] __initdata = {
 {
< at >< at > -267,6 +273,14 < at >< at > static struct dmi_system_id acpi_osi_dmi_table[] __initdata = {
      DMI_MATCH(DMI_PRODUCT_NAME, "Satellite P3

Parameter check for EINJ error injection - V2

Chen Gong — 2013-05-20T07:20:31

[PATCH 1/2 V2] ACPI/APEI: Add parameter check before error injection
[PATCH 2/2 V2] ACPI/APEI: Update einj documentation for param1/param2

These two patches are employed to enhance the check for param1/param2
when einj is used. Param1/param2 are very subtle for the guy
who lacks of experience. These two patches add some extra checks to
avoid happening further errors to confuse users.
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo< at >vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH] ACPI / video: Add "Asus UL30A" to ACPI video detect blacklist

Bastian Triller — 2013-05-19T11:52:33

Like on UL30VT, the ACPI video driver can't control backlight correctly on
Asus UL30A.  Vendor driver (asus-laptop) can work.  This patch is to
add "Asus UL30A" to ACPI video detect blacklist in order to use
asus-laptop for video control on the "Asus UL30A" rather than ACPI
video driver.

Signed-off-by: Bastian Triller <bastian.triller< at >gmail.com>
---
 drivers/acpi/video_detect.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/drivers/acpi/video_detect.c b/drivers/acpi/video_detect.c
index 66f6762..e6bd910 100644
--- a/drivers/acpi/video_detect.c
+++ b/drivers/acpi/video_detect.c
< at >< at > -161,6 +161,14 < at >< at > static struct dmi_system_id video_detect_dmi_table[] = {
 DMI_MATCH(DMI_PRODUCT_NAME, "UL30VT"),
 },
 },
+{
+.callback = video_detect_force_vendor,
+.ident = "Asus UL30A",
+.matches = {
+DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK Computer Inc."),
+DMI_MATCH(DMI_PRODUCT_NAME, "UL30A"),
+},
+},
 { },
 };

BGRT wild pointer

Andy Lutomirski — 2013-05-17T19:36:47

My MSI 79A-GD65 (8D) (MS-7760), which is a shining example of firmware
engineering, warns like this on startup:

[    0.061363] ioremap: invalid physical address d0bb01800000001
[    0.061365] ------------[ cut here ]------------
[    0.061368] WARNING: at arch/x86/mm/ioremap.c:85
__ioremap_caller+0x35a/0x370()
[    0.061369] Hardware name: MS-7760
[    0.061370] Modules linked in:
[    0.061372] Pid: 0, comm: swapper/0 Not tainted 3.8.11-200.fc18.x86_64 #1
[    0.061373] Call Trace:
[    0.061377]  [<ffffffff8105e675>] warn_slowpath_common+0x75/0xa0
[    0.061379]  [<ffffffff8105e6ba>] warn_slowpath_null+0x1a/0x20
[    0.061381]  [<ffffffff8104779a>] __ioremap_caller+0x35a/0x370
[    0.061383]  [<ffffffff81059645>] ? efi_bgrt_init+0xc5/0x160
[    0.061385]  [<ffffffff813800b0>] ? acpi_get_table_with_size+0x5f/0xbe
[    0.061386]  [<ffffffff81047807>] ioremap_nocache+0x17/0x20
[    0.061388]  [<ffffffff81059645>] efi_bgrt_init+0xc5/0x160
[    0.061390]  [<ffffffff81d18bb6>] efi_late_init+0x9/0xb
[    0.06139

Get your Free $5 in 30 Seconds or Less

Shelby Clark — 2013-05-17T15:31:50

Yes! Now Free Members can make a whole lot of money and never be harassed about paying for membership. There are no paid memberships. Only Free members that make "You" money on 3 different levels and you get paid 7 different ways. This is the craziest thing you've ever seen. Finally a Real Online Business that you make money with on the first day you sign up and just tell others to get their $5 to make even more. If your one of the vast majority of people that made little or no money online, than that is about to end in 30 Seconds (Unless you type slowly)



Again, thats:

    $5 Free just for Signing Up Guaranteed

    No Paid Memberships so It's Always Free

    Get paid in 7 Different ways

    Get Paid on 3 Levels, No confusing matrices or procedures

    Get Paid for Telling Others to get their free $5

    Grow your own Massive List for Free to contact about anything



Change that situation Right Now.



Go Here Now!!!!

http://goo.gl/YthnO



Make sure to click "Free Member" or "Money Plug-In"

--
To

Parameter check for EINJ error injection

Chen Gong — 2013-05-16T02:29:05

[PATCH 1/2] ACPI/APEI: Add parameter check before error injection
[PATCH 2/2] ACPI/APEI: Update einj documentation for param1/param2

There two patches are employed to enhance the check for param1/param2
when einj is used. Param1/param2 are very subtle for the guy
who lacks of experience. These two patches add some extra checks to
avoid happening further errors to confuse users.

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo< at >vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

enabling aspm on ati radeon

Phillip Susi — 2013-05-16T02:25:37

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I thought that booting with the pcie_aspm=force option should make
sure this was enabled, but passing this to a 3.8.0 kernel, lspci still
shows:

LnkCap:Port #0, Speed 5GT/s, Width x16, ASPM L0s L1, Latency L0
<64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot-
LnkCtl:ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-

What could be disabling ASPM?  dmesg confirms: [    0.000000] PCIe
ASPM is forcibly enabled

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQEcBAEBAgAGBQJRlEOfAAoJEJrBOlT6nu75D7gH/1/Nk62FAELr/IJR49pNFNVB
TY0JflxJ7hRMxGUYtcKCgGLA2UrUSf95fFh11NmWMCZFRXHS/9WQXp2gr8KUGXIp
iOlHHME2egFslbr8nUp3aHkmq0/D7lbZdK7eA1PO6hojnxapygbqt6tjpRKT7Vke
djWz+43IiljDD7ZKz1JoUPjJIEV2v/Eg5BpXFEVEiXXFYFfjAU3ZG95/mNuvTX3T
MraQFQOP/4kqpMc75tSsAsfMHg3ciYOt0GIYIk9SUE6mONkAY6o2g4kRgva5CwQC
bBvhDZcQfx8QsIPlTBa74Kjjx9q7yQyOD6lkJTLE5SQWfTiBwB5ET9D

[PATCH] ACPI / PM: Allow device power states to be used for CONFIG_PM unset

Rafael J. Wysocki — 2013-05-15T23:04:27

From: Rafael J. Wysocki <rafael.j.wysocki< at >intel.com>

Currently, drivers/acpi/device_pm.c depends on CONFIG_PM and all of
the functions defined in there are replaced with static inline stubs
if that option is unset.  However, CONFIG_PM means, roughly, "runtime
PM or suspend/hibernation support" and some of those functions are
useful regardless of that.  For example, they are used by the ACPI
fan driver for controlling fans and acpi_device_set_power() is called
during device removal.  Moreover, device initialization may depend on
setting device power states properly.

For these reasons, make the routines manipulating ACPI device power
states defined in drivers/acpi/device_pm.c available for CONFIG_PM
unset too.

Reported-by: Zhang Rui <rui.zhang< at >intel.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki< at >intel.com>
---
 drivers/acpi/Makefile    |    2 
 drivers/acpi/device_pm.c |  126 +++++++++++++++++++++++------------------------
 include/acpi/acpi_bus.h  |   40 +-------------
 3 files changed, 70 inserti

Disable hibernate -- Live media shouldn't allow it?

Phillip Susi — 2013-05-15T22:14:25

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

When booting from removable media, you may end up mounting a swap
partition on an internal hard disk, thus enabling hibernation.
Inadvertently hibernating ( perhaps in response to ACPI HOT event ) is
silly since the system can not be resumed.  Is there a flag somewhere
to prevent hibernating?  Shouldn't there be and shouldn't it be
disabled by default?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQEcBAEBAgAGBQJRlAjBAAoJEJrBOlT6nu75tD4IANMtQGPJfnwOrnwcL+pmxmRW
1Iq7EpwXtkxMbibcIiLIjtqfPXjupHQMQBxMoHvlZuISPv4lMChRqbM+wBEy5GfN
waGcSilqbHurx+L4xSUE9UmZ6iUOWEvZreQRniTlrFbAV+pClYq2D0Ub2msOo1Ka
Rg0zygVJSs0y6VrTZdUIbutiiGo24KFiJyTkErTnFr21QReIPd5Bq4zwVd+1I+UR
oZY0z49ot8c+m2BhBZ8V6+H0do+zpmcvjmik3b6Dm8sFfGiCnjQVHhmc4tHNZfhS
SnmW8dC+haR7kHAAFmIrd2RRbczD2H3XCM0/QvwVQ8ISz0h6Ejy1MTeNlW87XBA=
=5nIU
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-

How to simulate thermal event?

Phillip Susi — 2013-05-15T20:29:34

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I would like to simulate an acpi HOT or CRT event to test the OS
response.  Is this possible?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRk/AuAAoJEJrBOlT6nu75wqYH/RNkmPoeEPvD/h6NLnpNCbbJ
EmFN5xZSlP8dzUTbGO7BkFNS8YlPp63v2MVtKI6Vh9kF4GUdjEnY/qXATRFTaj6E
Jcbk7qLDzxkBTN3K5CZRaBJUMnq2lGonYWHL5F2VxrlpNCzqvowcAgThVwsFpwnt
TVanaHKt7uZzyHu3oDgAVcXP+5m7OJtwL1YPEgCLNzkXR/XjRvR8PxOpJ/JsOh5x
dzUK84XANnC9vuejvh5rbhDsf1jQtYmzozg0TZkGcvlWchNAe3+OcjQTWD1wh3ub
2USZdNnrhfZ+rfOOSSSmT4diqUmT2RT5ZbnXXj2B7UTwE8HbQSKX59LXCGrxrrE=
=iQaF
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo< at >vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH] acpi: Fix memory leak on acpi_scan_init_hotplug() error path

Catalin Marinas — 2013-05-15T16:49:35

Following commit 6b772e8f9 (ACPI: Update PNPID match handling for
notify), the acpi_scan_init_hotplug() calls acpi_set_pnp_ids() which
allocates acpi_hardware_id and copies a few strings (kstrdup). If the
devices does not have hardware_id set, the function exits without
freeing the previously allocated ids (and kmemleak complains). This
patch calls simply changes 'return' on error to a 'goto out' which calls
acpi_free_pnp_ids().

Signed-off-by: Catalin Marinas <catalin.marinas< at >arm.com>
Reported-by: Larry Finger <Larry.Finger< at >lwfinger.net>
Cc: Toshi Kani <toshi.kani< at >hp.com>
---
 drivers/acpi/scan.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c
index fe158fd..c1bc608 100644
--- a/drivers/acpi/scan.c
+++ b/drivers/acpi/scan.c
< at >< at > -1785,7 +1785,7 < at >< at > static void acpi_scan_init_hotplug(acpi_handle handle, int type)
 acpi_set_pnp_ids(handle, &pnp, type);
 
 if (!pnp.type.hardware_id)
-return;
+goto out;
 
 /*
  * This relies on the fact that a

[PATCH v1 1/2] ACPI, PCI: remove unused global list acpi_pci_roots in pci_root.c

Jiang Liu — 2013-05-14T13:00:38

Now the global list acpi_pci_roots pci_root.c is useless, remove it.

Signed-off-by: Jiang Liu <jiang.liu< at >huawei.com>
Cc: Len Brown <lenb< at >kernel.org>
Cc: "Rafael J. Wysocki" <rjw< at >sisk.pl>
Cc: linux-acpi< at >vger.kernel.org
Cc: linux-kernel< at >vger.kernel.org
---
 drivers/acpi/pci_root.c | 25 +++----------------------
 include/acpi/acpi_bus.h |  1 -
 2 files changed, 3 insertions(+), 23 deletions(-)

diff --git a/drivers/acpi/pci_root.c b/drivers/acpi/pci_root.c
index b80e06e..91ddfd6 100644
--- a/drivers/acpi/pci_root.c
+++ b/drivers/acpi/pci_root.c
< at >< at > -65,10 +65,6 < at >< at > static struct acpi_scan_handler pci_root_handler = {
 .detach = acpi_pci_root_remove,
 };
 
-/* Lock to protect both acpi_pci_roots lists */
-static DEFINE_MUTEX(acpi_pci_root_lock);
-static LIST_HEAD(acpi_pci_roots);
-
 static DEFINE_MUTEX(osc_lock);
 
 /**
< at >< at > -423,7 +419,6 < at >< at > static int acpi_pci_root_add(struct acpi_device *device,
 }
 }
 
-INIT_LIST_HEAD(&root->node);
 root->device = device;
 root->segment = segment & 0xFFFF;
 strcpy(acpi_d

[PATCH] ACPI / LPSS: add support for Intel BayTrail

Mika Westerberg — 2013-05-13T12:42:44

Intel BayTrail has almost the same Low Power Subsystem than Lynxpoint with
few differences. Peripherals are clocked with different speeds (typically
lower) and the clock is not always gated. To support this we add
possibility to share a common fixed rate clock and make clock gating
optional.

Signed-off-by: Mika Westerberg <mika.westerberg< at >linux.intel.com>
---
 drivers/acpi/acpi_lpss.c  |   88 +++++++++++++++++++++++++++++++++++++++++----
 drivers/clk/x86/clk-lpt.c |    4 +--
 2 files changed, 82 insertions(+), 10 deletions(-)

diff --git a/drivers/acpi/acpi_lpss.c b/drivers/acpi/acpi_lpss.c
index 652fd5c..f6d7605 100644
--- a/drivers/acpi/acpi_lpss.c
+++ b/drivers/acpi/acpi_lpss.c
< at >< at > -33,11 +33,19 < at >< at > ACPI_MODULE_NAME("acpi_lpss");
 #define LPSS_SW_LTR0x10
 #define LPSS_AUTO_LTR0x14
 
+struct lpss_shared_clock {
+const char *name;
+unsigned long rate;
+struct clk *clk;
+};
+
 struct lpss_device_desc {
 bool clk_required;
 const char *clkdev_name;
 bool ltr_required;
 unsigned int prv_offset;
+b

[PATCH] ACPI: implement acpi_os_get_timer() according the spec

Mika Westerberg — 2013-05-13T10:27:51

ACPI Timer() opcode should return monotonically increasing clock with 100ns
granularity. Implement this with the help of ktime_get().

Signed-off-by: Mika Westerberg <mika.westerberg< at >linux.intel.com>
---
 drivers/acpi/osl.c |   14 +-------------
 1 file changed, 1 insertion(+), 13 deletions(-)

diff --git a/drivers/acpi/osl.c b/drivers/acpi/osl.c
index 586e7e9..2a22170 100644
--- a/drivers/acpi/osl.c
+++ b/drivers/acpi/osl.c
< at >< at > -835,19 +835,7 < at >< at > void acpi_os_stall(u32 us)
  */
 u64 acpi_os_get_timer(void)
 {
-static u64 t;
-
-#ifdefCONFIG_HPET
-/* TBD: use HPET if available */
-#endif
-
-#ifdefCONFIG_X86_PM_TIMER
-/* TBD: default to PM timer if HPET was not available */
-#endif
-if (!t)
-printk(KERN_ERR PREFIX "acpi_os_get_timer() TBD\n");
-
-return ++t;
+return ktime_to_ns(ktime_get()) / 100;
 }
 
 acpi_status acpi_os_read_port(acpi_io_address port, u32 * value, u32 width)

..

Mr. Dale Alexander — 2013-05-12T23:24:09

I am Mr. Dale Alexander from the bank of Canada, I have a monetary deal
for you. Contact me if interested for more information via: dalealexander< at >careceo.com
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo< at >vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH v2] aerdrv: Move cper_print_aer() call out of interrupt context

Lance Ortiz — 2013-05-09T19:51:35

The following warning was seen on 3.9 when a corrected PCIe error was being
handled by the AER subsystem.

WARNING: at .../drivers/pci/search.c:214 pci_get_dev_by_id+0x8a/0x90()

This occurred because a call to pci_get_domain_bus_and_slot() was added to
cper_print_pcie() to setup for the call to cper_print_aer().  The warning
showed up because cper_print_pcie() is called in an interrupt context and
pci_get* functions are not supposed to be called in that context.

The solution is to move the cper_print_aer() call out of the interrupt
context and into aer_recover_work_func() to avoid any warnings when calling
pci_get* functions.

v2 - Re-worded header text.  Removed prefix arg from cper_print_aer().
     Added TODO message in cper_print_aer().

Signed-off-by: Lance Ortiz <lance.ortiz< at >hp.com>
Acked-by: Borislav Petkov <bp< at >suse.de>
---

 drivers/acpi/apei/cper.c               |   18 ------------------
 drivers/acpi/apei/ghes.c               |    3 ++-
 drivers/pci/pcie/aer/aerdrv_core.c     |    6 +++++-
 drive