From: Thomas Gleixner <tglx@linutronix.de>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
stable@kernel.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Meyer <thomas.mey@web.de>
Subject: Re: 2.6.21 known regressions (v2) (for -stable team)
Date: Sat, 28 Apr 2007 22:04:31 +0200 [thread overview]
Message-ID: <1177790671.7646.278.camel@localhost.localdomain> (raw)
In-Reply-To: <46338DF8.8010901@m3y3r.de>
On Sat, 2007-04-28 at 20:10 +0200, Thomas Meyer wrote:
> Thomas Gleixner schrieb:
> > On Sat, 2007-04-28 at 18:27 +0200, Michal Piotrowski wrote:
> >
> >> Subject : Bad interaction between dynticks and amarok?
> >> References : http://lkml.org/lkml/2007/4/26/307
> >> Submitter : Thomas Meyer <thomas.mey@web.de>
> >> Status : Unknow
> >>
> >
> > Michal,
> >
> > I don't think this is a regression. What Thomas wanted to point out is,
> > that the amarok / sound device is making the positive effect of dynticks
> > moot, as it starts to trigger useless interrupts.
> >
> > Thomas, is my interpretation correct ? Did you check, which interrupt
> > was increasing - i.e. was it the soundcard one ?
> >
> No, it wasn't the soundcard one. but i had this effect with amarok and
> audacious... so, i guessed... which was wrong.
>
> It's the timer interrupt (+50-70 timer interrupts). But i'm not sure
> what both applications are doing, while they are "idle"...
Ok, so amarok is one of those applications which arm timers for no
obvious reason. If you enable CONFIG_TIMER_STATS in the kernel, you can
analyse the timer offenders via the /proc/timer_stats interface.
tglx
next prev parent reply other threads:[~2007-04-28 20:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 16:27 2.6.21 known regressions (v2) (for -stable team) Michal Piotrowski
2007-04-28 16:52 ` Gene Heskett
2007-04-28 17:18 ` Michal Piotrowski
2007-04-28 17:52 ` Gene Heskett
2007-04-28 18:19 ` [stable] " Greg KH
2007-04-28 21:21 ` Krzysztof Halasa
2007-04-29 1:25 ` Greg KH
2007-04-28 16:58 ` Thomas Gleixner
2007-04-29 5:34 ` send_IPI_mask_bitmask() (Re: 2.6.21 known regressions (v2) (for -stable team)) Len Brown
2007-04-29 8:25 ` Thomas Gleixner
2007-04-28 17:06 ` 2.6.21 known regressions (v2) (for -stable team) Thomas Gleixner
2007-04-28 18:10 ` Thomas Meyer
2007-04-28 20:04 ` Thomas Gleixner [this message]
2007-04-28 18:03 ` Thomas Meyer
2007-04-28 19:06 ` Diego Calleja
2007-04-30 21:30 ` Stephen Hemminger
2007-04-30 22:35 ` Håkan Lindqvist
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=1177790671.7646.278.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=stable@kernel.org \
--cc=thomas.mey@web.de \
--cc=thomas@m3y3r.de \
/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