From owner-freebsd-current@FreeBSD.ORG Wed Oct 20 16:58:04 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C0F6106564A for ; Wed, 20 Oct 2010 16:58:04 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id D0DA08FC0C for ; Wed, 20 Oct 2010 16:58:03 +0000 (UTC) Received: by gwb20 with SMTP id 20so2171633gwb.13 for ; Wed, 20 Oct 2010 09:58:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=fZc5TrtPJhCjXr20Sf1fRQUVna1qOIhH3SgNRIn4Dus=; b=DhEfQPt4Q965SyYA/XI0bUl9cUSQqVOUt33/7OcDDJHXKCXvQbF0G3nldGYtUtFA4B +/Y2SHt9MkFNJWlyb7sf6z+tZV8lpAv6PwA75JhLgUDdu20mHNmPVVdDGd97qDRpuU11 +l1FSJ6k3rpUzOFP0UZYtqgGaVs8KJu+zHXiU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=vLmuVD6fJeiG+nBF2KS6jBeFRmm7+m1obyTiM6HK8uMjCOPjHdxnXUZCDtNeNiJjcO 3AvmG0Odn1c/ofgdZVyozbplvkmuqUAqsEg7XaIYGMJQDpsb+AkMv3fdVcDSKBmUhveG +YuT5ygpXSoGK79i0pJ0WVgjQd/oZ54uGVkM0= Received: by 10.103.131.9 with SMTP id i9mr6837034mun.77.1287593882397; Wed, 20 Oct 2010 09:58:02 -0700 (PDT) Received: from ono-sendai.local ([75.111.34.169]) by mx.google.com with ESMTPS id d17sm252813fav.29.2010.10.20.09.57.49 (version=SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 09:57:51 -0700 (PDT) Message-ID: <4CBF1F88.2070805@gmail.com> Date: Wed, 20 Oct 2010 09:57:44 -0700 From: Matt User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.9) Gecko/20100918 Thunderbird/3.1.4 MIME-Version: 1.0 To: gljennjohn@googlemail.com References: <4C732522.1010400@gmail.com> <4CA556EB.902@gmail.com> <20101001144505.C62022@sola.nimnet.asn.au> <20101002142419.G62022@sola.nimnet.asn.au> <1286051977.1655.45.camel@RabbitsDen.RabbitsLawn.verizon.net> <20101003174833.V62022@sola.nimnet.asn.au> <4CBE42CA.3050103@gmail.com> <20101020114121.476961db@ernst.jennejohn.org> In-Reply-To: <20101020114121.476961db@ernst.jennejohn.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Sleep/Lenovo SL410 fails again after csup & clang X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 20 Oct 2010 16:58:04 -0000 On 10/20/10 02:41, Gary Jennejohn wrote: > On Tue, 19 Oct 2010 18:15:54 -0700 > Matt wrote: > >> My experience with a sleeping freebsd laptop has been shortlived! >> >> Today I rebuilt world using clang& this morning's csup current. >> Clang build went just swimmingly. >> >> Unthinkingly, I closed my laptop lid and put it in my case. >> When I got to my house, it was roasting with fans spinning and sleep >> light flashing. No damage, thankfully. >> >> Low and behold, hw.pci.do_power_resume=0 no longer lets my laptop sleep! >> >> I had recently fiddled with powerd, but problem persisted after >> reverting to previous configuration of associated sysctls etc. >> >> Interestingly, sleep bounce now fails with a hard freeze, which it never >> has in the past. >> >> Verbose output shows the wifi then re0 network interfaces going from >> D0->D3 as last living output. >> >> Please note problem persists regardless of user, X running, sleep_delay >> sysctl, do_power_resume, do_power_nodriver, powerd running/not running. >> >> Without sleep bounce, problem is characterized by flashing sleep light >> and spinning fans (CPU temperature is high). >> >> No devices added or removed, was sleeping this morning before >> buildworld. Is it worth rebuilding with gcc? Or a content change and not >> a compiler issue? Any major pci changes lately maybe? >> >> Matt >> sendtomatt@gmail.com >> >> Not sure where to go from here... >> If it is helpful, I can provide any required logs, verbose dmesg etc. >> > Did you _not_ have this problem when compiling with the base C compiler > (gcc)? Not really clear from your description. > > -- > Gary Jennejohn > It wasn't particularly clear to me at the time of posting. I subsequently compiled generic with both gcc and clang and issue persists, ruling out clang as source of issue. A diff of dmesg output from before csup buildworld and after did not reveal any startling differences. Booting from kernel.prev allowed it to sleep again, so it seems something changed in cvs. Matt