From owner-freebsd-mobile@freebsd.org Thu Feb 18 14:12:55 2016 Return-Path: Delivered-To: freebsd-mobile@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 E0F16AAC60A; Thu, 18 Feb 2016 14:12:54 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mx.nsu.ru (mx.nsu.ru [84.237.50.39]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 75DA3887; Thu, 18 Feb 2016 14:12:51 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from regency.nsu.ru ([193.124.210.26]) by mx.nsu.ru with esmtp (Exim 4.72) (envelope-from ) id 1aWPJy-0001D2-D5; Thu, 18 Feb 2016 20:12:43 +0600 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.14.2/8.14.2) with ESMTP id u1IEDitW021759; Thu, 18 Feb 2016 20:13:44 +0600 (NOVT) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.14.2/8.14.2/Submit) id u1IEDcG0021595; Thu, 18 Feb 2016 20:13:38 +0600 (NOVT) (envelope-from danfe) Date: Thu, 18 Feb 2016 20:13:38 +0600 From: Alexey Dokuchaev To: John Baldwin Cc: Kevin Oberman , Adrian Chadd , "current@freebsd.org" , Stefan Ehmann , "freebsd-mobile@freebsd.org" Subject: Re: Thinkpad T410: resume broken Message-ID: <20160218141338.GA15706@regency.nsu.ru> References: <53762216.8020205@gmx.net> <537753F3.6000202@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <537753F3.6000202@FreeBSD.org> User-Agent: Mutt/1.4.2.1i X-KLMS-Rule-ID: 1 X-KLMS-Message-Action: clean X-KLMS-AntiSpam-Lua-Profiles: 91511 [Feb 18 2016] X-KLMS-AntiSpam-Version: 5.5.9.33 X-KLMS-AntiSpam-Envelope-From: danfe@regency.nsu.ru X-KLMS-AntiSpam-Rate: 0 X-KLMS-AntiSpam-Status: not_detected X-KLMS-AntiSpam-Method: none X-KLMS-AntiSpam-Moebius-Timestamps: 3969737, 3969800, 3969585 X-KLMS-AntiSpam-Info: LuaCore: 414 414 652141367f63b6038f5642fa97308d3a9d2edb46, 127.0.0.200:7.1.3; regency.nsu.ru:7.1.1; d41d8cd98f00b204e9800998ecf8427e.com:7.1.1; 193.124.210.26:7.1.3,7.1.2,7.3.4; nsu.ru:7.1.1; 127.0.0.199:7.1.2; wiki.freebsd.org:7.1.1 X-KLMS-AntiSpam-Interceptor-Info: scan successful X-KLMS-AntiPhishing: Clean, 2016/02/18 11:55:00 X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.705, not scanned, license restriction X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Feb 2016 14:12:55 -0000 On Sat, May 17, 2014 at 08:20:03AM -0400, John Baldwin wrote: > 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. This (VESA needs to be removed for i915kms) is news to me: I don't see it mentioned in UPDATING, and "options VESA" presents in -CURRENT's (post-KMS era) GENERIC kernel config. So what's the real deal here? :-) If "having VESA is supposed to be like using 'hw.acpi.reset_video=1' on 9", it should not hurt (I recall having to hw.acpi.reset_video=1 in early stable/[67] days, but no longer for quite a long time with stable/8). Admittedly, the whole situation with i915kms, vesa.ko, et al. looks quite confusing, while suspend/resume works *worse* than with stable/8 and pre- KMS. Table of known laptops on wiki page [1] is hardly helpful unless it has your laptop of interest; IMHO it would benefit a lot more from listing common symptoms and mitigation/fixes for them (including VESA, sysctl vars, kernel options, etc). > 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. What are indications for use of ACPI_PM option? As for removing VESA, I've found that my laptop resumes more willingly with i915kms.ko *and* vesa.ko than without vesa.ko (could only? be loaded from loader.conf): with both modules loaded it takes only three presses of power button to get back from suspend, while without vesa.ko it's a lottery, and often power-cycling is required to get things back to working -- any ideas on why would that be? Needless to say, suspend/resume worked nearly flawlessly under stable/8 and stable/7 FWIW. ./danfe [1] https://wiki.freebsd.org/SuspendResume From owner-freebsd-mobile@freebsd.org Thu Feb 18 14:36:54 2016 Return-Path: Delivered-To: freebsd-mobile@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 8CA72AAD4BA; Thu, 18 Feb 2016 14:36:54 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mx.nsu.ru (mx.nsu.ru [84.237.50.39]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 38B76194D; Thu, 18 Feb 2016 14:36:53 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from regency.nsu.ru ([193.124.210.26]) by mx.nsu.ru with esmtp (Exim 4.72) (envelope-from ) id 1aWPhC-0000d4-CL; Thu, 18 Feb 2016 20:36:43 +0600 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.14.2/8.14.2) with ESMTP id u1IEbid3041643; Thu, 18 Feb 2016 20:37:44 +0600 (NOVT) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.14.2/8.14.2/Submit) id u1IEbcLS041553; Thu, 18 Feb 2016 20:37:38 +0600 (NOVT) (envelope-from danfe) Date: Thu, 18 Feb 2016 20:37:38 +0600 From: Alexey Dokuchaev To: John Baldwin Cc: Jan Henrik Sylvester , Hans Petter Selasky , Adrian Chadd , "current@freebsd.org" , Stefan Ehmann , "freebsd-mobile@freebsd.org" , Kevin Oberman Subject: Re: Thinkpad T410: resume broken Message-ID: <20160218143738.GA38066@regency.nsu.ru> References: <53762216.8020205@gmx.net> <537CFCE4.2000300@selasky.org> <537D01F5.2050101@janh.de> <201405231000.30861.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201405231000.30861.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i X-KLMS-Rule-ID: 1 X-KLMS-Message-Action: clean X-KLMS-AntiSpam-Lua-Profiles: 91511 [Feb 18 2016] X-KLMS-AntiSpam-Version: 5.5.9.33 X-KLMS-AntiSpam-Envelope-From: danfe@regency.nsu.ru X-KLMS-AntiSpam-Rate: 0 X-KLMS-AntiSpam-Status: not_detected X-KLMS-AntiSpam-Method: none X-KLMS-AntiSpam-Moebius-Timestamps: 3969835, 3969873, 3969585 X-KLMS-AntiSpam-Info: LuaCore: 414 414 652141367f63b6038f5642fa97308d3a9d2edb46, 127.0.0.200:7.1.3; regency.nsu.ru:7.1.1; 193.124.210.26:7.1.3,7.1.2,7.3.4; nsu.ru:7.1.1; 127.0.0.199:7.1.2; d41d8cd98f00b204e9800998ecf8427e.com:7.1.1 X-KLMS-AntiSpam-Interceptor-Info: scan successful X-KLMS-AntiPhishing: Clean, 2016/02/18 11:55:00 X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.705, not scanned, license restriction X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Feb 2016 14:36:54 -0000 On Fri, May 23, 2014 at 10:00:30AM -0400, John Baldwin wrote: > On Wednesday, May 21, 2014 3:43:49 pm Jan Henrik Sylvester wrote: > > Looking through dmesg, it seems that other USB devices (build-in) are > > reappearing (Qualcomm Gobi 2000, Broadcom Bluetooth Device) after > > resume, just not the mouse. > > > > Are these lines likely related? > > > > pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.PEG_: > > AE_BAD_PARAMETER > > pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP1: > > AE_BAD_PARAMETER > > pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP2: > > AE_BAD_PARAMETER > > pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP4: > > AE_BAD_PARAMETER > > pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP5: > > AE_BAD_PARAMETER > > These are probably not related. These man that your BIOS explicitly told > the OS to power down these devices (PEG_ is probably your GPU, and EXP[1-5] > are probably PCI-PCI bridges that represent the downstream ports of your > PCI-e root complex) in the D2 state when suspending, but the devices don't > actually support D2 (most PCI devices only support D0 (full on) and D3 > (full off)). I've started to observe similar lines in the logs after updating to fresh -CURRENT, upon resume (on a different laptop though, not T410): pcib0: failed to set ACPI power state D2 on \_SB_.PCI0: AE_BAD_PARAMETER acpi0: cleared fixed power button status If these messages are legit, I'm wondering why I didn't see them on 8.4, and if it might affect suspend/resume sequence (broken right now)? Thanks, ./danfe From owner-freebsd-mobile@freebsd.org Thu Feb 18 14:55:35 2016 Return-Path: Delivered-To: freebsd-mobile@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 AE67AAADCED; Thu, 18 Feb 2016 14:55:35 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 88F9B95F; Thu, 18 Feb 2016 14:55:35 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 93073B94E; Thu, 18 Feb 2016 09:55:34 -0500 (EST) From: John Baldwin To: Alexey Dokuchaev Cc: Kevin Oberman , Adrian Chadd , "current@freebsd.org" , Stefan Ehmann , "freebsd-mobile@freebsd.org" Subject: Re: Thinkpad T410: resume broken Date: Thu, 18 Feb 2016 06:50:34 -0800 Message-ID: <2846385.IUIOUlEDYf@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: <20160218141338.GA15706@regency.nsu.ru> References: <53762216.8020205@gmx.net> <537753F3.6000202@FreeBSD.org> <20160218141338.GA15706@regency.nsu.ru> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 18 Feb 2016 09:55:34 -0500 (EST) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Feb 2016 14:55:35 -0000 On Thursday, February 18, 2016 08:13:38 PM Alexey Dokuchaev wrote: > On Sat, May 17, 2014 at 08:20:03AM -0400, John Baldwin wrote: > > 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. > > This (VESA needs to be removed for i915kms) is news to me: I don't see it > mentioned in UPDATING, and "options VESA" presents in -CURRENT's (post-KMS > era) GENERIC kernel config. So what's the real deal here? :-) This is an old mail you are responding to. You no longer need to remove VESA for kms. > If "having VESA is supposed to be like using 'hw.acpi.reset_video=1' on > 9", it should not hurt (I recall having to hw.acpi.reset_video=1 in early > stable/[67] days, but no longer for quite a long time with stable/8). > > Admittedly, the whole situation with i915kms, vesa.ko, et al. looks quite > confusing, while suspend/resume works *worse* than with stable/8 and pre- > KMS. Table of known laptops on wiki page [1] is hardly helpful unless it > has your laptop of interest; IMHO it would benefit a lot more from listing > common symptoms and mitigation/fixes for them (including VESA, sysctl vars, > kernel options, etc). The value of "worse" depends on your laptop. I have an older i386 HP netbook for which resume works fine using sc(4) and the older DRM drivers because the video BIOS turns the LCD back on during resume without requiring the OS to do so. However, the recent GPU chipsets from Intel do not do that and the only bit of code in the tree that knows how to turn the LCD panel back on is the KMS driver. However, note that KMS is not related to NVidia GPUs. If your laptop is using one of those then the nvidia driver is what has to turn the LCD panel back on. > > 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. > > What are indications for use of ACPI_PM option? As for removing VESA, > I've found that my laptop resumes more willingly with i915kms.ko *and* > vesa.ko than without vesa.ko (could only? be loaded from loader.conf): > with both modules loaded it takes only three presses of power button to > get back from suspend, while without vesa.ko it's a lottery, and often > power-cycling is required to get things back to working -- any ideas on > why would that be? vesa.ko shouldn't be working with KMS. KMS turns off the legacy VGA emulation in the hardware when it starts which prevents VESA from working (VESA requires the legacy VGA interface). I never have to hit the power button more than once to resume on a laptop where resume works though. (True on my X220 and on a T440 both with Intel or Radeon graphics (all using KMS). > Needless to say, suspend/resume worked nearly flawlessly under stable/8 > and stable/7 FWIW. If it worked here, then this means you could try using sc(4) + the old drm (not drm2). This means your laptop is old enough to still turn the LCD panel back on in its BIOS during resume like my HP netbook. However, I don't know for how much longer Xorg will support the older drm (if it even does now). FWIW, the HP netbook resumes fine with KMS as well for me. One caveat though is that if you are using vt(4) and haven't yet loaded KMS it won't resume (due to vt(4) not having the equivalent of VESA). With sc(4) the netbook was always able to resume. -- John Baldwin From owner-freebsd-mobile@freebsd.org Thu Feb 18 14:55:34 2016 Return-Path: Delivered-To: freebsd-mobile@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 BA8F5AADCDA; Thu, 18 Feb 2016 14:55:34 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9901C95B; Thu, 18 Feb 2016 14:55:34 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 4E913B918; Thu, 18 Feb 2016 09:55:33 -0500 (EST) From: John Baldwin To: Alexey Dokuchaev Cc: Jan Henrik Sylvester , Hans Petter Selasky , Adrian Chadd , "current@freebsd.org" , Stefan Ehmann , "freebsd-mobile@freebsd.org" , Kevin Oberman Subject: Re: Thinkpad T410: resume broken Date: Thu, 18 Feb 2016 06:55:03 -0800 Message-ID: <1519677.qimO7W0WJL@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: <20160218143738.GA38066@regency.nsu.ru> References: <53762216.8020205@gmx.net> <201405231000.30861.jhb@freebsd.org> <20160218143738.GA38066@regency.nsu.ru> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 18 Feb 2016 09:55:33 -0500 (EST) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Feb 2016 14:55:34 -0000 On Thursday, February 18, 2016 08:37:38 PM Alexey Dokuchaev wrote: > On Fri, May 23, 2014 at 10:00:30AM -0400, John Baldwin wrote: > > On Wednesday, May 21, 2014 3:43:49 pm Jan Henrik Sylvester wrote: > > > Looking through dmesg, it seems that other USB devices (build-in) are > > > reappearing (Qualcomm Gobi 2000, Broadcom Bluetooth Device) after > > > resume, just not the mouse. > > > > > > Are these lines likely related? > > > > > > pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.PEG_: > > > AE_BAD_PARAMETER > > > pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP1: > > > AE_BAD_PARAMETER > > > pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP2: > > > AE_BAD_PARAMETER > > > pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP4: > > > AE_BAD_PARAMETER > > > pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP5: > > > AE_BAD_PARAMETER > > > > These are probably not related. These man that your BIOS explicitly told > > the OS to power down these devices (PEG_ is probably your GPU, and EXP[1-5] > > are probably PCI-PCI bridges that represent the downstream ports of your > > PCI-e root complex) in the D2 state when suspending, but the devices don't > > actually support D2 (most PCI devices only support D0 (full on) and D3 > > (full off)). > > I've started to observe similar lines in the logs after updating to fresh > -CURRENT, upon resume (on a different laptop though, not T410): > > pcib0: failed to set ACPI power state D2 on \_SB_.PCI0: AE_BAD_PARAMETER > acpi0: cleared fixed power button status > > If these messages are legit, I'm wondering why I didn't see them on 8.4, > and if it might affect suspend/resume sequence (broken right now)? Thanks, 8.4 has a bug fixed only in HEAD where we tried to power down the wrong devices during suspend (or used the _Sx hint from the wrong device to decide which Dx state to use when powering down, I can't recall which). For this reason, 11 is going to use different Dx states on different devices. The reason for the message remains the same (though it should now be correct on 11). Your BIOS said "please put this device in D2 during suspend" and your device's capabilites said "I don't support D2". You can confirm this by looking up the _S3 method of your _SB_.PCIO device to find out what state is requested during suspend and then looking at 'pciconf -lc pci0:0:0' to see what D states are listed as supported. There's not much we can do if your BIOS lies to us. -- John Baldwin From owner-freebsd-mobile@freebsd.org Thu Feb 18 15:46:24 2016 Return-Path: Delivered-To: freebsd-mobile@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 6440DAAD954; Thu, 18 Feb 2016 15:46:24 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mx.nsu.ru (mx.nsu.ru [84.237.50.39]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 110F017DD; Thu, 18 Feb 2016 15:46:23 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from regency.nsu.ru ([193.124.210.26]) by mx.nsu.ru with esmtp (Exim 4.72) (envelope-from ) id 1aWQmV-00044O-IW; Thu, 18 Feb 2016 21:46:16 +0600 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.14.2/8.14.2) with ESMTP id u1IFlHHV062697; Thu, 18 Feb 2016 21:47:17 +0600 (NOVT) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.14.2/8.14.2/Submit) id u1IFlCMM062651; Thu, 18 Feb 2016 21:47:12 +0600 (NOVT) (envelope-from danfe) Date: Thu, 18 Feb 2016 21:47:12 +0600 From: Alexey Dokuchaev To: John Baldwin Cc: Kevin Oberman , Adrian Chadd , "current@freebsd.org" , Stefan Ehmann , "freebsd-mobile@freebsd.org" Subject: Re: Thinkpad T410: resume broken Message-ID: <20160218154712.GA56997@regency.nsu.ru> References: <53762216.8020205@gmx.net> <537753F3.6000202@FreeBSD.org> <20160218141338.GA15706@regency.nsu.ru> <2846385.IUIOUlEDYf@ralph.baldwin.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2846385.IUIOUlEDYf@ralph.baldwin.cx> User-Agent: Mutt/1.4.2.1i X-KLMS-Rule-ID: 1 X-KLMS-Message-Action: clean X-KLMS-AntiSpam-Lua-Profiles: 91511 [Feb 18 2016] X-KLMS-AntiSpam-Version: 5.5.9.33 X-KLMS-AntiSpam-Envelope-From: danfe@regency.nsu.ru X-KLMS-AntiSpam-Rate: 0 X-KLMS-AntiSpam-Status: not_detected X-KLMS-AntiSpam-Method: none X-KLMS-AntiSpam-Moebius-Timestamps: 3969987, 3970033, 3969585 X-KLMS-AntiSpam-Info: LuaCore: 414 414 652141367f63b6038f5642fa97308d3a9d2edb46, 127.0.0.200:7.1.3; regency.nsu.ru:7.1.1; 193.124.210.26:7.1.3,7.1.2,7.3.4; nsu.ru:7.1.1; 127.0.0.199:7.1.2; d41d8cd98f00b204e9800998ecf8427e.com:7.1.1 X-KLMS-AntiSpam-Interceptor-Info: scan successful X-KLMS-AntiPhishing: Clean, 2016/02/18 11:55:00 X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.705, not scanned, license restriction X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Feb 2016 15:46:24 -0000 On Thu, Feb 18, 2016 at 06:50:34AM -0800, John Baldwin wrote: > On Thursday, February 18, 2016 08:13:38 PM Alexey Dokuchaev wrote: > > On Sat, May 17, 2014 at 08:20:03AM -0400, John Baldwin wrote: > > > 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. > > > > This (VESA needs to be removed for i915kms) is news to me: I don't see it > > mentioned in UPDATING, and "options VESA" presents in -CURRENT's (post-KMS > > era) GENERIC kernel config. So what's the real deal here? :-) > > This is an old mail you are responding to. You no longer need to remove > VESA for kms. Ah OK, that would explain it, thanks. > vesa.ko shouldn't be working with KMS. KMS turns off the legacy VGA > emulation in the hardware when it starts which prevents VESA from working > (VESA requires the legacy VGA interface). Hmm, could this explain why vesa.ko can be loaded from loader.conf, but not via kldload(8)? OTOH, kldload'ing it later does not seem to work (ir)regardless of whether i915kms.ko is loaded or not... > I never have to hit the power button more than once to resume on a laptop > where resume works though. > > (True on my X220 and on a T440 both with Intel or Radeon graphics (all > using KMS). I'm about to try fresh -CURRENT on some HP AMD APU-based laptops, hence I'll ask: do aforementioned laptops suspend/resume without issues in X11 or on the naked console as well? (In a shop, I could only quickly test our X11-less memstick image.) > > Needless to say, suspend/resume worked nearly flawlessly under stable/8 > > and stable/7 FWIW. > > If it worked here, then this means you could try using sc(4) + the old drm > (not drm2). This means your laptop is old enough to still turn the LCD panel > back on in its BIOS during resume like my HP netbook. However, I don't know > for how much longer Xorg will support the older drm (if it even does now). Well, technically, my laptop *does* resume with vt(4) + i915kms, just it takes a lot of power button hits and quite some time (up to several minutes), unless it dies somewhere during the process. I'll retest it against GENERIC and report in a separate email. On a related note, how does one configure sc(4) with old drm (vs. drm2) shall I need to try that? > FWIW, the HP netbook resumes fine with KMS as well for me. One caveat > though is that if you are using vt(4) and haven't yet loaded KMS it won't > resume (due to vt(4) not having the equivalent of VESA). With sc(4) the > netbook was always able to resume. Right. So far, I've been booting, kldloading i915kms.ko, zzz(8), resume. No X.Org was involved -- given how fragile suspend/resume is ATM, I'd like to iron out the issues with the pure console first. ./danfe From owner-freebsd-mobile@freebsd.org Thu Feb 18 16:55:43 2016 Return-Path: Delivered-To: freebsd-mobile@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 4D537AAC0E3; Thu, 18 Feb 2016 16:55:43 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mx.nsu.ru (mx.nsu.ru [84.237.50.39]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EBB0E789; Thu, 18 Feb 2016 16:55:42 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from regency.nsu.ru ([193.124.210.26]) by mx.nsu.ru with esmtp (Exim 4.72) (envelope-from ) id 1aWRrY-0003U6-9s; Thu, 18 Feb 2016 22:55:33 +0600 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.14.2/8.14.2) with ESMTP id u1IGuYwV072968; Thu, 18 Feb 2016 22:56:34 +0600 (NOVT) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.14.2/8.14.2/Submit) id u1IGuTOF072930; Thu, 18 Feb 2016 22:56:29 +0600 (NOVT) (envelope-from danfe) Date: Thu, 18 Feb 2016 22:56:29 +0600 From: Alexey Dokuchaev To: John Baldwin Cc: Jan Henrik Sylvester , Hans Petter Selasky , Adrian Chadd , "current@freebsd.org" , Stefan Ehmann , "freebsd-mobile@freebsd.org" , Kevin Oberman Subject: Re: Thinkpad T410: resume broken Message-ID: <20160218165629.GA64990@regency.nsu.ru> References: <53762216.8020205@gmx.net> <201405231000.30861.jhb@freebsd.org> <20160218143738.GA38066@regency.nsu.ru> <1519677.qimO7W0WJL@ralph.baldwin.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1519677.qimO7W0WJL@ralph.baldwin.cx> User-Agent: Mutt/1.4.2.1i X-KLMS-Rule-ID: 1 X-KLMS-Message-Action: clean X-KLMS-AntiSpam-Lua-Profiles: 91515 [Feb 18 2016] X-KLMS-AntiSpam-Version: 5.5.9.33 X-KLMS-AntiSpam-Envelope-From: danfe@regency.nsu.ru X-KLMS-AntiSpam-Rate: 0 X-KLMS-AntiSpam-Status: not_detected X-KLMS-AntiSpam-Method: none X-KLMS-AntiSpam-Moebius-Timestamps: 3970137, 3970161, 3969585 X-KLMS-AntiSpam-Info: LuaCore: 414 414 652141367f63b6038f5642fa97308d3a9d2edb46, 127.0.0.200:7.1.3; regency.nsu.ru:7.1.1; 193.124.210.26:7.1.3,7.1.2,7.3.4; nsu.ru:7.1.1; 127.0.0.199:7.1.2; d41d8cd98f00b204e9800998ecf8427e.com:7.1.1 X-KLMS-AntiSpam-Interceptor-Info: scan successful X-KLMS-AntiPhishing: Clean, 2016/02/18 13:06:53 X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.705, not scanned, license restriction X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Feb 2016 16:55:43 -0000 On Thu, Feb 18, 2016 at 06:55:03AM -0800, John Baldwin wrote: > On Thursday, February 18, 2016 08:37:38 PM Alexey Dokuchaev wrote: > > I've started to observe similar lines in the logs after updating to > > fresh -CURRENT, upon resume (on a different laptop though, not T410): > > > > pcib0: failed to set ACPI power state D2 on \_SB_.PCI0: AE_BAD_PARAMETER > > acpi0: cleared fixed power button status > > > > If these messages are legit, I'm wondering why I didn't see them on 8.4, > > and if it might affect suspend/resume sequence (broken right now)? > > [...] Your BIOS said "please put this device in D2 during suspend" and your > device's capabilities said "I don't support D2". You can confirm this by > looking up the _S3 method of your _SB_.PCIO device to find out what state is > requested during suspend and then looking at 'pciconf -lc pci0:0:0' to see > what D states are listed as supported. This?: Scope (\_SB) { Name (ECOK, 0x00) Device (PCI0) { Method (_S3D, 0, NotSerialized) // _S3D: S3 Device State { Return (0x02) } ... # pciconf -lc pci0:0:0 hostb0@pci0:0:0:0: class=0x060000 card=0x83191033 chip=0x25908086 rev=0x04 hdr=0x00 cap 09[e0] = vendor (length 9) Intel cap 2 version 1 # pciconf -rb pci0:0:0 0xe0:0xff 09 00 09 21 02 a2 8b 90 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 05 00 10 00 00 00 > There's not much we can do if your BIOS lies to us. As long as we can patch ACPI tables, lying BIOS should not be a problem, no? ./danfe From owner-freebsd-mobile@freebsd.org Thu Feb 18 17:53:38 2016 Return-Path: Delivered-To: freebsd-mobile@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 2B006AADDD6; Thu, 18 Feb 2016 17:53:38 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 05BB915B1; Thu, 18 Feb 2016 17:53:38 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 1C7DBB990; Thu, 18 Feb 2016 12:53:37 -0500 (EST) From: John Baldwin To: Alexey Dokuchaev Cc: Kevin Oberman , Adrian Chadd , "current@freebsd.org" , Stefan Ehmann , "freebsd-mobile@freebsd.org" Subject: Re: Thinkpad T410: resume broken Date: Thu, 18 Feb 2016 09:48:40 -0800 Message-ID: <9693306.i8x5an8c0H@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: <20160218154712.GA56997@regency.nsu.ru> References: <53762216.8020205@gmx.net> <2846385.IUIOUlEDYf@ralph.baldwin.cx> <20160218154712.GA56997@regency.nsu.ru> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 18 Feb 2016 12:53:37 -0500 (EST) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Feb 2016 17:53:38 -0000 On Thursday, February 18, 2016 09:47:12 PM Alexey Dokuchaev wrote: > On Thu, Feb 18, 2016 at 06:50:34AM -0800, John Baldwin wrote: > > On Thursday, February 18, 2016 08:13:38 PM Alexey Dokuchaev wrote: > > vesa.ko shouldn't be working with KMS. KMS turns off the legacy VGA > > emulation in the hardware when it starts which prevents VESA from working > > (VESA requires the legacy VGA interface). > > Hmm, could this explain why vesa.ko can be loaded from loader.conf, but > not via kldload(8)? OTOH, kldload'ing it later does not seem to work > (ir)regardless of whether i915kms.ko is loaded or not... You might load it from loader.conf but it might then fail with an error about failing to register in dmesg. In that case it is effectively ignored. > > I never have to hit the power button more than once to resume on a laptop > > where resume works though. > > > > (True on my X220 and on a T440 both with Intel or Radeon graphics (all > > using KMS). > > I'm about to try fresh -CURRENT on some HP AMD APU-based laptops, hence > I'll ask: do aforementioned laptops suspend/resume without issues in X11 > or on the naked console as well? (In a shop, I could only quickly test > our X11-less memstick image.) Once KMS is loaded they resume fine. They require the KMS driver to turn the LCD panel back on. Without KMS they also "resume" but the screen is off so you can't see anything. However, you can type blind and run commands. If the network is up you can ssh into the laptop, etc. after resume. > > > Needless to say, suspend/resume worked nearly flawlessly under stable/8 > > > and stable/7 FWIW. > > > > If it worked here, then this means you could try using sc(4) + the old drm > > (not drm2). This means your laptop is old enough to still turn the LCD panel > > back on in its BIOS during resume like my HP netbook. However, I don't know > > for how much longer Xorg will support the older drm (if it even does now). > > Well, technically, my laptop *does* resume with vt(4) + i915kms, just it > takes a lot of power button hits and quite some time (up to several minutes), > unless it dies somewhere during the process. I'll retest it against > GENERIC and report in a separate email. On a related note, how does one > configure sc(4) with old drm (vs. drm2) shall I need to try that? On HEAD you need to set kern.vty=sc to use sc(4) instead of vt(4). For suspend/resume without X that should be sufficient. You would only need the old drm drivers for X. > > FWIW, the HP netbook resumes fine with KMS as well for me. One caveat > > though is that if you are using vt(4) and haven't yet loaded KMS it won't > > resume (due to vt(4) not having the equivalent of VESA). With sc(4) the > > netbook was always able to resume. > > Right. So far, I've been booting, kldloading i915kms.ko, zzz(8), resume. > No X.Org was involved -- given how fragile suspend/resume is ATM, I'd like > to iron out the issues with the pure console first. Note that for the HP netbook, resume in console with vt(4) does not work without KMS (due to vt(4) not supporting VESA). -- John Baldwin From owner-freebsd-mobile@freebsd.org Thu Feb 18 17:53:37 2016 Return-Path: Delivered-To: freebsd-mobile@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 54CE1AADDCF; Thu, 18 Feb 2016 17:53:37 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3486C15AC; Thu, 18 Feb 2016 17:53:37 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id CE4D6B94E; Thu, 18 Feb 2016 12:53:35 -0500 (EST) From: John Baldwin To: Alexey Dokuchaev Cc: Jan Henrik Sylvester , Hans Petter Selasky , Adrian Chadd , "current@freebsd.org" , Stefan Ehmann , "freebsd-mobile@freebsd.org" , Kevin Oberman Subject: Re: Thinkpad T410: resume broken Date: Thu, 18 Feb 2016 09:51:08 -0800 Message-ID: <3029262.DlAcg8ENfU@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: <20160218165629.GA64990@regency.nsu.ru> References: <53762216.8020205@gmx.net> <1519677.qimO7W0WJL@ralph.baldwin.cx> <20160218165629.GA64990@regency.nsu.ru> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 18 Feb 2016 12:53:35 -0500 (EST) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Feb 2016 17:53:37 -0000 On Thursday, February 18, 2016 10:56:29 PM Alexey Dokuchaev wrote: > On Thu, Feb 18, 2016 at 06:55:03AM -0800, John Baldwin wrote: > > On Thursday, February 18, 2016 08:37:38 PM Alexey Dokuchaev wrote: > > > I've started to observe similar lines in the logs after updating to > > > fresh -CURRENT, upon resume (on a different laptop though, not T410): > > > > > > pcib0: failed to set ACPI power state D2 on \_SB_.PCI0: AE_BAD_PARAMETER > > > acpi0: cleared fixed power button status > > > > > > If these messages are legit, I'm wondering why I didn't see them on 8.4, > > > and if it might affect suspend/resume sequence (broken right now)? > > > > [...] Your BIOS said "please put this device in D2 during suspend" and your > > device's capabilities said "I don't support D2". You can confirm this by > > looking up the _S3 method of your _SB_.PCIO device to find out what state is > > requested during suspend and then looking at 'pciconf -lc pci0:0:0' to see > > what D states are listed as supported. > > This?: > > Scope (\_SB) > { > Name (ECOK, 0x00) > Device (PCI0) > { > Method (_S3D, 0, NotSerialized) // _S3D: S3 Device State > { > Return (0x02) > } > ... Yes, this says "please use D2 when going to S3". > # pciconf -lc pci0:0:0 > hostb0@pci0:0:0:0: class=0x060000 card=0x83191033 chip=0x25908086 rev=0x04 hdr=0x00 > cap 09[e0] = vendor (length 9) Intel cap 2 version 1 Humm, perhaps PCI0 is not at 0:0. Can you find the _ADR method for _SB_.PCI0? That contains the "slot" and "function" as two words, e.g. 0x10002 would correspond to the 'pci0:1:2' device (or possibly pci0:2:1, don't recall the order off the top of my head). -- John Baldwin From owner-freebsd-mobile@freebsd.org Thu Feb 18 18:02:18 2016 Return-Path: Delivered-To: freebsd-mobile@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 DCB35AAC298; Thu, 18 Feb 2016 18:02:18 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (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 A603F1E5D; Thu, 18 Feb 2016 18:02:18 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x230.google.com with SMTP id g203so82386063iof.2; Thu, 18 Feb 2016 10:02:18 -0800 (PST) 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=3LJMvbnyhs+fkpi7SSIrA/5+PWZjYs/diBmt2TmT11c=; b=bXk/pZQx7JDkyW97EkBM+p2dQtEIBhj14UfJYe2wX0KPcmhgD/lTia+KpOQy0A/sxF jV8E34ZVMw63Soq0CXlhP/m1mhkSgt31H6n6ReZ4JorKbVo7137hmBh+euGE25HtAtTh 4Xj1m0gNLf/p1+OoTR3lJKJrhu/jNnTJkph28zgfGuzMEWVxPCUwGj/4WmdZgRQI0Xc1 Nrn6LBUicu+nxYYw4pGjDn2Dw8SVfa3RFDmg/oLGnNvbsPO3vF2Gu64wpo/UpM31ief2 JW0H5o5m6o9+hsUfesZ1qJIWgHb+OlUZQ9FzhvXQqSxwzUkOXmTSReWp+kT3/I8aZ73y z0kg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=3LJMvbnyhs+fkpi7SSIrA/5+PWZjYs/diBmt2TmT11c=; b=TXjk4Uv85PPkvmZf1koV8o05AphVl3sePlewCYhAMPGPbUOpuY6kFeLUgJwf0tV4P3 YhsoMLlwy4wuoYPN90eHnAkohCvjExDbLWLNJKZa6RPlp6mku3mUNVXRBEUDzTEa22Ep jJfF4q1G8sSCm2hmzZGBTbQpHy4ok548o8kA3Ccytz9flBwsWIIqfHvCljGiP2dOrvOf fXSI4FoOxrggdqvvOFoYRtcCCeNcAJiyr+xzd8wtjvc9BnIVegBk27+9/fqZz31VoGcT OEccbftp1ttR2nNoBTvTeb4Gbos0DoumC4jEfqyECTJtD2zWg+rkgMLnJWOZZv5Rmbno 8Z0g== X-Gm-Message-State: AG10YORXRTyz1bkJhuDwnm1K7wUkBMRsJPMi9yVEtrkv/sBCSZjRcmZJRWuP6aU4zjRF29iONcnrqPEA+sk3FQ== MIME-Version: 1.0 X-Received: by 10.107.162.144 with SMTP id l138mr9749137ioe.123.1455818538099; Thu, 18 Feb 2016 10:02:18 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.14.19 with HTTP; Thu, 18 Feb 2016 10:02:17 -0800 (PST) In-Reply-To: <9693306.i8x5an8c0H@ralph.baldwin.cx> References: <53762216.8020205@gmx.net> <2846385.IUIOUlEDYf@ralph.baldwin.cx> <20160218154712.GA56997@regency.nsu.ru> <9693306.i8x5an8c0H@ralph.baldwin.cx> Date: Thu, 18 Feb 2016 10:02:17 -0800 X-Google-Sender-Auth: wP_LDl7CZino1XFb_u8zlZGdCC8 Message-ID: Subject: Re: Thinkpad T410: resume broken From: Adrian Chadd To: John Baldwin Cc: Alexey Dokuchaev , Kevin Oberman , "current@freebsd.org" , Stefan Ehmann , "freebsd-mobile@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Feb 2016 18:02:19 -0000 [snip] Someone should sit me down with pizza and "help" me just modularise the vesa/fb code so we can use it in vt. It isn't /that/ hard, I've just been preoccupied. -a From owner-freebsd-mobile@freebsd.org Thu Feb 18 22:29:11 2016 Return-Path: Delivered-To: freebsd-mobile@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 C4B5BAADD5D for ; Thu, 18 Feb 2016 22:29:11 +0000 (UTC) (envelope-from bengta@sics.se) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A5549A37 for ; Thu, 18 Feb 2016 22:29:11 +0000 (UTC) (envelope-from bengta@sics.se) Received: by mailman.ysv.freebsd.org (Postfix) id A4640AADD5C; Thu, 18 Feb 2016 22:29:11 +0000 (UTC) Delivered-To: mobile@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 A4013AADD5B for ; Thu, 18 Feb 2016 22:29:11 +0000 (UTC) (envelope-from bengta@sics.se) Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (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 390DBA36 for ; Thu, 18 Feb 2016 22:29:11 +0000 (UTC) (envelope-from bengta@sics.se) Received: by mail-lf0-x230.google.com with SMTP id l143so42460832lfe.2 for ; Thu, 18 Feb 2016 14:29:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sics-se.20150623.gappssmtp.com; s=20150623; h=from:to:subject:user-agent:date:message-id:mime-version :content-type; bh=PaL2RjAkoCZuis6DSWg98ppiq0tP2MUVR8Yezm5k+Tg=; b=S3CKK6TKfc2v5iS2GbAn7uHfeBIp2M+t8M3fqO1xwZZbU+XI/eqpTOg+UkNkitBdDv 0fE33nKQ+2yFQlYuE5JeI/KV+IDKyc9ts54h8qXRQlb3r92dikMnMiCJvrPPJMjEuUQy 0RMDyUPWBpYfDumIIQBvifHDoS0RpUGEPek8OFsHzF/lsFu6IkqCjPLhrzHPN/VG7rl1 6o03RlOz//mAn9WQ6hGf+jbCk6LKz6bPVHoWIzlpF3AVgBB6bSzuoa8qoWafYZWwnscR Znzt3e5B5bN9w5a/9nEU4JRtxDIogMpITmQqBndjBwxdyoZid8B80O5Xl4K8PlL76Ca/ 2DAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:user-agent:date:message-id :mime-version:content-type; bh=PaL2RjAkoCZuis6DSWg98ppiq0tP2MUVR8Yezm5k+Tg=; b=Ad3JnqsPEQ7ymSUXdgF8estyBaRZ7e8uBP3g+dTDz2n4QCHBNE4LcPx50Km7nCc1fZ ngW725RCs4aee5Hz0NgYOtcEzefbkphtzOJJo1qtLEyhBid9egz4JLwG5luiFbRi99Q8 gH567LkdKFqhzVs5pbY1SWayYHC1psa8Iub9ncjpgKaFTVbcm0/osFSw2zENQ5lyCWU8 OA2tiYEDA+Lm1lNS6ZTlRSPEHFcBkIs2de0I5scdrfR1DEws2Z2xUcm9O9NLM2udUIxC zL69O4U/W3qrAZuIqwkcIhT8KabbRk5H4skNzg+FK8u0jpapbBrPpFvY0vb/aj1nbZTR cZNQ== X-Gm-Message-State: AG10YORSA0KS8VnREvzrFsqLbwA6rCBo+zuqkGWBZfa0/2iUezzPeAFbMfY9gHY3wdV8ieab X-Received: by 10.25.24.68 with SMTP id o65mr3466621lfi.156.1455834549063; Thu, 18 Feb 2016 14:29:09 -0800 (PST) Received: from P142s.sics.se (h139n3-u-d1.ias.bredband.telia.com. [90.228.197.139]) by smtp.gmail.com with ESMTPSA id 193sm1203106lfz.26.2016.02.18.14.29.07 (version=TLS1 cipher=AES128-SHA bits=128/128); Thu, 18 Feb 2016 14:29:08 -0800 (PST) Received: from P142s.sics.se (localhost [127.0.0.1]) by P142s.sics.se (8.15.2/8.15.2) with ESMTP id u1IMRpks001968; Thu, 18 Feb 2016 23:27:51 +0100 (CET) (envelope-from bengta@P142s.sics.se) Received: (from bengta@localhost) by P142s.sics.se (8.15.2/8.15.2/Submit) id u1IMRpsE001967; Thu, 18 Feb 2016 23:27:51 +0100 (CET) (envelope-from bengta@P142s.sics.se) From: Bengt Ahlgren To: mobile@freebsd.org Subject: Mouse does not work after resume User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix) Date: Thu, 18 Feb 2016 23:27:51 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Feb 2016 22:29:11 -0000 The mouse does not work on my Lenovo X201 after resume on 10-STABLE (10.3-BETA2). The issue is known and resolved - see: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200938 The fix works for me - is there anything preventing committing this to stable/10? Bengt From owner-freebsd-mobile@freebsd.org Fri Feb 19 11:54:36 2016 Return-Path: Delivered-To: freebsd-mobile@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 C5600AAC6FF; Fri, 19 Feb 2016 11:54:36 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mx.nsu.ru (mx.nsu.ru [84.237.50.39]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3733613F0; Fri, 19 Feb 2016 11:54:35 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from regency.nsu.ru ([193.124.210.26]) by mx.nsu.ru with esmtp (Exim 4.72) (envelope-from ) id 1aWjdi-0003fn-SJ; Fri, 19 Feb 2016 17:54:27 +0600 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.14.2/8.14.2) with ESMTP id u1JBtVc5018050; Fri, 19 Feb 2016 17:55:31 +0600 (NOVT) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.14.2/8.14.2/Submit) id u1JBtQm4018049; Fri, 19 Feb 2016 17:55:26 +0600 (NOVT) (envelope-from danfe) Date: Fri, 19 Feb 2016 17:55:26 +0600 From: Alexey Dokuchaev To: John Baldwin Cc: Kevin Oberman , Adrian Chadd , "current@freebsd.org" , Stefan Ehmann , "freebsd-mobile@freebsd.org" Subject: Re: Thinkpad T410: resume broken Message-ID: <20160219115525.GA12543@regency.nsu.ru> References: <53762216.8020205@gmx.net> <2846385.IUIOUlEDYf@ralph.baldwin.cx> <20160218154712.GA56997@regency.nsu.ru> <9693306.i8x5an8c0H@ralph.baldwin.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9693306.i8x5an8c0H@ralph.baldwin.cx> User-Agent: Mutt/1.4.2.1i X-KLMS-Rule-ID: 1 X-KLMS-Message-Action: clean X-KLMS-AntiSpam-Lua-Profiles: 91565 [Feb 19 2016] X-KLMS-AntiSpam-Version: 5.5.9.33 X-KLMS-AntiSpam-Envelope-From: danfe@regency.nsu.ru X-KLMS-AntiSpam-Rate: 0 X-KLMS-AntiSpam-Status: not_detected X-KLMS-AntiSpam-Method: none X-KLMS-AntiSpam-Moebius-Timestamps: 3971456, 3971494, 3971287 X-KLMS-AntiSpam-Info: LuaCore: 414 414 652141367f63b6038f5642fa97308d3a9d2edb46, 127.0.0.200:7.1.3; regency.nsu.ru:7.1.1; 193.124.210.26:7.1.3,7.1.2,7.3.4; nsu.ru:7.1.1; 127.0.0.199:7.1.2; d41d8cd98f00b204e9800998ecf8427e.com:7.1.1 X-KLMS-AntiSpam-Interceptor-Info: scan successful X-KLMS-AntiPhishing: Clean, 2016/02/18 13:06:53 X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.705, not scanned, license restriction X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Feb 2016 11:54:37 -0000 On Thu, Feb 18, 2016 at 09:48:40AM -0800, John Baldwin wrote: > On Thursday, February 18, 2016 09:47:12 PM Alexey Dokuchaev wrote: > > On Thu, Feb 18, 2016 at 06:50:34AM -0800, John Baldwin wrote: > > > On Thursday, February 18, 2016 08:13:38 PM Alexey Dokuchaev wrote: > > > vesa.ko shouldn't be working with KMS. KMS turns off the legacy VGA > > > emulation in the hardware when it starts which prevents VESA from > > > working (VESA requires the legacy VGA interface). > > > > Hmm, could this explain why vesa.ko can be loaded from loader.conf, but > > not via kldload(8)? OTOH, kldload'ing it later does not seem to work > > (ir)regardless of whether i915kms.ko is loaded or not... > > You might load it from loader.conf but it might then fail with an error > about failing to register in dmesg. In that case it is effectively > ignored. By "can be loaded from loader.conf" I mean that it's reported in kldstat(8) output. I'm still unsure if I understand all implications of having or not having VESA kernel option or vesa.ko loaded in vt(4)+KMS world. E.g., do I understand correctly that vesa.ko is not needed (or might even cause certain problems) with vt(4)+KMS, and "options VESA" is left in GENERIC as part of syscons(4) support, and will likely go south together with syscons(4) some day? > > I'm about to try fresh -CURRENT on some HP AMD APU-based laptops, hence > > I'll ask: do [Intel or Radeon graphics] laptops suspend/resume without > > issues in X11 or on the naked console as well? (In a shop, I could only > > quickly test our X11-less memstick image.) > > Once KMS is loaded they resume fine. They require the KMS driver to turn > the LCD panel back on. Without KMS they also "resume" but the screen is off > so you can't see anything. However, you can type blind and run commands. > If the network is up you can ssh into the laptop, etc. after resume. > [...] > On HEAD you need to set kern.vty=sc to use sc(4) instead of vt(4). For > suspend/resume without X that should be sufficient. You would only need > the old drm drivers for X. > [...] > Note that for the HP netbook, resume in console with vt(4) does not work > without KMS (due to vt(4) not supporting VESA). OK I see, makes sense. So my best bet would be to try suspend/resume with vt(4)+KMS, then if it fails try with kern.vty=sc (in the context of GENERIC kernel and pure console). ./danfe From owner-freebsd-mobile@freebsd.org Fri Feb 19 12:00:57 2016 Return-Path: Delivered-To: freebsd-mobile@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 C1768AAD11C; Fri, 19 Feb 2016 12:00:57 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mx.nsu.ru (mx.nsu.ru [84.237.50.39]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6F0BA1A05; Fri, 19 Feb 2016 12:00:57 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from regency.nsu.ru ([193.124.210.26]) by mx.nsu.ru with esmtp (Exim 4.72) (envelope-from ) id 1aWjju-0007Lx-6s; Fri, 19 Feb 2016 18:00:52 +0600 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.14.2/8.14.2) with ESMTP id u1JC1sG5021917; Fri, 19 Feb 2016 18:01:54 +0600 (NOVT) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.14.2/8.14.2/Submit) id u1JC1n64021909; Fri, 19 Feb 2016 18:01:49 +0600 (NOVT) (envelope-from danfe) Date: Fri, 19 Feb 2016 18:01:49 +0600 From: Alexey Dokuchaev To: Adrian Chadd Cc: John Baldwin , Kevin Oberman , "current@freebsd.org" , Stefan Ehmann , "freebsd-mobile@freebsd.org" Subject: Re: Thinkpad T410: resume broken Message-ID: <20160219120149.GA18684@regency.nsu.ru> References: <53762216.8020205@gmx.net> <2846385.IUIOUlEDYf@ralph.baldwin.cx> <20160218154712.GA56997@regency.nsu.ru> <9693306.i8x5an8c0H@ralph.baldwin.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-KLMS-Rule-ID: 1 X-KLMS-Message-Action: clean X-KLMS-AntiSpam-Lua-Profiles: 91565 [Feb 19 2016] X-KLMS-AntiSpam-Version: 5.5.9.33 X-KLMS-AntiSpam-Envelope-From: danfe@regency.nsu.ru X-KLMS-AntiSpam-Rate: 0 X-KLMS-AntiSpam-Status: not_detected X-KLMS-AntiSpam-Method: none X-KLMS-AntiSpam-Moebius-Timestamps: 3971469, 3971510, 3971287 X-KLMS-AntiSpam-Info: LuaCore: 414 414 652141367f63b6038f5642fa97308d3a9d2edb46, 127.0.0.200:7.1.3; regency.nsu.ru:7.1.1; d41d8cd98f00b204e9800998ecf8427e.com:7.1.1; 193.124.210.26:7.1.3,7.1.2,7.3.4; nsu.ru:7.1.1; 127.0.0.199:7.1.2; bugs.freebsd.org:7.1.1 X-KLMS-AntiSpam-Interceptor-Info: scan successful X-KLMS-AntiPhishing: Clean, 2016/02/18 13:06:53 X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.705, not scanned, license restriction X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Feb 2016 12:00:57 -0000 On Thu, Feb 18, 2016 at 10:02:17AM -0800, Adrian Chadd wrote: > [snip] > > Someone should sit me down with pizza and "help" me just modularise > the vesa/fb code so we can use it in vt. > > It isn't /that/ hard, I've just been preoccupied. And before it happens, someone(tm) could write a few paragraphs of current state of affairs and codependencies between sc(4), vt(4), and VESA. :-) Hopefully this would lower the degree of "black magic" surrounding this code and help with some [1] related PRs. ./danfe [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=174504 From owner-freebsd-mobile@freebsd.org Fri Feb 19 12:37:40 2016 Return-Path: Delivered-To: freebsd-mobile@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 37C84AAE4D5 for ; Fri, 19 Feb 2016 12:37:40 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 1F0991335 for ; Fri, 19 Feb 2016 12:37:40 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: by mailman.ysv.freebsd.org (Postfix) id 1BF22AAE4D3; Fri, 19 Feb 2016 12:37:40 +0000 (UTC) Delivered-To: mobile@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 1B690AAE4D0; Fri, 19 Feb 2016 12:37:40 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mx.nsu.ru (mx.nsu.ru [84.237.50.39]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BB0901332; Fri, 19 Feb 2016 12:37:39 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from regency.nsu.ru ([193.124.210.26]) by mx.nsu.ru with esmtp (Exim 4.72) (envelope-from ) id 1aWkJL-0001Bg-JD; Fri, 19 Feb 2016 18:37:28 +0600 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.14.2/8.14.2) with ESMTP id u1JCcWdE030139; Fri, 19 Feb 2016 18:38:32 +0600 (NOVT) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.14.2/8.14.2/Submit) id u1JCcRtB030110; Fri, 19 Feb 2016 18:38:27 +0600 (NOVT) (envelope-from danfe) Date: Fri, 19 Feb 2016 18:38:27 +0600 From: Alexey Dokuchaev To: John Baldwin Cc: current@freebsd.org, mobile@freebsd.org Subject: Re: Thinkpad T410: resume broken Message-ID: <20160219123827.GA27878@regency.nsu.ru> References: <53762216.8020205@gmx.net> <1519677.qimO7W0WJL@ralph.baldwin.cx> <20160218165629.GA64990@regency.nsu.ru> <3029262.DlAcg8ENfU@ralph.baldwin.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3029262.DlAcg8ENfU@ralph.baldwin.cx> User-Agent: Mutt/1.4.2.1i X-KLMS-Rule-ID: 1 X-KLMS-Message-Action: clean X-KLMS-AntiSpam-Lua-Profiles: 91566 [Feb 19 2016] X-KLMS-AntiSpam-Version: 5.5.9.33 X-KLMS-AntiSpam-Envelope-From: danfe@regency.nsu.ru X-KLMS-AntiSpam-Rate: 0 X-KLMS-AntiSpam-Status: not_detected X-KLMS-AntiSpam-Method: none X-KLMS-AntiSpam-Moebius-Timestamps: 3971555, 3971593, 3971287 X-KLMS-AntiSpam-Info: LuaCore: 414 414 652141367f63b6038f5642fa97308d3a9d2edb46, 127.0.0.200:7.1.3; people.freebsd.org:7.1.1; regency.nsu.ru:7.1.1; 193.124.210.26:7.1.3,7.1.2,7.3.4; nsu.ru:7.1.1; 127.0.0.199:7.1.2; d41d8cd98f00b204e9800998ecf8427e.com:7.1.1 X-KLMS-AntiSpam-Interceptor-Info: scan successful X-KLMS-AntiPhishing: Clean, 2016/02/18 13:06:53 X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.705, not scanned, license restriction X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Feb 2016 12:37:40 -0000 On Thu, Feb 18, 2016 at 09:51:08AM -0800, John Baldwin wrote: > On Thursday, February 18, 2016 10:56:29 PM Alexey Dokuchaev wrote: > > # pciconf -lc pci0:0:0 > > hostb0@pci0:0:0:0: class=0x060000 card=0x83191033 chip=0x25908086 rev=0x04 hdr=0x00 > > cap 09[e0] = vendor (length 9) Intel cap 2 version 1 > > Humm, perhaps PCI0 is not at 0:0. Can you find the _ADR method for > _SB_.PCI0? That contains the "slot" and "function" as two words, e.g. > 0x10002 would correspond to the 'pci0:1:2' device (or possibly pci0:2:1, > don't recall the order off the top of my head). Seems it's all zeros: Device (PCI0) { ... Name (_ADR, 0x00) // _ADR: Address I've uploaded the dump on freefall [1], perhaps I've missed something so you can have a better/sharper look. ./danfe [1] http://people.freebsd.org/~danfe/nec_versa_s950.asl From owner-freebsd-mobile@freebsd.org Fri Feb 19 19:17:27 2016 Return-Path: Delivered-To: freebsd-mobile@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 5F0C6AAE3D6 for ; Fri, 19 Feb 2016 19:17:27 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4E35613B5 for ; Fri, 19 Feb 2016 19:17:27 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 4AB2FAAE3D1; Fri, 19 Feb 2016 19:17:27 +0000 (UTC) Delivered-To: mobile@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 4A2B6AAE3CF; Fri, 19 Feb 2016 19:17:27 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2C24513B4; Fri, 19 Feb 2016 19:17:27 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 74EF8B946; Fri, 19 Feb 2016 14:17:25 -0500 (EST) From: John Baldwin To: Alexey Dokuchaev Cc: current@freebsd.org, mobile@freebsd.org Subject: Re: Thinkpad T410: resume broken Date: Fri, 19 Feb 2016 10:48:56 -0800 Message-ID: <1677027.G58VU7gWm8@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: <20160219123827.GA27878@regency.nsu.ru> References: <53762216.8020205@gmx.net> <3029262.DlAcg8ENfU@ralph.baldwin.cx> <20160219123827.GA27878@regency.nsu.ru> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 19 Feb 2016 14:17:25 -0500 (EST) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Feb 2016 19:17:27 -0000 On Friday, February 19, 2016 06:38:27 PM Alexey Dokuchaev wrote: > On Thu, Feb 18, 2016 at 09:51:08AM -0800, John Baldwin wrote: > > On Thursday, February 18, 2016 10:56:29 PM Alexey Dokuchaev wrote: > > > # pciconf -lc pci0:0:0 > > > hostb0@pci0:0:0:0: class=0x060000 card=0x83191033 chip=0x25908086 rev=0x04 hdr=0x00 > > > cap 09[e0] = vendor (length 9) Intel cap 2 version 1 > > > > Humm, perhaps PCI0 is not at 0:0. Can you find the _ADR method for > > _SB_.PCI0? That contains the "slot" and "function" as two words, e.g. > > 0x10002 would correspond to the 'pci0:1:2' device (or possibly pci0:2:1, > > don't recall the order off the top of my head). > > Seems it's all zeros: > > Device (PCI0) > { > ... > Name (_ADR, 0x00) // _ADR: Address > > I've uploaded the dump on freefall [1], perhaps I've missed something so > you can have a better/sharper look. Ok, so your BIOS is just odd / broken. It's asked us to power that device down to D2, but it doesn't support any power management at all, so we whine. In practice it should be harmless and something you can ignore. -- John Baldwin