From: Mantas <grawity@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 3.2rc7 rcu_preempt stalls and tasks blocked.
Date: Wed, 11 Jan 2012 22:22:40 +0200 [thread overview]
Message-ID: <jekr2s$c9c$1@dough.gmane.org> (raw)
In-Reply-To: <bcf.4ef5dd08.61f72@roo.daria.co.uk>
On 2011-12-24 16:09, Jonathan Hudson wrote:
> Ever since 3.1, I've been experiencing rcu_preempt stalls, tasks
> blocked and subsequent lock ups on an eeepc 901. Judging by the thread
> <https://bugs.archlinux.org/task/26847> on the Arch forums, this is not
> an uncommon experience.
Can confirm on ASUS K52JT, using 3.2 (Arch Linux) and various git builds
starting around 3.2-rc6/7. Appears to be caused by heavier wireless
network activity (ath9k, Atheros AR9285, open network, IPv4 & IPv6),
such as BitTorrent -- although not by ordinary HTTP or such. Other posts
in the Arch bug report say having ipv6 loaded/enabled is causing the
problem.
During the lockup, accessing certain files in /proc (can't remember all,
but /proc/*/mounts and /proc/*/cgroup included) causes the process to
hang; same when running `ip`, `iwconfig` and related tools. Often (but
not always), killing NetworkManager makes everything work again.
Hoping for a fix someday.
--
Mantas M.
prev parent reply other threads:[~2012-01-11 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-24 14:09 Jonathan Hudson
2012-01-11 20:22 ` Mantas [this message]
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='jekr2s$c9c$1@dough.gmane.org' \
--to=grawity@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
Powered by JetHome