From: Natanji <natanji@gmail.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Henning Schild <henning@wh9.tu-dresden.de>,
Tom Gundersen <teg@jklm.no>,
ibm-acpi-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
maciej.rutecki@gmail.com, lenb@kernel.org
Subject: Re: [ibm-acpi-devel] Regression in thinkpad-acpi events
Date: Wed, 30 Nov 2011 14:34:37 +0100 [thread overview]
Message-ID: <4ED630ED.3070301@gmail.com> (raw)
In-Reply-To: <20111130111507.GA32079@khazad-dum.debian.net>
Yes, there are dozens of acpi interrupts every second.
$ cat /proc/interrupts | grep acpi ; sleep 1; cat /proc/interrupts |
grep acpi
9: 1776309 0 IO-APIC-fasteoi acpi
9: 1776332 0 IO-APIC-fasteoi acpi
On Wed 30 Nov 2011 12:15:07 PM CET, Henrique de Moraes Holschuh wrote:
> On Wed, 30 Nov 2011, Natanji wrote:
>> The standard Arch kernel does not use tuxonice, you need to build your
>> kernel manually if you want it. I also don't receive these events before
>> the first hibernation, so you might be having a different problem.
>
> Just a hunch: check /proc/interrupts. One of them must be assigned to acpi,
> and it *must* increase when you press hotkeys, etc.
>
> Does it?
>
prev parent reply other threads:[~2011-11-30 13:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EBAC3B5.5060405@gmail.com>
[not found] ` <201111142031.06663.maciej.rutecki@gmail.com>
[not found] ` <4EC16F8E.7060601@gmail.com>
2011-11-14 20:18 ` Regression in thinkpad-acpi events Maciej Rutecki
2011-11-15 7:09 ` Tom Gundersen
2011-11-15 23:03 ` Henrique de Moraes Holschuh
2011-11-24 9:25 ` Tom Gundersen
2011-11-25 0:25 ` Henrique de Moraes Holschuh
2011-11-27 1:23 ` [ibm-acpi-devel] " Henning Schild
2011-11-30 9:22 ` Natanji
[not found] ` <4ED5F5D7.8020208-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-11-30 11:15 ` Henrique de Moraes Holschuh
2011-11-30 13:34 ` Natanji [this message]
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=4ED630ED.3070301@gmail.com \
--to=natanji@gmail.com \
--cc=henning@wh9.tu-dresden.de \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=teg@jklm.no \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).