From owner-freebsd-acpi@freebsd.org Sat Oct 17 15:09:11 2015 Return-Path: Delivered-To: freebsd-acpi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99E98A17943 for ; Sat, 17 Oct 2015 15:09:11 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (207-172-209-83.c3-0.arl-ubr1.sbo-arl.ma.static.cable.rcn.com [207.172.209.83]) by mx1.freebsd.org (Postfix) with ESMTP id 75A221EFE for ; Sat, 17 Oct 2015 15:09:10 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [IPv6:2001:470:1f11:617:ea2a:eaff:fe21:e067] (unknown [IPv6:2001:470:1f11:617:ea2a:eaff:fe21:e067]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id B8B801DF5 for ; Sat, 17 Oct 2015 15:09:03 +0000 (UTC) To: "freebsd-acpi@freebsd.org" From: Eric McCorkle Subject: Old suspend/resume issue likely root cause Message-ID: <5622648F.2090509@metricspace.net> Date: Sat, 17 Oct 2015 11:09:03 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Oct 2015 15:09:11 -0000 A while back (in May or June or so), I was attempting to figure out why my laptop screen stayed blank on suspend/resume. I posted some dmesg outputs and theorized that it might be something about the devices coming back up in the wrong order. John Baldwin suggested I try doing hw.pci.do_power_suspend=0. I got tangled up with other projects and had to set it aside. However, I now finally have more information: * hw.pci.power_suspend=0 does cause the screen to come back up properly. The network (wireless via iwm driver) needs to be re-initialized, but everything else seems to work properly. * Without hw.pci.power_suspend=0, the issue persists even when booting from EFI, so we can rule out some kind of legacy BIOS issue. The issue manifests even with the experimental i915 driver, so we can rule out something with the efifb or VGA framebuffer drivers. Based on this, it looks pretty likely that the pci bus is the culprit. Any suggestions on where to look?