Date: Wed, 20 Oct 2010 09:57:44 -0700 From: Matt <sendtomatt@gmail.com> To: gljennjohn@googlemail.com Cc: freebsd-current@freebsd.org Subject: Re: Sleep/Lenovo SL410 fails again after csup & clang Message-ID: <4CBF1F88.2070805@gmail.com> In-Reply-To: <20101020114121.476961db@ernst.jennejohn.org> References: <4C732522.1010400@gmail.com> <4CA556EB.902@gmail.com> <20101001144505.C62022@sola.nimnet.asn.au> <AANLkTikg-CW-wSiWz7VmtBKFafFkCvXeOMEoRW_U2Wvv@mail.gmail.com> <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>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/20/10 02:41, Gary Jennejohn wrote: > On Tue, 19 Oct 2010 18:15:54 -0700 > Matt<sendtomatt@gmail.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CBF1F88.2070805>