All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
Cc: Ingo Molnar <mingo@elte.hu>,
	len.brown@intel.com, linux-kernel@vger.kernel.org
Subject: Re: CONFIG_NO_HZ: missed ticks, stall (keyb IRQ required) [2.6.18-rc4-mm1]
Date: Mon, 06 Nov 2006 17:20:32 +0100	[thread overview]
Message-ID: <1162830033.4715.201.camel@localhost.localdomain> (raw)
In-Reply-To: <20061103000631.GA23182@rhlx01.hs-esslingen.de>

On Fri, 2006-11-03 at 01:06 +0100, Andreas Mohr wrote:
> ACPI: lapic on CPU 0 stops in C2[C2]

> How probable is it that the APIC timer got killed due to mis-programming
> in Linux versus VIA chipset design garbage probability? I.e. do you think
> there's a chance to fix C2 malfunction by going into the innards of
> VIA chipsets operation?
> How useful would it be to simply disable C2 operation (but not C1)
> in CONFIG_NO_HZ mode after's been determined to kill APIC timer?:

No, we better disable local apic timer in that case. What happens if you
boot your machine with ACPI disabled ?

	tglx



  reply	other threads:[~2006-11-06 16:18 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-01 14:07 CONFIG_NO_HZ: missed ticks, stall (keyb IRQ required) [2.6.18-rc4-mm1] Andreas Mohr
2006-11-01 21:51 ` Thomas Gleixner
2006-11-02  0:18   ` Andreas Mohr
2006-11-02  7:31     ` Thomas Gleixner
2006-11-02  8:14       ` Thomas Gleixner
2006-11-02 17:22         ` Thomas Gleixner
2006-11-02 19:28           ` Andreas Mohr
2006-11-02 20:34             ` Andreas Mohr
2006-11-03  0:06               ` Andreas Mohr
2006-11-06 16:20                 ` Thomas Gleixner [this message]
2006-11-06 20:58                   ` Andreas Mohr
2006-11-07  6:41                     ` Len Brown
2006-11-07  8:07                       ` Ingo Molnar
2006-11-07  8:25                         ` Thomas Gleixner
2006-11-07  9:16                           ` Andreas Mohr
2006-11-07  9:28                             ` Thomas Gleixner
2006-11-07  9:45                               ` Thomas Gleixner
2006-11-07 22:27                                 ` Andreas Mohr
2006-11-08 19:36                                   ` Thomas Gleixner
2006-11-14  6:34                         ` Len Brown
2006-11-07  8:18                       ` Andreas Mohr
2006-11-07  8:24                         ` Ingo Molnar
2006-11-14  6:27                         ` Len Brown
  -- strict thread matches above, loose matches on Subject: below --
2006-11-14 17:21 Pallipadi, Venkatesh
2006-11-14 17:30 ` Andreas Mohr
2006-11-14 18:04   ` Andreas Mohr
2006-12-17 15:58 ` Tobias Diedrich
2006-11-14 18:06 Pallipadi, Venkatesh
2006-11-14 20:30 ` Andreas Mohr
2006-11-14 21:00   ` Andreas Mohr
2006-11-14 21:18     ` Andreas Mohr

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=1162830033.4715.201.camel@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=andi@rhlx01.fht-esslingen.de \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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.