Bug 228654 - ACPI suspend S3 with bounce kills USB; ACPI suspend S3 kills screen and leaves the system in a broken state
Summary: ACPI suspend S3 with bounce kills USB; ACPI suspend S3 kills screen and leave...
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-acpi mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-31 21:30 UTC by Yuri Victorovich
Modified: 2018-07-11 08:37 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yuri Victorovich freebsd_committer 2018-05-31 21:30:54 UTC
Version:
> FreeBSD xxx 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r334417M: Thu May 31 07:47:47 PDT 2018     unknown@nohost.com:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64

Commands (from https://www.freebsd.org/doc/handbook/acpi-overview.html):
> # sysctl debug.bootverbose=1
> # sysctl debug.acpi.suspend_bounce=1
> # acpiconf -s 3
cause USB to be deactivated with these messages:
> May 31 14:09:12 xxx acpi[1801]: resumed at 20180531 14:09:12
> May 31 14:09:12 xxx kernel: uhub2: 4 ports with 4 removable, self powered
> May 31 14:09:12 xxx kernel: random: harvesting attach, 8 bytes (4 bits) from uhub2
> May 31 14:09:13 xxx kernel: uhub_reattach_port: giving up port reset - device vanished

Symptoms:
USB mouse doesn't come back from the simulated suspend. Unplugging/replugging the mouse doesn't bring it back either. Only reboot helps.

USB is identified as:
> May 31 14:17:27 xxx kernel: ugen1.1: <AMD EHCI root HUB> at usbus1
> May 31 14:17:27 xxx kernel: ugen0.1: <0x1022 XHCI root HUB> at usbus0
> May 31 14:17:27 xxx kernel: uhub0: <AMD EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
> May 31 14:17:27 xxx kernel: uhub1: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
Comment 1 Yuri Victorovich freebsd_committer 2018-06-03 19:41:28 UTC
Also
> # acpiconf -s 3
does put it to sleep, but when the system wakes up the screen is black, and memory can't be allocated:
> # top
> top: sysctlbyname kern.cp_times: Cannot allocate memory
Comment 2 Yuri Victorovich freebsd_committer 2018-06-03 19:44:39 UTC
Hardware: Lenovo laptop IdeaPad 320.