All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zheng, Lv" <lv.zheng@intel.com>
To: "Deak, Imre" <imre.deak@intel.com>,
	"Moore, Robert" <robert.moore@intel.com>,
	"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"devel@acpica.org" <devel@acpica.org>
Subject: RE: 4.9-rc1: [TMP_] ACPI namespace lookup failure, AE_ALREADY_EXISTS
Date: Thu, 20 Oct 2016 16:45:23 +0000	[thread overview]
Message-ID: <1AE640813FDE7649BE1B193DEA596E886A2561D7@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1476913001.7633.13.camel@intel.com>

Hi, Imre

> From: Deak, Imre
> Subject: 4.9-rc1: [TMP_] ACPI namespace lookup failure, AE_ALREADY_EXISTS
> 
> Hi,
> 
> after upgrading to 4.9-rc1 I get the following errors occasionally
> during boot and suspend-to-ram on an APL system:
> 
> [   59.513434] ACPI Error: [TMP_] Namespace lookup failure, AE_ALREADY_EXISTS (20160831/dswload2-330)
> [   59.513446] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20160831/psobject-227)
> [   59.513469] ACPI Error: Method parse/execution failed [\_SB.PCI0.SCPG] (Node ffff8802770b7bb8),
> AE_ALREADY_EXISTS (20160831/psparse-543)
> [   59.515415] ACPI Error: Method parse/execution failed [\_SB.PCI0.SDHA._PS3] (Node ffff8802770b7dc0),
> AE_ALREADY_EXISTS (20160831/psparse-543)
> [   59.517118] ACPI: Marking method _PS3 as Serialized because of AE_ALREADY_EXISTS error

Could you send me acpidump output?

> 
> Other than these error messages, booting and suspend/resume seems to work ok.
> Bisecting points to
> commit 74f51b80a0c4ff84fbeb7f12ea43ce66934d29aa
> Author: Lv Zheng <lv.zheng@intel.com>
> Date:   Wed Sep 7 14:07:10 2016 +0800
> 
>     ACPICA: Namespace: Fix dynamic table loading issues
> 
> Reverting this on top of 4.9-rc1 gets rid of the error messages.

This fix is essential.
Without this, all of other ACPICA fixes can easily fall into dead locks.
So we won't simply revert it just because of non-functional-failure error messages.
Instead, we will improve it.

Thanks and best regards
Lv

WARNING: multiple messages have this Message-ID (diff)
From: Zheng, Lv <lv.zheng at intel.com>
To: devel@acpica.org
Subject: Re: [Devel] 4.9-rc1: [TMP_] ACPI namespace lookup failure, AE_ALREADY_EXISTS
Date: Thu, 20 Oct 2016 16:45:23 +0000	[thread overview]
Message-ID: <1AE640813FDE7649BE1B193DEA596E886A2561D7@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: 1476913001.7633.13.camel@intel.com

[-- Attachment #1: Type: text/plain, Size: 1536 bytes --]

Hi, Imre

> From: Deak, Imre
> Subject: 4.9-rc1: [TMP_] ACPI namespace lookup failure, AE_ALREADY_EXISTS
> 
> Hi,
> 
> after upgrading to 4.9-rc1 I get the following errors occasionally
> during boot and suspend-to-ram on an APL system:
> 
> [   59.513434] ACPI Error: [TMP_] Namespace lookup failure, AE_ALREADY_EXISTS (20160831/dswload2-330)
> [   59.513446] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20160831/psobject-227)
> [   59.513469] ACPI Error: Method parse/execution failed [\_SB.PCI0.SCPG] (Node ffff8802770b7bb8),
> AE_ALREADY_EXISTS (20160831/psparse-543)
> [   59.515415] ACPI Error: Method parse/execution failed [\_SB.PCI0.SDHA._PS3] (Node ffff8802770b7dc0),
> AE_ALREADY_EXISTS (20160831/psparse-543)
> [   59.517118] ACPI: Marking method _PS3 as Serialized because of AE_ALREADY_EXISTS error

Could you send me acpidump output?

> 
> Other than these error messages, booting and suspend/resume seems to work ok.
> Bisecting points to
> commit 74f51b80a0c4ff84fbeb7f12ea43ce66934d29aa
> Author: Lv Zheng <lv.zheng(a)intel.com>
> Date:   Wed Sep 7 14:07:10 2016 +0800
> 
>     ACPICA: Namespace: Fix dynamic table loading issues
> 
> Reverting this on top of 4.9-rc1 gets rid of the error messages.

This fix is essential.
Without this, all of other ACPICA fixes can easily fall into dead locks.
So we won't simply revert it just because of non-functional-failure error messages.
Instead, we will improve it.

Thanks and best regards
Lv

  reply	other threads:[~2016-10-20 16:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-19 21:36 4.9-rc1: [TMP_] ACPI namespace lookup failure, AE_ALREADY_EXISTS Imre Deak
2016-10-20 16:45 ` Zheng, Lv [this message]
2016-10-20 16:45   ` [Devel] " Zheng, Lv
2016-10-20 18:44 ` Zheng, Lv
2016-10-20 18:44   ` [Devel] " Zheng, Lv
2016-10-20 21:16   ` Rafael J. Wysocki
2016-10-20 23:05     ` Zheng, Lv
2016-10-20 23:05       ` [Devel] " Zheng, Lv
2016-10-21 19:46 ` Zheng, Lv
2016-10-21 19:46   ` [Devel] " Zheng, Lv
     [not found]   ` <1477216090.7258.9.camel@intel.com>
2016-10-24  6:10     ` Zheng, Lv
2016-10-24  6:10       ` [Devel] " Zheng, Lv
2016-10-24  7:35     ` Zheng, Lv
2016-10-24  7:35       ` [Devel] " Zheng, Lv
2016-10-27 15:31       ` Moore, Robert
2016-10-27 15:31         ` [Devel] " Moore, Robert
2016-10-25  1:14     ` Zheng, Lv
2016-10-25  1:14       ` [Devel] " Zheng, Lv
2016-10-25 12:48       ` Imre Deak
2016-10-25 14:26         ` Zheng, Lv
2016-10-25 14:26           ` [Devel] " Zheng, Lv

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1AE640813FDE7649BE1B193DEA596E886A2561D7@SHSMSX101.ccr.corp.intel.com \
    --to=lv.zheng@intel.com \
    --cc=devel@acpica.org \
    --cc=imre.deak@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=robert.moore@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.