public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	john stultz <johnstul@us.ibm.com>, Ingo Molnar <mingo@elte.hu>,
	Len Brown <lenb@kernel.org>,
	Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Subject: Re: clockevents: fix resume logic
Date: Tue, 11 Sep 2007 23:49:47 +0200	[thread overview]
Message-ID: <1189547387.5235.69.camel@chaos> (raw)
In-Reply-To: <1189540321.5235.21.camel@chaos>

On Tue, 2007-09-11 at 21:52 +0200, Thomas Gleixner wrote:
> >     C1:                  type[C1] promotion[C2] demotion[--] latency[001] usage[00000010] duration[00000000000000000000]
> >    *C2:                  type[C2] promotion[--] demotion[C1] latency[001] usage[00008316] duration[00000000000170717293]
> 
> Ok, here we are. The bad one uses C2 which stops the local apic on the
> VAIO. I suspect we end up in the suspend/resume with going into C2
> without the broadcast active.
> 
> Can you try to get the output of SysRq-Q during the "it needs help from
> keyboard" period ?

Summary of the oddities we are seing:

1.) disabling local apic timer makes the problem go away
2.) disabling nohz and highres makes the problem go away
3.) adding the cpuidle patches from the acpi tree makes the problem go
away

The obvious conclusion is, that in all other cases we run into a state,
where the local apic timer is not working.

1) we do not use it
2) it is used in periodic mode
3) the cpu does not enter C2 (which turns the lapic timer off on the
VAIO)

While 1) and 3) are understandable, the reason why 2) is working is a
mystery because the periodic mode is affected by the C state as well.

Andrew, can you please provide the output of /proc/timer_list when you
boot the kernel with "nohz=off highres=off", but honestly I do not
expect a lot of enlightenment from it.

The Sysrq-Q output from the point where the box is stuck without
keystrokes might give us more information.

	tglx



  reply	other threads:[~2007-09-11 21:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200707220159.l6M1xBgH001236@hera.kernel.org>
2007-09-10 21:47 ` clockevents: fix resume logic Andrew Morton
2007-09-11  6:37   ` Thomas Gleixner
2007-09-11  7:00     ` Andrew Morton
2007-09-11  7:23       ` Thomas Gleixner
2007-09-11  7:34         ` Thomas Gleixner
2007-09-11  7:44           ` Andrew Morton
2007-09-11  7:47         ` Thomas Gleixner
2007-09-11  8:20           ` Andrew Morton
2007-09-11  8:35             ` Andrew Morton
2007-09-11  9:16               ` Thomas Gleixner
2007-09-11 10:31                 ` Andrew Morton
2007-09-11 11:23                   ` Rafael J. Wysocki
2007-09-11 11:22                     ` Andrew Morton
2007-09-11 12:09                       ` Rafael J. Wysocki
2007-09-11 18:25                         ` Andrew Morton
2007-09-11 18:38                           ` Thomas Gleixner
2007-09-11 18:44                             ` Andrew Morton
2007-09-11 19:52                               ` Thomas Gleixner
2007-09-11 21:49                                 ` Thomas Gleixner [this message]
2007-09-12  9:16                                   ` Andrew Morton
2007-09-12 16:57                                     ` Thomas Gleixner
2007-09-13  4:48                                       ` Andrew Morton
2007-09-12  9:12                                 ` Andrew Morton
2007-09-17 18:37                                   ` Pavel Machek
2007-09-22  8:50                                     ` Thomas Gleixner
2007-09-22 10:47                                       ` Rafael J. Wysocki
2007-10-02  8:05                                       ` Pavel Machek
2007-09-11 19:35                           ` Rafael J. Wysocki
2007-09-11 19:39                             ` Andrew Morton
2007-09-11 19:40                           ` Arjan van de Ven
2007-09-11  9:01             ` Thomas Gleixner

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=1189547387.5235.69.camel@chaos \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=johnstul@us.ibm.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=venkatesh.pallipadi@intel.com \
    /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