linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marvin24@gmx.de (Marc Dietrich)
To: linux-arm-kernel@lists.infradead.org
Subject: possible hrtimer related problem on tegra
Date: Sun, 22 Jan 2012 16:18:12 +0100	[thread overview]
Message-ID: <1539302.lfXQIS47Lr@ax5200p> (raw)

Hi,

I've been plagued with random lockups starting with Linux 3.0.13 (pulled from 
ChromeOS-3.0 tree) on a Tegra board (paz00). First symtoms are slowly losing 
responsiveness followed by a total lockup (nothing in dmesg, no oops). Using 
performance governor instead of ondemand, made it go away.

So I started bisecting 3.0.12..3.0.13 and finially found that reverting 
24ee8bfe (hrtimer: Fix extra wakeups from __remove_hrtimer()) fixes the 
problem.

As Olof mentioned on IRC it is likely that the patch does not directly causes 
lockups but something else which was hidden before. It isn't clear to me if 
other tegra boards (seaboard, harmony) also suffer from this.

Any hints on this issue are appreciated.

Thanks

Marc

             reply	other threads:[~2012-01-22 15:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-22 15:18 Marc Dietrich [this message]
2012-01-23  8:09 ` possible hrtimer related problem on tegra Olof Johansson
2012-01-23 10:08   ` Marc Dietrich

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=1539302.lfXQIS47Lr@ax5200p \
    --to=marvin24@gmx.de \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).