Ok. Also to point out that when it goes to sleep, regardless of dim or blank, will drop the wifi connections. However, getting out of sleep will eventually (in about a minute) reconnect. So SLEPP is equivalent to suspend, disregarding DCON/screen state.
--- On Mon, 3/29/10, Paul Fox pgf@laptop.org wrote:
From: Paul Fox pgf@laptop.org Subject: Re: (fwd) Re: powerd on XO-1 (was Re: New release ... OS13 ) To: "Yioryos Asprobounitis" mavrothal@yahoo.com Cc: "OLPC Devel" devel@lists.laptop.org, "fedora-olpc-list" fedora-olpc-list@redhat.com Date: Monday, March 29, 2010, 4:43 PM hi yioryos --
thanks for the detailed descriptions.
debugging and drawing conclusions about suspend/resume problems is pretty hard without a serial connection. i'll try and stress an OS13 a little more, and see if i can't reproduce your symptoms. others with serial ports are welcome/encouraged to try as well. ;-)
paul
yioryos wrote:
Well, my predicament with powerd and a proper ticket
filling
is that I can get no logs. So I'll describe the
story instead
...:-)
Test settings SLEEP=15 DIM=30 BLANK=45 running on
battery.
os13 (clean). XO-1 CL1 Firmware q2e42d(not
overclocked, no
SDcard or anything attached to it)
Without trace-on the XO will sleep and will _not_ dim
or
blank. On slight touchpad touch after the
timeouts (or
spontaneous if you let it long enough) will wake to
dim and
then blank. Power button wakes it up fine but
no trace log.
okay -- this is definitely a kernel issue then. i think i thought we'd gotten past all the bad ones, but i guess not.
With trace-on, same behavior but on slight touch of
the
touchpad (or spontaneously) will wake to dim and
freeze there.
After hard reboot no trace log either :( and no I do
not have
a serial port adapter) It's a clue though (I hope)
hard freezes are certainly harder to diagnose.
If while at sleep, pass dim or blank time points, you
wake it
up by typing or rubbing the touchpad constantly, will
wake,
dim and then recover to normal operation. This
is where the
attached powerd.trace is coming from.
It would appear that the kernel configuration is
also
relevant. With the os13 kernel I also got a
freeze without
the trace-on (1 in 5 tests). With the 2010322
kernel never
(in 6 tests). Using one of my kernels patched
for Aufs and
with hfsplus, sisusbvga modules and in-kernel loop
enabled, I
can not get it to sleep unless both DIM and BLANK are
before
SLEEP time (I could provide config diffs and trace
logs if you
think it may help the issue at hand)
paul
> in DIM=180, BLANK=480,
SLEEP=600. No huge power
savings but > at least the build is usable. > > > --- On Sat, 3/27/10, Paul Fox pgf@laptop.org wrote: > > > From: Paul Fox pgf@laptop.org > > Subject: Re: (fwd) Re: powerd on
XO-1 (was Re:
New release ... OS13 ) > > To: "Yioryos Asprobounitis"
> > Cc: "OLPC Devel" devel@lists.laptop.org, "fedora-olpc-list" > fedora-olpc-list@redhat.com > > Date: Saturday, March 27, 2010,
1:26 PM
> > yioryos wrote: > > > I guess the question
is: is os13
usable at this > > stage? > > > Should power
management be be
inactivated in the > > control panel? > > > Are there
appropriate/recommended
powerd.conf > > settings for the XO-1 at this > > > stage? > > > > maybe, i don't know, and i don't
know.
> > > > paul > > =--------------------- > > paul fox, pgf@laptop.org > > > > >
=--------------------- paul fox, pgf@laptop.org
=--------------------- paul fox, pgf@laptop.org