Date: Thu, 27 Sep 2018 12:53:21 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: Petr Fischer <petr.fischer@me.com> Cc: "freebsd-acpi@freebsd.org" <freebsd-acpi@freebsd.org> Subject: Re: suspend to RAM stopped working on 11.2 (11.1 was OK) Message-ID: <CAN6yY1tOebi%2BrPSX15%2BFwxhq7B3pPjnCxgrwQFDwmVf1h-VB6g@mail.gmail.com> In-Reply-To: <20180927175917.7iea6w4ckyngrpto@pf-bsd> References: <20180927175917.7iea6w4ckyngrpto@pf-bsd>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 27, 2018 at 10:59 AM Petr Fischer via freebsd-acpi < freebsd-acpi@freebsd.org> wrote: > Hello, suspend to RAM stopped working on my laptop on 11.2 (11.1 was OK) > > freebsd: 11.2-RELEASE-p3 > hardware: Toshiba Portege Z30 - Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz > > tried with i915kms from FreeBSD base (default) and also with > drm-next-kmod-4.11.g20180822 > (drm-stable-kmod-g20180822 freezes graphics 1 second after load) > > tried with hw.acpi.reset_video=0 and also with hw.acpi.reset_video=1 > > Is there someone who can help me with debug this problem? > I can compile something and test when you say. > > Thanks very much! Petr Fischer > > > /var/log/messages after acpiconf -s 3 command: > --------------------- > Sep 27 19:49:40 pf-bsd acpi: suspend at 20180927 19:49:40 > Sep 27 19:49:54 pf-bsd kernel: Power well on > Sep 27 19:49:54 pf-bsd kernel: vgapci0: child drmn0 requested > pci_set_powerstate > Sep 27 19:49:54 pf-bsd kernel: pci0: failed to set ACPI power state D3 on > \_SB_.PCI0.GFX0: AE_BAD_PARAMETER > Sep 27 19:49:54 pf-bsd kernel: hdac0: Command timeout on address 0 > Sep 27 19:49:54 pf-bsd kernel: uhub0: at usbus0, port 1, addr 1 > (disconnected) > Sep 27 19:49:54 pf-bsd kernel: ugen0.2: <vendor 0x0458 product 0x0154> at > usbus0 (disconnected) > Sep 27 19:49:54 pf-bsd kernel: ums0: at uhub0, port 5, addr 1 > (disconnected) > Sep 27 19:49:54 pf-bsd kernel: ums0: detached > Sep 27 19:49:54 pf-bsd kernel: uhid0: at uhub0, port 5, addr 1 > (disconnected) > Sep 27 19:49:54 pf-bsd kernel: uhid0: detached > Sep 27 19:49:54 pf-bsd kernel: ugen0.3: <vendor 0x05e3 USB2.0 Hub> at > usbus0 (disconnected) > Sep 27 19:49:54 pf-bsd kernel: uhub3: at uhub0, port 6, addr 2 > (disconnected) > Sep 27 19:49:54 pf-bsd kernel: ugen0.4: <vendor 0x0b97 product 0x7761> at > usbus0 (disconnected) > Sep 27 19:49:54 pf-bsd kernel: uhub4: at uhub3, port 3, addr 3 > (disconnected) > Sep 27 19:49:54 pf-bsd kernel: ugen0.5: <O2 O2Micro CCID SC Reader> at > usbus0 (disconnected) > Sep 27 19:49:54 pf-bsd kernel: uhub4: detached > Sep 27 19:49:54 pf-bsd kernel: uhub3: detached > Sep 27 19:49:54 pf-bsd kernel: wlan0: link state changed to DOWN > Sep 27 19:49:54 pf-bsd kernel: uhub1: at usbus1, port 1, addr 1 > (disconnected) > Sep 27 19:49:54 pf-bsd kernel: ugen1.2: <vendor 0x8087 product 0x8000> at > usbus1 (disconnected) > Sep 27 19:49:54 pf-bsd kernel: uhub2: at uhub1, port 1, addr 2 > (disconnected) > Sep 27 19:49:54 pf-bsd kernel: uhub2: detached > Sep 27 19:49:54 pf-bsd kernel: pcib0: failed to set ACPI power state D2 on > \_SB_.PCI0: AE_BAD_PARAMETER > Sep 27 19:49:54 pf-bsd kernel: acpi0: cleared fixed power button status > Sep 27 19:49:54 pf-bsd kernel: vgapci0: child drmn0 requested > pci_set_powerstate > Sep 27 19:49:54 pf-bsd kernel: vgapci0: child drmn0 requested pci_enable_io > Sep 27 19:49:54 pf-bsd kernel: vgapci0: child drmn0 requested pci_enable_io > Sep 27 19:49:54 pf-bsd kernel: hdac0: Device stuck in reset > Sep 27 19:49:54 pf-bsd kernel: hdac0: Command timeout on address 0 > Sep 27 19:49:54 pf-bsd last message repeated 21 times > Sep 27 19:49:54 pf-bsd kernel: xhci0: Port routing mask set to 0xffffffff > Sep 27 19:49:54 pf-bsd kernel: uhub0: <0x8086 XHCI root HUB, class 9/0, > rev 3.00/1.00, addr 1> on usbus0 > Sep 27 19:49:54 pf-bsd kernel: uhub1: <Intel EHCI root HUB, class 9/0, rev > 2.00/1.00, addr 1> on usbus1 > Sep 27 19:49:54 pf-bsd wpa_supplicant[58136]: wlan0: > CTRL-EVENT-DISCONNECTED bssid=f0:79:59:d2:7a:00 reason=0 > Sep 27 19:49:54 pf-bsd wpa_supplicant[58136]: ioctl[SIOCS80211, op=20, > val=0, arg_len=7]: Can't assign requested address > Sep 27 19:49:54 pf-bsd acpi: resumed at 20180927 19:49:54 > Sep 27 19:49:55 pf-bsd kernel: uhub0: 13 ports with 13 removable, self > powered > Sep 27 19:49:55 pf-bsd kernel: uhub1: 2 ports with 2 removable, self > powered > Sep 27 19:49:56 pf-bsd kernel: ugen0.2: <vendor 0x0458 product 0x0154> at > usbus0 > Sep 27 19:49:56 pf-bsd kernel: ums0 on uhub0 > Sep 27 19:49:56 pf-bsd kernel: ums0: <vendor 0x0458 product 0x0154, class > 0/0, rev 1.10/33.52, addr 1> on usbus0 > Sep 27 19:49:56 pf-bsd kernel: ums0: 5 buttons and [XYZT] coordinates ID=1 > Sep 27 19:49:56 pf-bsd kernel: uhid0 on uhub0 > Sep 27 19:49:56 pf-bsd kernel: uhid0: <vendor 0x0458 product 0x0154, class > 0/0, rev 1.10/33.52, addr 1> on usbus0 > Sep 27 19:49:56 pf-bsd kernel: ugen1.2: <vendor 0x8087 product 0x8000> at > usbus1 > Sep 27 19:49:56 pf-bsd kernel: uhub2 on uhub1 > Sep 27 19:49:56 pf-bsd kernel: uhub2: <vendor 0x8087 product 0x8000, class > 9/0, rev 2.00/0.04, addr 2> on usbus1 > Sep 27 19:49:56 pf-bsd kernel: ugen0.3: <vendor 0x05e3 USB2.0 Hub> at > usbus0 > Sep 27 19:49:56 pf-bsd kernel: uhub3 on uhub0 > Sep 27 19:49:56 pf-bsd kernel: uhub3: <vendor 0x05e3 USB2.0 Hub, class > 9/0, rev 2.00/85.37, addr 2> on usbus0 > Sep 27 19:49:56 pf-bsd kernel: uhub2: 8 ports with 8 removable, self > powered > Sep 27 19:49:57 pf-bsd kernel: uhub3: 3 ports with 0 removable, self > powered > Sep 27 19:49:57 pf-bsd kernel: ugen0.4: <vendor 0x0b97 product 0x7761> at > usbus0 > Sep 27 19:49:58 pf-bsd kernel: uhub4 on uhub3 > Sep 27 19:49:58 pf-bsd kernel: uhub4: <vendor 0x0b97 product 0x7761, class > 9/0, rev 1.10/1.10, addr 3> on usbus0 > Sep 27 19:49:58 pf-bsd kernel: uhub4: 4 ports with 3 removable, self > powered > Sep 27 19:49:59 pf-bsd kernel: ugen0.5: <O2 O2Micro CCID SC Reader> at > usbus0 > Sep 27 19:49:59 pf-bsd root: Unknown USB device: vendor 0x0b97 product > 0x7772 bus uhub4 > Sep 27 19:50:02 pf-bsd wpa_supplicant[58136]: wlan0: Trying to associate > with f0:79:59:d2:7a:00 (SSID='pf's Network' freq=2427 MHz) > Sep 27 19:50:02 pf-bsd wpa_supplicant[58136]: wlan0: Associated with > f0:79:59:d2:7a:00 > Sep 27 19:50:02 pf-bsd kernel: wlan0: link state changed to UP > > From the log, it appears that the system sis resume. The network reports that wlan0 is UP an hte wpa_supplicant reports success. I suspect that you system is up, but that the display is hung. Near the top I see "vgapci0: child drmn0 requested pci_set_powerstate" followed by "pci0: failed to set ACPI power state D3 on \_SB_.PCI0.GFX0: AE_BAD_PARAMETER". It looks like this is a failure to properly wake the graphics processor. (The sound system also appears to fail.) This well out of my area of expertise, so I hope someone more clueful about GPU/ACPI interaction might help. You should be able to ssh into the system to confirm that it is up. You might be able to log in blind from the keyboard as well, but that would be a bit less useful. At least you should log in and so a clean shutdown. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1tOebi%2BrPSX15%2BFwxhq7B3pPjnCxgrwQFDwmVf1h-VB6g>