From owner-freebsd-current@FreeBSD.ORG Fri May 16 20:51:37 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D39025A8; Fri, 16 May 2014 20:51:37 +0000 (UTC) Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8192927B0; Fri, 16 May 2014 20:51:37 +0000 (UTC) Received: by mail-qg0-f43.google.com with SMTP id 63so5085365qgz.16 for ; Fri, 16 May 2014 13:51:36 -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=z53+4r8TcuvCSug8BZkWeKf/9ajXuc488v+bCduTVy0=; b=zMtzXzAVnqg5gGkil63DvMFLpfR1mCpfi2iJWCrgM8qBYGCSYiDyk7ga0Uzr+IIV07 CBHTWbIfFbMOsoydUoWw5KA4O0DRPkjOSoBguCRm2Al/nOk4Xu11yNvxhBTKC+NNWpNC GuAw73kfzm2n6dBc+NgnjeJGzUhmANux7T9vVOiHwAbceU8vNXtmkrlaeWdTbNvNxoe4 fjN5PLDrFXs8yvAT2SHm/eH9CyB0Qnsqe1ZKuA57P+m17YZh9W84OfQxkyfNzA0j0nZT uuEqqawnOQYcIKbydmwjjjiUrjAGm3xPHMRbzrXrsnnXhwE8rZ+OvB/8BPN2yZqhMqw3 yEzQ== MIME-Version: 1.0 X-Received: by 10.224.37.10 with SMTP id v10mr22860248qad.98.1400273496689; Fri, 16 May 2014 13:51:36 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Fri, 16 May 2014 13:51:36 -0700 (PDT) In-Reply-To: <537675A0.8000108@janh.de> References: <53762216.8020205@gmx.net> <537675A0.8000108@janh.de> Date: Fri, 16 May 2014 13:51:36 -0700 X-Google-Sender-Auth: ahSHUgPItl-xS1Q9wuddyKBjp_w Message-ID: Subject: Re: Thinkpad T410: resume broken From: Adrian Chadd To: Jan Henrik Sylvester Content-Type: text/plain; charset=UTF-8 Cc: Kevin Oberman , current-list freebsd , Stefan Ehmann , "freebsd-mobile@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2014 20:51:38 -0000 Hi, Yeah. I'd really suggest trying with stable/10 or -HEAD with vt enabled and no VESA. -a On 16 May 2014 13:31, Jan Henrik Sylvester wrote: > On 05/16/2014 20:10, 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. > > (Sorry, this is more or less a lengthy "me, too":) > > I am observing exactly the same on my T510 (not surprisingly, as it is > basically the same with a different screen size) using Nvidia (in > contract to most other recent mailing list reports, which are using Intel). > > From 8.1-RELEASE to 9.2-RELEASE, suspend and resume used to work with a > generic kernel (I like generic release kernels and freebsd-update) -- > except for a short time, which was due to the Xorg port. Especially > 9.X-RELEASE were really stable with all the hardware working after > resume (maybe except firewire). > > After going to 10.0-RELEASE, resuming would briefly turn the screen on, > but it would go back to black with the power LED continuing to blink (as > it does while sleeping). After a while, I realized that I lost the > non-default option ACPI_PM for x11/nvidia-driver installing 10.0. > > With ACPI_PM for x11/nvidia-driver, I had at least one resume with most > of the hardware working: The screen was still unusable being static with > colorful lines, but I could ssh into the machine over wireless. > > I have not had time to try 10-STABLE with vt, but from reading various > reports on the lists, that is probably the only way. > > I hope there will be a vt enabled kernel on the 10.1-RELEAS media, if vt > is going to be required even for configurations that would work just > fine on 9.X (WITH_NEW_XORG=yes is very usable with x11/nvidia-driver > even without vt). > > From what you said, you already have ACPI_PM for x11/nvidia-driver as it > is listed on the wiki. Have you? > > Cheers, > Jan Henrik