Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 07 Nov 2007 21:30:06 -0800
From:      "Kevin Oberman" <oberman@es.net>
To:        freebsd-current@freebsd.org
Subject:   Re: Recent update of 7-BETA causes laptop to freeze on battery 
Message-ID:  <20071108053006.28F384500E@ptavv.es.net>
In-Reply-To: Your message of "Wed, 07 Nov 2007 12:08:49 PST." <20071107200849.GO7943@bunrab.catwhisker.org> 

next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_1194499806_96090P
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Nov. 7, 2007, Kevin Oberman wrote:

> After an update of my laptop to 7-BETA2 on Nov. 4, I can no longer run
> on battery. If I boot on battery, everything is normal until devd is
> started. It immediately fires off /etc/rc.d/power_profile which
> sets my system to C4.
> 
> Once this happens, the system almost freezes. It takes about 15 seconds
> to move on the ipfw and, after the initial "Flushed all rules" it pauses
> for another 20-30 seconds and loads rules by ones and twos before
> finally totally freezing. Ctrl-C will cause a several more lines to come
> out, but it never makes it to multiuser mode.
> 
> If I plug it in, it often eventually switches back to C1 and runs
> normally. Pulling the plug again switches back to C4 and everything
> locks up. I eventually gave up and power cycled the system. (Ugh!) It
> may be an issue with output to the console as, if it unfreezes at all,
> it usually spits out several lines to the console at once before another
> pause.
> 
> This has not been a problem until recently. My last known working kernel
> was from back on about Oct. 15, although I think one from back on Oct 29
> also worked. (Just not sure that I had it on battery.)
> 
> Any ideas on where to look for this and how to debug? If forces me to
> leave the CX state at HIGHEST (C1) all the time with kills the battery.

I've learned a bit more about the problem.

I have discovered that this is tied to the syscons. If I set cx_lowest
to C3 or C4 in X, it works fine. If I set it while in syscons, the
system almost completely locks up. If I have cx_lowest set to C3 and
shut down my X session, it fails as soon as it drops into syscons. I get
a few lines of output and then it hangs for a very long time. After
several minutes I could get logged onto another vty and change
dev.cpu.0.cx_lowest to C1 which made it all work again.

Since it might be scheduler related, I should mention that I run
SCHED_ULE on an 2 GHz T43 (Pentium-M).

Has anyone else seen this?
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751


--==_Exmh_1194499806_96090P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (FreeBSD)
Comment: Exmh version 2.5 06/03/2002

iD8DBQFHMp7ekn3rs5h7N1ERAlpOAKCYt7zGXDtzYqyplfjoLucPPpWWawCdGuaN
n+2KSRGLk8Nim+J05+QWkis=
=k7BU
-----END PGP SIGNATURE-----

--==_Exmh_1194499806_96090P--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071108053006.28F384500E>