mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shawn Starr <shawn.starr@rogers.com>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.33-rc1] System timer flooding bus on Lenovo Thinkpad W500 laptop in x86_64
Date: Mon, 21 Dec 2009 19:58:51 -0500	[thread overview]
Message-ID: <200912211958.52120.shawn.starr@rogers.com> (raw)
In-Reply-To: <4B301744.2010404@gmail.com>

On December 21, 2009 07:48:04 pm Robert Hancock wrote:
> On 12/21/2009 12:12 PM, Shawn Starr wrote:
> > Hello kernel devs,
> >
> > I am noticing a serious problem with the system timer flooding the bus
> > with many interrupts for no reason. I have compiled the kernel with
> > tickless enabled.
> >
> > Can someone provide me some debugging to find out why this is happening?
> >
> > As a comparsion my quad core box has no such issue: (Running 2.6.32-rc7)
> > x86_64
> >    0:         42          4          1          1   IO-APIC-edge     
> > timer
> 
> That's not really a fair comparison, that box is likely using the APIC
> timer (which will be on a different line) instead of the PC timer. Those
> 48 interrupts likely all occurred just after boot.
> 
> > my Lenovo ThinkPad W500 (latest BIOS 3.11) laptop shows the system timer
> > flooding the bus (Running 2.6.33-rc1) x86_64
> >   0:      66775      70429   IO-APIC-edge      timer<-- keeps rising,
> > rapidly
> >
> > and  afew minutes ...
> >
> >   0:     119849     124505   IO-APIC-edge      timer
> >
> > Same for Rescheduling interrupts rising just as fast with the timer.
> >
> > This does not look right, powertop shows:
> >
> > 40.0% ( 62.1)<kernel IPI>  : Rescheduling interrupts
> > 22.9% ( 35.6)<interrupt>  : extra timer interrupt
> > 17.0% ( 26.4)<interrupt>  : iwlagn
> >
> > and another sample...
> >
> >    54.6% (144.8)<kernel IPI>  : Rescheduling interrupts
> >    14.6% ( 38.8)<interrupt>  : extra timer interrupt
> >     8.5% ( 22.6)<interrupt>  : iwlagn
> >     6.5% ( 17.2)<interrupt>  : uhci_hcd:usb6, radeon@pci:0000:01:00.0
> >     6.5% ( 17.2)   USB device  6-1 : Microsoft Basic Optical Mouse v2.0
> > (Microsoft )
> >
> > There is no cause for the rescheduling interrupts and extra timer
> > interrupt to wakeup the CPUs so much? Are there any timer issues?
> 
> Can you post full dmesg and /proc/interrupts output?
> 

This is found in http://bugzilla.kernel.org/show_bug.cgi?id=14354. 

Turning off dynticks has stopped the system timer from firing so much. But 
there still is an underlying irq problem because especially trying the radeon 
KMS IRQ support, typing or moving the mouse causes stalls. 

Thanks, 
Shawn.

  reply	other threads:[~2009-12-22  0:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-21 18:12 Shawn Starr
2009-12-21 19:12 ` Shawn Starr
2009-12-22  0:48 ` Robert Hancock
2009-12-22  0:58   ` Shawn Starr [this message]
2009-12-22  1:07     ` Robert Hancock
2009-12-22  3:08       ` Shawn Starr
2010-01-06 19:28 ` [2.6.33-rc1] System timer flooding bus on Lenovo Thinkpad W500 laptop in x86_64 - continues in -rc3 Shawn Starr
2010-01-17 20:48   ` [2.6.33-rc1] System timer flooding bus on Lenovo Thinkpad W500 laptop in x86_64 - update Shawn Starr

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=200912211958.52120.shawn.starr@rogers.com \
    --to=shawn.starr@rogers.com \
    --cc=hancockrwd@gmail.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®