On Fri, Feb 23, 2018 at 08:00:50AM +0100, Greg KH wrote: > On Thu, Feb 22, 2018 at 11:26:37PM +0000, De La Torre Mena, ElizabethX wrote: > > According to https://bugzilla.kernel.org/show_bug.cgi?id=198893#c1, I'm sending this to report the following bug: > > > > It happens easily if I ran the test, that sends the machine to S3 and autoresume, twice giving back an rtcwake error. I'm attaching the dmesg with latest drm-tip. > > Kernel 4.16.0-rc1-commit-67f1480+ > > > > From Bugzilla: > > > > I'm opening this case to follow up the issue on https://bugs.freedesktop.org/show_bug.cgi?id=105130. > > Machine is an IVB. > > > Test outputs: > > > > > > igt@gem_exec_suspend@basic-s3: > > > [...] > > > Subtest basic-S3: FAIL (1.372s) > > > [...] > > > (gem_exec_suspend:12804) igt-core-INFO: [cmd] rtcwake: wakeup from "mem" > > > using /dev/rtc0 at Thu Jan 25 06:10:24 2018 > > > (gem_exec_suspend:12804) igt-core-WARNING: [cmd] rtcwake: write error > > > (gem_exec_suspend:12804) igt-aux-WARNING: rtcwake failed with 1 > > > Check dmesg for further details. > > > (gem_exec_suspend:12804) igt-aux-DEBUG: suspend_stats: > > > success: 0 > > > fail: 1 > > > failed_freeze: 0 > > > failed_prepare: 0 > > > failed_suspend: 1 > > > failed_suspend_late: 0 > > > failed_suspend_noirq: 0 > > > failed_resume: 0 > > > failed_resume_early: 0 > > > failed_resume_noirq: 0 > > > failures: > > > last_failed_dev: 0000:00:1d.0 > > > > > > last_failed_errno: -16 > > > 0 > > > last_failed_step: suspend > > > > > > > > based on the above: > > > > $ lspci -s 0000:00:1d.0 > > > > 00:1d.0 USB controller > > > > from dmesg: > > > > [ 133.856853] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 > > [ 133.856863] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -16 > > [ 133.856873] PM: Device 0000:00:1d.0 failed to suspend async: error -16 > > [ 133.957621] hp_wmi: Unknown event_id - 14 - 0x0 > > [ 134.341326] PM: Some devices failed to suspend, or early wake event detected > > > > How is this a USB bug? Shouldn't this be a power management / PCI > issue? That was my suggestion looking at the last_failed_dev above and in dmesg hcd_pci_suspend() failing. Looking more it looks like suspend_common() in drivers/usb/core/hcd-pci.c returns -EBUSY because a pending root-hub wakeup event. Not sure what that means. Do you mean that USB PM issues should always be filed as PM/PCI bugs? --Imre > > confused, > > greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
