public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Artur Skawina <art.08.09@gmail.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, Nix <nix@esperi.org.uk>,
	Venkatesh Pallipadi <venki@google.com>,
	Damien Wyart <damien.wyart@free.fr>,
	John Drescher <drescherjm@gmail.com>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [BISECTED] 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (HPET)
Date: Fri, 10 Sep 2010 15:22:57 +0200	[thread overview]
Message-ID: <4C8A3131.7030003@gmail.com> (raw)
In-Reply-To: <4C89FD56.6060505@gmail.com>

On 09/10/10 11:41, Jiri Slaby wrote:
> AFAIU, clocksource=jiffies shouldn't fix this issue. If that's the case
> we have another 2.6.32->2.6.33 regression (and I will report it
> separately). People report the system is unusable (sleepers are not
> woken), unless clocksource=jiffies, clocksource=tsc or nolapic_timer is
> used or a key pressed (i.e. some HW interrupt):
> https://bugzilla.novell.com/show_bug.cgi?id=579932
> (there is also a report with 2.6.35.3 vanilla)

I saw this first in v2.6.35-rc4. The symptom is that suddenly everything
stops and the only way to make things progress is to generate some events.
Apps that are waiting for a timeout aren't woken up unless you press a key
etc. After a few minutes (and lots of key presses ;) ) the machine usually
recovers, leaving no trace in logs.
It's a nasty bug to debug as there's no way to trigger it, at least here,
and it usually does not want to happen when you most want it to; took me
~week to strike a bios upgrade from the suspect list, another one to
exclude intel_idle and so on. Never got around to check 30a564be9d955,
which was on the list too, unfortunately. I'll bet it /is/ the cause, but
won't be able to confirm this for quite a while...

artur

  reply	other threads:[~2010-09-10 13:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-05  0:51 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (ACPI idle?) Nix
2010-09-06  5:32 ` Damien Wyart
2010-09-06 20:27   ` Nix
2010-09-07  5:36     ` Damien Wyart
2010-09-08 21:24   ` Nix
2010-09-08 21:35     ` John Drescher
2010-09-08 22:25       ` Nix
2010-09-09 22:34     ` [BISECTED] 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (HPET) Nix
2010-09-09 23:44       ` John Drescher
2010-09-09 23:57         ` Nix
2010-09-10  0:08           ` John Drescher
2010-09-10  0:14             ` John Drescher
2010-09-10  0:59       ` Artur Skawina
2010-09-10  5:36         ` Damien Wyart
2010-09-10  7:42         ` Nix
2010-09-10  7:47           ` Damien Wyart
2010-09-10  8:37           ` Thomas Gleixner
2010-09-10  9:41             ` Jiri Slaby
2010-09-10 13:22               ` Artur Skawina [this message]
2010-09-10 20:13                 ` Nix
2010-09-10 20:12               ` Nix
2010-09-14 10:09             ` Thomas Gleixner
2010-09-14 20:17               ` Nix
2010-09-14 22:18                 ` Thomas Gleixner
2010-09-14 22:23                 ` Artur Skawina

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=4C8A3131.7030003@gmail.com \
    --to=art.08.09@gmail.com \
    --cc=damien.wyart@free.fr \
    --cc=drescherjm@gmail.com \
    --cc=hpa@zytor.com \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nix@esperi.org.uk \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=venki@google.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