From: Andrew Morton <akpm@linux-foundation.org>
To: lenb@kernel.org, linux-acpi@vger.kernel.org
Subject: Re: breakage in current git-acpi
Date: Sun, 25 Feb 2007 00:54:17 -0800 [thread overview]
Message-ID: <20070225005417.a9e2245a.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070217190755.e708effd.akpm@linux-foundation.org>
> On Sat, 17 Feb 2007 19:07:55 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
> On Sat, 17 Feb 2007 21:59:02 -0500 Len Brown <lenb@kernel.org> wrote:
>
> >
> > Assuming there is exactly 1 event for each press,
> > then the kernel part of this is healthy.
> >
> > Assuming the failure is that the lid event fails
> > to trigger the STD after a few iterations,
> > and you did this after the failure started;
> > then it seems the failure isn't the event
> > at all, but perhaps the inability to re-invoke STD.
> >
> > What happens if you invoke STD manually with
> > # echo disk > /sys/power/state
>
> That works OK.
>
> > > 9: 1344 IO-APIC-fasteoi acpi
> > >
> > > it's increasing even while the machine is just sitting there.
> >
> > That's okay -- it is common -- particularly
> > laptops, which are likely to have a number of events ticking away.
> > thermal and fan control, and battery state, in particular.
> >
> > > > Also, you should be able to see the state of the lid in a file under /proc/acpi/button/*/
> > >
> > > sony:/home/akpm# cat /proc/acpi/button/lid/LID0/state
> > > state: closed
> > > sony:/home/akpm# cat /proc/acpi/button/lid/LID0/state
> > > state: open
> > >
> > > all seems well.
> > >
> > > Stopping and restarting acpid doesn't fix it.
> >
> > Yeah, it must be suspend-to-disk itself refusing to suspend.
> > Probably when automatically invoked any errors or warnings
> > get sent to /dev/null.
> > Are there any dmesg associated with the failed suspend attempt?
>
> No messages come out when I shut the lid.
>
> Manually suspending works normally.
>
> > How many suspend cycles can you survive before git-acpi is applied?
>
> I tested up to five or six times once.
So.. I went from 2.6.20-mm1 back to 2.6.21-rc1 the other day and have
since been happily suspending via lid closure maybe ten times a day.
Any more suggestions about how to debug this?
How does the suspend happen, anyway? Is it acpid's job to read the
LID0/state file and to then poke /sys/power/state? Or is that linkage
in-kernel?
next prev parent reply other threads:[~2007-02-25 8:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-17 6:39 breakage in current git-acpi Andrew Morton
2007-02-17 7:25 ` Len Brown
2007-02-17 7:49 ` Andrew Morton
2007-02-18 2:59 ` Len Brown
2007-02-18 3:07 ` Andrew Morton
2007-02-25 8:54 ` Andrew Morton [this message]
2007-02-25 14:20 ` Alexey Starikovskiy
2007-02-25 14:44 ` Alexey Starikovskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070225005417.a9e2245a.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.