From: Peter Meiser <meiser@gmx-topmail.de>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: Dell Vostro V131: special hotkey not working
Date: Wed, 25 Apr 2012 16:19:51 +0200 [thread overview]
Message-ID: <4F980807.6000705@gmx-topmail.de> (raw)
In-Reply-To: <20120425135328.GA13385@srcf.ucam.org>
Hello Matthew,
Am 25.04.2012 15:53, schrieb Matthew Garrett:
> watch -n 0.1 cat /proc/interrupts
When running "watch -n 0,1 cat /proc/interrupts" (watch -n 0.1 errors out, maybe because of German environment???), the following row increases after each press:
9: 5 0 0 0 IO-APIC-fasteoi acpi
Others increase more quickly, but they are iwlwifi, i915, "Local timer interrupts" and "Rescheduling interrupts" which are out of interest, right?
Best regards,
Peter
next prev parent reply other threads:[~2012-04-25 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F97FA4C.9040201@gmx-topmail.de>
2012-04-25 13:53 ` Dell Vostro V131: special hotkey not working Matthew Garrett
2012-04-25 14:19 ` Peter Meiser [this message]
2012-04-25 14:22 ` Matthew Garrett
2012-05-11 5:28 ` Peter Meiser
2013-01-19 10:38 ` Peter Meiser
2013-07-20 5:03 ` Peter Meiser
2014-06-12 6:58 ` Peter Meiser
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=4F980807.6000705@gmx-topmail.de \
--to=meiser@gmx-topmail.de \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox