linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mariusz Libera <mariusz.libera@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: kernel 3.1 lots of cpu stalls and lockups
Date: Thu, 17 Nov 2011 20:03:37 +0100	[thread overview]
Message-ID: <CACLQ8Mu_QvTi0ioLzLAmDHOOtRRc4RvSFFae3XPKdoL_e05VPQ@mail.gmail.com> (raw)

Hi,

since updating from kernel 3.0 to 3.1 I'm experiencing lockups.
They happen quite randomly, sometimes after 1 day of running,
other times after few hours or just few minutes after booting.
I don't have an idea what may be causing them, but in dmesg I see lots of

INFO: rcu_preempt_state detected stalls on CPUs/tasks: {} (detected by
0, t=18002 jiffies)

and backtraces.

Please have a look at following ArchLinux bug report with logs and comments from
other affected people.

https://bugs.archlinux.org/task/26847

Mariusz Libera

                 reply	other threads:[~2011-11-17 19:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CACLQ8Mu_QvTi0ioLzLAmDHOOtRRc4RvSFFae3XPKdoL_e05VPQ@mail.gmail.com \
    --to=mariusz.libera@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;
as well as URLs for NNTP newsgroup(s).