From: Leho Kraav <leho@kraav.com>
To: linux-usb@vger.kernel.org
Subject: 5.3.0-rc6: DELL Latitude 7400 2-in-1 (Whiskey Lake) unable to `s2idle`, XHC causes wakeups
Date: Tue, 27 Aug 2019 11:34:35 +0300 [thread overview]
Message-ID: <20190827083435.GD4124@papaya> (raw)
Hi all
[ 0.000000] DMI: Dell Inc. Latitude 7400 2-in-1/0HCNR3, BIOS 1.4.0 06/10/2019
[ 0.225802] smpboot: CPU0: Intel(R) Core(TM) i5-8365U CPU @ 1.60GHz (family: 0x6, model: 0x8e, stepping: 0xc)
For some reason this machine out of the box can't suspend on latest Linux, because XHC wakeups.
Only `echo XHC | sudo tee /proc/acpi/wakeup` helps.
No external USB devices are connected.
How do I diagnose which internal devices is causing the wakeup? Search
engines are only displaying results for people bluntly disabling this
wakeup source, but information on how to find out details is hard to come by.
I did not need to disable anything on my previous DELL Latitude 7480, so curious.
```
aug 25 17:24:34 papaya kernel: PM: suspend entry (s2idle)
aug 25 17:24:35 papaya kernel: Filesystems sync: 0.010 seconds
aug 25 17:24:35 papaya kernel: Freezing user space processes ... (elapsed 0.192 seconds) done.
aug 25 17:24:35 papaya kernel: OOM killer disabled.
aug 25 17:24:35 papaya kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
aug 25 17:24:35 papaya kernel: printk: Suspending console(s) (use no_console_suspend to debug)
aug 25 17:24:35 papaya kernel: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x20 returns -16
aug 25 17:24:35 papaya kernel: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1b0 returns -16
aug 25 17:24:35 papaya kernel: PM: Device 0000:00:14.0 failed to suspend async: error -16
aug 25 17:24:35 papaya kernel: PM: Some devices failed to suspend, or early wake event detected
aug 25 17:24:35 papaya kernel: OOM killer enabled.
aug 25 17:24:35 papaya wpa_supplicant[1104]: wlo1: Reject scan trigger since one is already pending
aug 25 17:24:35 papaya wpa_supplicant[1104]: wlo1: Failed to initiate AP scan
aug 25 17:24:35 papaya wpa_supplicant[1104]: wlo1: SME: Trying to authenticate with a4:2b:b0:f8:27:f5 (SSID='s62-xt-1' freq=2462 MHz)
aug 25 17:24:35 papaya kernel: Restarting tasks ... done.
aug 25 17:24:35 papaya kernel: wlo1: authenticate with a4:2b:b0:f8:27:f5
aug 25 17:24:35 papaya kernel: nvme nvme0: 4/0/0 default/read/poll queues
aug 25 17:24:35 papaya kernel: wlo1: send auth to a4:2b:b0:f8:27:f5 (try 1/3)
aug 25 17:24:35 papaya wpa_supplicant[1104]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD
aug 25 17:24:35 papaya kernel: wlo1: authenticated
aug 25 17:24:35 papaya wpa_supplicant[1104]: wlo1: Trying to associate with a4:2b:b0:f8:27:f5 (SSID='s62-xt-1' freq=2462 MHz)
aug 25 17:24:35 papaya kernel: wlo1: associate with a4:2b:b0:f8:27:f5 (try 1/3)
aug 25 17:24:35 papaya kernel: wlo1: RX AssocResp from a4:2b:b0:f8:27:f5 (capab=0x431 status=0 aid=2)
aug 25 17:24:35 papaya kernel: PM: suspend exit
```
Device 0000:00:14.0 is `00:14.0 USB controller: Intel Corporation Device 9ded (rev 30)`,
no surprise there.
--
Leho Kraav, senior technology & digital marketing architect
reply other threads:[~2019-08-27 8:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190827083435.GD4124@papaya \
--to=leho@kraav.com \
--cc=linux-usb@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).