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: Tue, 25 Oct 2016 14:26:34 +0000	[thread overview]
Message-ID: <1AE640813FDE7649BE1B193DEA596E886A259D4B@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1477399707.11683.14.camel@intel.com>

Hi, Imre

> From: Deak, Imre
> Subject: Re: 4.9-rc1: [TMP_] ACPI namespace lookup failure, AE_ALREADY_EXISTS
> 
> On ti, 2016-10-25 at 04:14 +0300, Zheng, Lv wrote:
> > Hi, Imre
> >
> > I think this is the root cause fix:
> > https://github.com/zetalog/linux/commit/108009d0
> > Which seems to be an old trap triggered by the good fix.
> >
> > Could you give the fix commit a try?
> > It’s better to use this branch, where more improvements are included:
> > git clone linux-acpica https://github.com/zetalog/linux
> > git branch acpica-lock linux-acpica/acpica-lock
> > git checkout acpica-lock
> 
> Yes, with the above branch I couldn't reproduce the problem during
> suspend/resume while reverting 108009d0 made the problem reappear.

Thanks for the bug report.
I've sent the patches to the ACPI mailinglist.

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: Tue, 25 Oct 2016 14:26:34 +0000	[thread overview]
Message-ID: <1AE640813FDE7649BE1B193DEA596E886A259D4B@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: 1477399707.11683.14.camel@intel.com

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

Hi, Imre

> From: Deak, Imre
> Subject: Re: 4.9-rc1: [TMP_] ACPI namespace lookup failure, AE_ALREADY_EXISTS
> 
> On ti, 2016-10-25 at 04:14 +0300, Zheng, Lv wrote:
> > Hi, Imre
> >
> > I think this is the root cause fix:
> > https://github.com/zetalog/linux/commit/108009d0
> > Which seems to be an old trap triggered by the good fix.
> >
> > Could you give the fix commit a try?
> > It’s better to use this branch, where more improvements are included:
> > git clone linux-acpica https://github.com/zetalog/linux
> > git branch acpica-lock linux-acpica/acpica-lock
> > git checkout acpica-lock
> 
> Yes, with the above branch I couldn't reproduce the problem during
> suspend/resume while reverting 108009d0 made the problem reappear.

Thanks for the bug report.
I've sent the patches to the ACPI mailinglist.

Best regards
Lv

  reply	other threads:[~2016-10-25 14:26 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
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 [this message]
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=1AE640813FDE7649BE1B193DEA596E886A259D4B@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.