From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>, Bjorn Helgaas <bhelgaas@google.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux PCI <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
1745646@bugs.launchpad.net
Subject: Re: [Regression] PCI / PM: Simplify device wakeup settings code
Date: Mon, 16 Apr 2018 11:31:08 -0400 [thread overview]
Message-ID: <ae84e595-dede-1409-4aff-3a29a310f2ba@canonical.com> (raw)
In-Reply-To: <CAJZ5v0j8GAatWoAra37y3c-ti2Ft5am75KONgEkjB6AaypkCqg@mail.gmail.com>
On 04/13/2018 05:34 PM, Rafael J. Wysocki wrote:
> On Fri, Apr 13, 2018 at 7:56 PM, Joseph Salisbury
> <joseph.salisbury@canonical.com> wrote:
>> Hi Rafael,
>>
>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>> bisect, it was found that reverting the following two commits resolved
>> this bug:
>>
>> 0ce3fcaff929 ("PCI / PM: Restore PME Enable after config space restoration")
>> 0847684cfc5f("PCI / PM: Simplify device wakeup settings code")
>>
>> This is a regression introduced in v4.13-rc1 and still exists in
>> mainline. The bug causes the battery to drain when the system is
>> powered down and unplugged, which does not happed prior to these two
>> commits.
> What system and what do you mean by "powered down"? How much time
> does it take for the battery to drain now?
By powered down, the bug reporter is saying physically powered off and
unplugged. The system is a HP laptop:
dmi.chassis.vendor: HP
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Notebook
vendor_id : GenuineIntel
cpu family : 6
>
>> The bisect actually pointed to commit de3ef1e, but reverting
>> these two commits fixes the issue.
>>
>> I was hoping to get your feedback, since you are the patch author. Do
>> you think gathering any additional data will help diagnose this issue,
>> or would it be best to submit a revert request?
> First, reverting these is not an option or you will break systems
> relying on them now. 4.13 is three releases back at this point.
>
> Second, your issue appears to be related to the suspend/shutdown path
> whereas commit 0ce3fcaff929 is mostly about resume, so presumably the
> change in pci_enable_wake() causes the problem to happen. Can you try
> to revert this one alone and see if that helps?
A test kernel with commits 0ce3fcaff929 and de3ef1eb1cd0 reverted was
tested. However, the test kernel still exhibited the bug.
next prev parent reply other threads:[~2018-04-16 15:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 17:56 Joseph Salisbury
2018-04-13 21:34 ` Rafael J. Wysocki
2018-04-16 15:31 ` Joseph Salisbury [this message]
2018-04-16 15:58 ` Rafael J. Wysocki
2018-04-16 16:48 ` Joseph Salisbury
2018-04-30 14:22 ` Joseph Salisbury
2018-05-01 8:34 ` Rafael J. Wysocki
2018-05-01 19:55 ` Bjorn Helgaas
2018-05-02 8:21 ` Rafael J. Wysocki
2018-05-02 10:41 ` Rafael J. Wysocki
2018-05-02 11:12 ` Joseph Salisbury
2018-05-03 18:29 ` Joseph Salisbury
2018-05-03 19:11 ` Bjorn Helgaas
2018-05-03 21:29 ` Rafael J. Wysocki
2018-05-04 11:14 ` Rafael J. Wysocki
2018-05-07 16:15 ` Joseph Salisbury
2018-05-08 22:13 ` Rafael J. Wysocki
2018-05-08 22:18 ` [PATCH] PCI / PM: Check device_may_wakeup() in pci_enable_wake() Rafael J. Wysocki
2018-05-09 22:34 ` Rafael J. Wysocki
2018-05-10 13:03 ` Bjorn Helgaas
2018-05-10 14:49 ` Rafael J. Wysocki
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=ae84e595-dede-1409-4aff-3a29a310f2ba@canonical.com \
--to=joseph.salisbury@canonical.com \
--cc=1745646@bugs.launchpad.net \
--cc=bhelgaas@google.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/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
all inboxes | Powered by JetHome®