Linux ACPI
 help / color / mirror / Atom feed
From: "Michal Suchánek" <msuchanek@suse.de>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Schmauss, Erik" <erik.schmauss@intel.com>,
	Lv <lv.zheng@intel.com>,
	Rafael Wysocki <rafael.j.wysocki@intel.com>,
	Robert Moore <robert.moore@intel.com>,
	Len Brown <lenb@kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	devel@acpica.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Takashi Iwai <tiwai@suse.com>
Subject: Re: Regression: 18996f2db918 ("ACPICA: Events: Stop unconditionally clearing ACPI IRQs during suspend/resume" breaks resume from suspend
Date: Tue, 21 Aug 2018 16:34:21 +0200	[thread overview]
Message-ID: <20180821163421.3208af59@kitsune.suse.cz> (raw)
In-Reply-To: <CAJZ5v0hMZ_bmCy7vQBfzu6RNVkCX0V9qRtqYVNmFOefc1TnGCA@mail.gmail.com>

On Tue, 21 Aug 2018 08:50:36 +0200
"Rafael J. Wysocki" <rafael@kernel.org> wrote:

> On Mon, Aug 20, 2018 at 6:29 PM Michal Suchánek <msuchanek@suse.de>
> wrote:
> >
> > Hello,
> >
> > after commit 18996f2db918 ("ACPICA: Events: Stop unconditionally
> > clearing ACPI IRQs during suspend/resume") I am no longer able to
> > resume from suspend.
> >
> > Reported in bugzilla
> > https://bugzilla.kernel.org/show_bug.cgi?id=200841
> >
> > Reverting this on top of 4.18 fixes the issue. acpidump output is
> > attaches in the bugzilla.
> >
> > Is there anything else that can be done to diagnose the issue?  
> 
> Can you please test the patch at
> https://patchwork.kernel.org/patch/10563631/ to start with?
> 

Yes, that works for me.

Thanks

Michal

      reply	other threads:[~2018-08-21 14:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-20 16:29 Regression: 18996f2db918 ("ACPICA: Events: Stop unconditionally clearing ACPI IRQs during suspend/resume" breaks resume from suspend Michal Suchánek
2018-08-21  6:50 ` Rafael J. Wysocki
2018-08-21 14:34   ` Michal Suchánek [this message]

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=20180821163421.3208af59@kitsune.suse.cz \
    --to=msuchanek@suse.de \
    --cc=devel@acpica.org \
    --cc=erik.schmauss@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lv.zheng@intel.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rafael@kernel.org \
    --cc=robert.moore@intel.com \
    --cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox