From owner-freebsd-acpi@freebsd.org Fri Oct 16 14:09:15 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 63B67A169F6 for ; Fri, 16 Oct 2015 14:09:15 +0000 (UTC) (envelope-from accountlostin@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ECA3C197C for ; Fri, 16 Oct 2015 14:09:14 +0000 (UTC) (envelope-from accountlostin@gmx.com) Received: from [151.66.207.26] by 3capp-mailcom-bs16.server.lan (via HTTP); Fri, 16 Oct 2015 16:09:07 +0200 MIME-Version: 1.0 Message-ID: From: "account lost" To: freebsd-acpi@freebsd.org Subject: suspend broken when disconnecting an usb audio device Content-Type: text/plain; charset=UTF-8 Date: Fri, 16 Oct 2015 16:09:07 +0200 Importance: normal Sensitivity: Normal X-Priority: 3 X-Provags-ID: V03:K0:a8+85RNQRaV6yCMWGwm+GB9+BdfzIbPTml0MVnxiAK5 xaMZc2FT4j43TuT8vjarBP7/ElaUevsW1ke4bdTz9cHlZhSE0G y5WbO9MOGCwvs6xvliTX3pePVAH5RZtI1O89qRNr3XLANI54kF efCWKaT+EXzplVIUmqqXDGUr31BknceX5Bx+shbDPbyiHNo2Sk zjtcPOUTwRQVgh4mvDFnDTh0apTRW0F4hhhH4vrO/ncI5q4FfZ coUVx2C1LQIvCwo0A1UWDqAZbWCDYCF+OGZe9+wATUMq0rOpIs Zwjrg5lz2cXhlfsbQCGEyqrqtV7 X-UI-Out-Filterresults: notjunk:1;V01:K0:WCAL+U9ut8E=:lVHw6oeqy/ARGg98tKmWhR eZWyhwQyYDcZ2H6I0HUBcvRYwlYS5Pe5o6pJOXJDRerdHMBt8itv5+mQTrSEPr96fVRfj1rxa lrzATYJjwiMBbOu0qqCNAfWhHg3ItDcw7wvUXcwOR6iDZea5gCIBXwU4/PGP2D3jGE6rSICte joB/HUFcnWyUsOnwXSNj0beHs0kuc6H8AGZn0xMTOIbb6Y7NTyy/sI6HRf8OdeP7MtsNk24/x UJ7Lvt7IZ4zmxoE6ftXpHD7rdZ+vUrs/LcV0XpdHaNUNdXLM4xwaICSkw9siKSpgs8L9a4h4i FrGqTRAkONzzwI0cySu4in2KpwV/+vE7xWbxmFJ2xEjkEfF/3M6NUlSELmF3dXkDcY86t7cVZ gIIqQPzPMqxsZd96/EhBiuGVFYpNrjJoQwCD84x1AuPh+bL8+yiHz/hrtSag/9MleNDV1wMue vwaL2E2mfA== 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: Fri, 16 Oct 2015 14:09:15 -0000 Hi, I'm using FreeBSD 10.2-RELEASE-p5 amd64 on a thinkpad t430. I have suspend and resume functionality working by using newcons and i915kms.ko as the video driver, but whenever I plug in and use my usb DAC, either by choosing it in applications supporting OSS or by setting it as the hw.snd.default_unit and then disconnect it without terminating the audio applications, I can't enter acpi s3. When trying to suspend the system I get repeated messages on the console: "Waiting for sound application to exit!" (as documented here: http://baitisj.blogspot.it/2015/05/usb-audio-disconnect-woes-in-freebsd.html) but I can't react by killing the incriminated pid since ttys are already unavailable, and I'm forced to perform an hard reset From owner-freebsd-acpi@freebsd.org Fri Oct 16 14:26:42 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 21D66A16F5B for ; Fri, 16 Oct 2015 14:26:42 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D849CA25 for ; Fri, 16 Oct 2015 14:26:41 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id AC08C1FE022; Fri, 16 Oct 2015 16:26:32 +0200 (CEST) Subject: Re: suspend broken when disconnecting an usb audio device To: account lost , freebsd-acpi@freebsd.org References: From: Hans Petter Selasky Message-ID: <5621097F.20705@selasky.org> Date: Fri, 16 Oct 2015 16:28:15 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; 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: Fri, 16 Oct 2015 14:26:42 -0000 On 10/16/15 16:09, account lost wrote: > Hi, I'm using FreeBSD 10.2-RELEASE-p5 amd64 on a thinkpad t430. > > I have suspend and resume functionality working by using newcons and i915kms.ko as the video driver, but whenever I plug in and use my usb DAC, either by choosing it in applications supporting OSS or by setting it as the hw.snd.default_unit and then disconnect it without terminating the audio applications, I can't enter acpi s3. > > When trying to suspend the system I get repeated messages on the console: "Waiting for sound application to exit!" (as documented here: http://baitisj.blogspot.it/2015/05/usb-audio-disconnect-woes-in-freebsd.html) but I can't react by killing the incriminated pid since ttys are already unavailable, and I'm forced to perform an hard reset Hi, There is a bug in pulseaudio or some mixer application, that it doesn't close the /dev/mixer or /dev/dsp, when receiving a read/write error from the USB audio device. Try killing pulseaudio. --HPS From owner-freebsd-acpi@freebsd.org Fri Oct 16 14:29:02 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 3FD3FA16FBA for ; Fri, 16 Oct 2015 14:29:02 +0000 (UTC) (envelope-from accountlostin@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CCBE3A86 for ; Fri, 16 Oct 2015 14:29:01 +0000 (UTC) (envelope-from accountlostin@gmx.com) Received: from [151.66.207.26] by 3capp-mailcom-bs08.server.lan (via HTTP); Fri, 16 Oct 2015 16:28:53 +0200 MIME-Version: 1.0 Message-ID: From: "account lost" To: freebsd-acpi@freebsd.org Subject: suspend broken when disconnecting an usb audio device Content-Type: text/plain; charset=UTF-8 Date: Fri, 16 Oct 2015 16:28:53 +0200 Importance: normal Sensitivity: Normal X-Priority: 3 X-Provags-ID: V03:K0:DW+R3qCsF0xABUWYP00djoBNKgPoh+xn2aEukVL897b 7qu2FQAFSDEWfrkLboHaMkGMAVpASb0EAMpv9zcpw2/Z1icuA+ SeeoB5AvAE1AEUIje17zTZ9OYIx7xk6xA507kgGyjlIb9cr00a mcHYM74fwt/c8MF8iJWNTDufpShAh53Ba78oIgsJqqsh27I6XG IAF8FIK/jI9a2bnRM84GE84V2zLqmOJLFz7kuE0AX4DnLKR/da biUG8zwCG5n+EvQUWFkJQL3CSH2u2VIz70u8cBDiGgL/aJetZt dDK7NvOaSouTQyCDt2RLlKe4q76 X-UI-Out-Filterresults: notjunk:1;V01:K0:cY32YhJrNKY=:7DKNnamQzZEV2KSfoEZnwq /bsEiE7PXu4Ib1sGwGiXyk5dBsJnAssgVYu0KSzm+vpY9ofoQX4UWeX2bBDJR+rr2a7xSPePf W/YD3rMn4/9u1KIEwsNBS7wbjDYck8oFokuoOSbnKwdS/nWn+zfLAvNvN4jJ5scc6dECfnEZL DscEH6YHNwZrxrtcmGFYkD7ljG1MZob/3/wj75d6GIS2L09pVuB6h+ac8x3GempExiMPyDps1 WpUgph8Q8aulEAarsflVjrUhfhXGLGKHGQQsRQO/7uY3bdvvBnta0lwNK8X6ZW7dzHXerh7hs U34JT0RmOUqExLr2F9J4B/GjQ7q1ryDRN2siVR//LRHJUHjIK8+1U2wNrFCrPsU4SXl3YRUmM /zismDyH9NT68AXoR21WGxCfM+G2tmNidBjLxM/UVy9TUhUJ14JR3Wa+Vu2/WSDVa2nz1r/hU 77O2Dr9Mfg== 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: Fri, 16 Oct 2015 14:29:02 -0000 Sorry about the mailing list chaos I'm creating, I hadn't subscribed and can't yet recover the message id to correctly reply to my previous message. I reproduced the problem again in order to transcribe the accurate error message I'm getting, and noticed that this happens by simply plugging the usb sound card, even without setting it as the default hw.snd.default_unit and without opening any sound application at all. In this case, instead of reading about which PID is still using the device, I get an error regarding the in kernel oss mixer PCM5: Waiting for sound application to exit! PCM5: unregister: mixer busy From owner-freebsd-acpi@freebsd.org Fri Oct 16 23:10:57 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 285DEA16D4E for ; Fri, 16 Oct 2015 23:10:57 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DE63B966 for ; Fri, 16 Oct 2015 23:10:56 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by obcqt19 with SMTP id qt19so24121581obc.3 for ; Fri, 16 Oct 2015 16:10:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=5tQhdRmMiWE/7GXKdYGiH+qlSnfWlJekRd3+ypP5TOc=; b=qUO8XuNRO3DZEH2V4R5rT8rvRqOsp6cId3qeX/rbTzRD9G9D/FIVnL4OXQSTFTmbBb UF7dYbzfBKbQQK4y5LpRbYPg9xqCydAA4CRh7ZtcraKIDVAdlcZ3aypFO+fzrhyMEaFp xhfvpTt1VS9GKuNZCNdnp6QeAFjkWqEvCHU2lwITmmqwszhmGn91kpF/AYl/aeOheYdF Fmbv7J7LG8fWmMSXK/nEBdlBfnqyAYgyPaiX8z8aXVWzJpCss33KJ7G3cyFmuzArAZ+d OVjCz0zvCGbeMUdy0Qu2bXwXwQcjvqKRrLAZOK2MWvdHG2hvjA/3DLcZZ4Kv2V2lm4TE KnMg== MIME-Version: 1.0 X-Received: by 10.60.118.40 with SMTP id kj8mr11255393oeb.5.1445037056142; Fri, 16 Oct 2015 16:10:56 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.202.50.136 with HTTP; Fri, 16 Oct 2015 16:10:56 -0700 (PDT) In-Reply-To: <5621097F.20705@selasky.org> References: <5621097F.20705@selasky.org> Date: Fri, 16 Oct 2015 16:10:56 -0700 X-Google-Sender-Auth: RIYntph3hoz-epVO_lzb10QCMpU Message-ID: Subject: Re: suspend broken when disconnecting an usb audio device From: Kevin Oberman To: Hans Petter Selasky Cc: account lost , "freebsd-acpi@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 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: Fri, 16 Oct 2015 23:10:57 -0000 On Fri, Oct 16, 2015 at 7:28 AM, Hans Petter Selasky wrote: > On 10/16/15 16:09, account lost wrote: > >> Hi, I'm using FreeBSD 10.2-RELEASE-p5 amd64 on a thinkpad t430. >> >> I have suspend and resume functionality working by using newcons and >> i915kms.ko as the video driver, but whenever I plug in and use my usb DAC, >> either by choosing it in applications supporting OSS or by setting it as >> the hw.snd.default_unit and then disconnect it without terminating the >> audio applications, I can't enter acpi s3. >> >> When trying to suspend the system I get repeated messages on the console: >> "Waiting for sound application to exit!" (as documented here: >> http://baitisj.blogspot.it/2015/05/usb-audio-disconnect-woes-in-freebsd.html) >> but I can't react by killing the incriminated pid since ttys are already >> unavailable, and I'm forced to perform an hard reset >> > > Hi, > > There is a bug in pulseaudio or some mixer application, that it doesn't > close the /dev/mixer or /dev/dsp, when receiving a read/write error from > the USB audio device. > > Try killing pulseaudio. > > --HPS You might also try lsof(8) or fstat(1) to confirm what is holding it open. (I really wish I could avoid using pulseaudio at all. It's a giant pain in the rear and pretty useless, but my MATE desktop insists.) I'd be curious if both fstat and lsof work. Of late I have not had success with fstat on a hung device, but lsof works fine. I realy need to try to track the fstat ossue down and, if it's not cockpit error, open a bug report.) -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 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? From owner-freebsd-acpi@freebsd.org Sat Oct 17 15:14:49 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 8F47EA17BB7 for ; Sat, 17 Oct 2015 15:14:49 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 7D33A263; Sat, 17 Oct 2015 15:14:49 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 0AF371BF4; Sat, 17 Oct 2015 15:14:48 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Sat, 17 Oct 2015 15:14:47 +0000 From: Glen Barber To: Eric McCorkle Cc: "freebsd-acpi@freebsd.org" Subject: Re: Old suspend/resume issue likely root cause Message-ID: <20151017151447.GH15305@FreeBSD.org> References: <5622648F.2090509@metricspace.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="YrQNB5Deg1WGKZi3" Content-Disposition: inline In-Reply-To: <5622648F.2090509@metricspace.net> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.24 (2015-08-30) 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:14:49 -0000 --YrQNB5Deg1WGKZi3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Oct 17, 2015 at 11:09:03AM -0400, Eric McCorkle wrote: > 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=3D0. >=20 > I got tangled up with other projects and had to set it aside. However, I > now finally have more information: >=20 >=20 > * hw.pci.power_suspend=3D0 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. >=20 > * Without hw.pci.power_suspend=3D0, the issue persists even when booting = =66rom > EFI, so we can rule out some kind of legacy BIOS issue. The issue manife= sts > even with the experimental i915 driver, so we can rule out something with > the efifb or VGA framebuffer drivers. >=20 >=20 > Based on this, it looks pretty likely that the pci bus is the culprit. Any > suggestions on where to look? What graphics chipset do you have? I noticed with dumbbell's i915kms update branch [1], suspend/resume now works for me with Haswell graphics, whereas previously I would experience the same blank screen on resume you report. (And I also see the iwm(4) reinitialization issue, as well.) [1] https://github.com/freebsd/freebsd-base-graphics.git branch drm-i915-update-38 Glen --YrQNB5Deg1WGKZi3 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWImXnAAoJEAMUWKVHj+KTpYYQAIU4gE1FWA+MWbVQ2EB6+xDR H9zZQX5D+tMIbCsVCdB5lapVCO3r9dk93TfwKfP9wVhYfdTL0dbtc6mHvrzXhM2l QRJGAPgm9qPBWa4H1MPMH4N/e7H31276+GgBTux+AZfqzMy8+LEp9VyxJ6l4QtxL bK9LbaxqROlaNmG2ZX2mzk/kBLBdBe8huB7BHnhqkf1XN94Bq18z4d+Jw7WL8CFG NnAaQ3sRilHU7/PsEyAHRNC5B9sxP64y3nrnli7jgLAU00CfKXCxaSnTuE3dYWGS vzntS/WaJsecQ/q7bepotxsdqEprSVZiMMCfFdv5yWad5qHZbDtfAVIFJ9iFGW0u XU5yQd+rPp6JjS/Qs/FMuJPkwRYuCHAX4O7IivA4BMUQYnXmYCFGAgZZJqME5u+1 SJ9H7yG68IIhF8SClBIyKGwDjE9KiDwNcf7gVTJi3vhd9+mF2NSLU/8ahR0QLpKc +Z+kZRBXTOnR26J0cuUS/o7sNavMrD5OWozRtqC+gfv4++R4mpY3NrfSrHehoFuj c7mxG5b+z9o9ESuhim+Q245QUbbJm8nRZ2oJXbEbuiKkKvU0bGB5ljAFiVRNhNK0 hZ7SIgYx6B0THAES6BpqJfxtu1A3n4J9rNzicAxbvUK2DxUlE96/63nvVW78/NHO eg9hcjONmJEAGL/TkZkY =f0BQ -----END PGP SIGNATURE----- --YrQNB5Deg1WGKZi3-- From owner-freebsd-acpi@freebsd.org Sat Oct 17 15:57:07 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 4B220A17838 for ; Sat, 17 Oct 2015 15:57:07 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::107]) by mx1.freebsd.org (Postfix) with ESMTP id 2389A1505; Sat, 17 Oct 2015 15:57:07 +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 69F661DFE; Sat, 17 Oct 2015 15:57:06 +0000 (UTC) Subject: Re: Old suspend/resume issue likely root cause To: Glen Barber References: <5622648F.2090509@metricspace.net> <20151017151447.GH15305@FreeBSD.org> Cc: "freebsd-acpi@freebsd.org" From: Eric McCorkle Message-ID: <56226FD1.4070806@metricspace.net> Date: Sat, 17 Oct 2015 11:57:05 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <20151017151447.GH15305@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; 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:57:07 -0000 On 10/17/15 11:14, Glen Barber wrote: > On Sat, Oct 17, 2015 at 11:09:03AM -0400, Eric McCorkle wrote: >> 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? > > What graphics chipset do you have? I noticed with dumbbell's i915kms > update branch [1], suspend/resume now works for me with Haswell > graphics, whereas previously I would experience the same blank screen on > resume you report. Intel i7-4700. I tried suspend with the i915kms driver active, hoping that would do the trick, but it didn't work. > (And I also see the iwm(4) reinitialization issue, as well.) The workaround there is just to take netif, wpa_supplicant, dhclient, and rtsold down in rc.suspend and bring them back up in rc.resume. > [1] https://github.com/freebsd/freebsd-base-graphics.git branch > drm-i915-update-38 > > Glen > From owner-freebsd-acpi@freebsd.org Sat Oct 17 16:00:46 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 EE628A179C1 for ; Sat, 17 Oct 2015 16:00:45 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id D385218D8; Sat, 17 Oct 2015 16:00:45 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 682E01323; Sat, 17 Oct 2015 16:00:45 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Sat, 17 Oct 2015 16:00:43 +0000 From: Glen Barber To: Eric McCorkle Cc: "freebsd-acpi@freebsd.org" Subject: Re: Old suspend/resume issue likely root cause Message-ID: <20151017160043.GJ15305@FreeBSD.org> References: <5622648F.2090509@metricspace.net> <20151017151447.GH15305@FreeBSD.org> <56226FD1.4070806@metricspace.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ucfHZChuBC0NsER/" Content-Disposition: inline In-Reply-To: <56226FD1.4070806@metricspace.net> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.24 (2015-08-30) 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 16:00:46 -0000 --ucfHZChuBC0NsER/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Oct 17, 2015 at 11:57:05AM -0400, Eric McCorkle wrote: > On 10/17/15 11:14, Glen Barber wrote: > >On Sat, Oct 17, 2015 at 11:09:03AM -0400, Eric McCorkle wrote: > >>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 outp= uts > >>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=3D0. > >> > >>I got tangled up with other projects and had to set it aside. However,= I > >>now finally have more information: > >> > >> > >>* hw.pci.power_suspend=3D0 does cause the screen to come back up proper= ly. > >>The network (wireless via iwm driver) needs to be re-initialized, but > >>everything else seems to work properly. > >> > >>* Without hw.pci.power_suspend=3D0, the issue persists even when bootin= g from > >>EFI, so we can rule out some kind of legacy BIOS issue. The issue mani= fests > >>even with the experimental i915 driver, so we can rule out something wi= th > >>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? > > > >What graphics chipset do you have? I noticed with dumbbell's i915kms > >update branch [1], suspend/resume now works for me with Haswell > >graphics, whereas previously I would experience the same blank screen on > >resume you report. >=20 > Intel i7-4700. I tried suspend with the i915kms driver active, hoping th= at > would do the trick, but it didn't work. >=20 I missed in your first email you mentioned the "experimental i915 driver." Is this the driver update from the branch I linked to? >=20 > >(And I also see the iwm(4) reinitialization issue, as well.) >=20 > The workaround there is just to take netif, wpa_supplicant, dhclient, and > rtsold down in rc.suspend and bring them back up in rc.resume. >=20 Yep, that's basically what I did to work around this. > >[1] https://github.com/freebsd/freebsd-base-graphics.git branch > > drm-i915-update-38 > > Glen --ucfHZChuBC0NsER/ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWInCrAAoJEAMUWKVHj+KT9CAP/0zNoqoacutJMblBY2JOH9R3 DuYdHDlBwgC3eX1fI0OSXL8M6fDNu6HDWdhSXPCIZ0W0zsvapEYciVYYYiQudXeT iref1St96pfHrri0dkqzGkc94JWrtJqqbBNfn1qk/yMG8xYiv4OEJl+b2s8E2Dkh rLrJF4CoTrk5j1Ubvho6JmsuaXWIgYObM84tEuuMpNz3upIGJZnw7jAoZy5GgiZt VnsiFtvTbtQ//vDPJ5TfHJFH3duEabS+yiHLCH8NbbHh9YQpFDLQMoFNBPBAqfc2 ITnLEw4NBzRgpmQpPtsaFkvCJ+dO2uAkGvomzPxEZ2yysJblZPnBLOsp+j/BrpTe KUx7qZv4PRMLt4sJKiPfYuZLCzhCnMIAgrNqaEKac7465HYncGIcwdZo5g31d/kk Hv/KDiF9zvXqN2Q8oUCyAjZlc30xDL1iDYCFKAAmS8wu4pD8HLhql8jVnPQy80dH jycWIbJ4heSdSy3PBrWkq7ZDhocKGAbqndBFZ5z7GG83qOO8IMmVPPUtoR7BPHxV V3YCQEj55JDstfbo9ejlRzchXYtX2iB3JHguCgA92OATta+PfhLZGRjioQuEhUzK 6MiSvXWlb7JSjT1FEdrqSTn8N230ZuLUkYbRODhNwDcmZPxgnjKPSVSsPeDBCaHD m0cBQmoEOGkQUGE8RuTW =K2SH -----END PGP SIGNATURE----- --ucfHZChuBC0NsER/--