From owner-freebsd-mobile@FreeBSD.ORG Wed May 21 19:16:25 2014 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 566AC4DB; Wed, 21 May 2014 19:16:25 +0000 (UTC) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.187]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA256 (256/256 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DD05E2658; Wed, 21 May 2014 19:16:24 +0000 (UTC) Received: from [192.168.178.36] (p57AEE30E.dip0.t-ipconnect.de [87.174.227.14]) by mrelayeu.kundenserver.de (node=mreue005) with ESMTP (Nemesis) id 0Mgrp6-1WR6jc0V3Q-00M712; Wed, 21 May 2014 21:16:12 +0200 Message-ID: <537CFB7C.60702@janh.de> Date: Wed, 21 May 2014 21:16:12 +0200 From: Jan Henrik Sylvester User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: John Baldwin , Kevin Oberman , Adrian Chadd Subject: Re: Re: Thinkpad T410: resume broken References: <53762216.8020205@gmx.net> <537753F3.6000202@FreeBSD.org> In-Reply-To: <537753F3.6000202@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:6B+o1ch6f0VE3J31YQ3DcGkccwIyP4J+qt7LmRkKRJl UCgzuLVAvlSppZK84/LU7G/FDX8f/7ATce+xaMaw/0lPxiWKFZ 3eTDscRXGyFAZR5wjGvQZ7FcN7wkMLYNHcusLAn6TLLvSHrnLE jV6AIWbp2dZIkBICXkZN/Lrm8RG0aROUTcNo1XShNcLT1fZm24 az4WYv6sML1X3i1ENbnhKrB3TGW4e/TBRprfnRJPM/bpMAjNpW 4p0PvaO0euyyIFUrhEKJc1RHqp5Ry6gvXnAlvrKYq99MoYb/VI 5EUmSlg39mkD1Dh8RtfHdljd5tjd2nXDqfAs5i7FTtvTk71wQ= = Cc: "current@freebsd.org" , Stefan Ehmann , "freebsd-mobile@freebsd.org" X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2014 19:16:25 -0000 On 05/17/2014 14:20, John Baldwin wrote: > On 5/16/14, 2:10 PM, Kevin Oberman wrote: >> On Fri, May 16, 2014 at 10:44 AM, Adrian Chadd wrote: >> >>> Hi! >>> >>> I wonder what changed between 9.2-RELEASE and 10.0-RELEASE. >>> >>> Please poke me about this next week. I'm busy this week with work and >>> maker faire but I will try to help you later. >>> >>> (It's possible something like ACPI updates or a driver update has >>> broken things.) >>> >>> >>> -a >>> >> >> Does your kernel include VESA? My T320 behaved as you describe until I >> removed VESA from my kernel. I think using vt may also fix this without the >> need to remove VESA, bug I have not gotten around to confirming this. > > To be clear, vt does not fix resume. Using i915kms is what actually > fixes resume when using Intel GPUs on the Thinkpad as i915kms is what > actually turns the LCD backlight on during resume. You just have to use > vt to have a useable console when you use i915kms. You can > suspend/resume fine in X with syscons + i915kms, you just can't use your > console if you do. > > If you are using the Nvidia GPU, then i915kms can't help you with > turning the LCD backlight back on (and using vt shouldn't make any > difference). VESA needs to be removed for i915kms, but I've no idea if > it needs to be removed for Nvidia. The video reset code was reworked in > 10 so that having VESA is supposed to be like using > 'hw.acpi.reset_video=1' on 9, but in theory it works more often. The > ACPI_PM setting to the kernel module along with removing VESA would seem > like your best bet, but I see in follow-ups that that wasn't completely > reliable. However, you can try using ACPI_PM with syscons, no need to > use vt. Yes, without VESA, resume seems much more reliable on 10.0-RELEASE/amd64 with Nvidia: With a generic kernel, I put vesa_load="YES" in /boot/loader.conf to be able to kldunload vesa later. With that, I just had four successful suspend-and-resume cycles. Unfortunately, my USB mouse does not work anymore: After the first resume, it took a few seconds until it worked again (the build in touchpad was back immediately). After the second resume, it would not work anymore at all, even after reconnecting it to a different EHCI port. It does work at a XHCI, though, until the next resume. Anyhow, this is obviously not related to the original problem. Cheers, Jan Henrik